Page MenuHome GnuPG

inconsistant bytecount for output files
Closed, InvalidPublic

Description

I ran the encryption process using the same input file, but the bytecount on
the output file was different.

[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp1 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp2 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp3 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp4 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp5 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp6 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp7 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp8 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ gpg --always-trust -r A4B5DCFA --output ztmp9 --encrypt
CCOD3082.04092013.103706.TXT
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
[mway@s1pvap026:~]$ ls -l z*
-rw-r--r-- 1 mway mway 138552 Apr 17 13:08 ztmp
-rw-r--r-- 1 mway mway 138551 Apr 17 13:08 ztmp1
-rw-r--r-- 1 mway mway 138552 Apr 17 13:08 ztmp2
-rw-r--r-- 1 mway mway 138551 Apr 17 13:08 ztmp3
-rw-r--r-- 1 mway mway 138550 Apr 17 13:09 ztmp4
-rw-r--r-- 1 mway mway 138550 Apr 17 13:09 ztmp5
-rw-r--r-- 1 mway mway 138552 Apr 17 13:09 ztmp6
-rw-r--r-- 1 mway mway 138550 Apr 17 13:09 ztmp7
-rw-r--r-- 1 mway mway 138550 Apr 17 13:09 ztmp8
-rw-r--r-- 1 mway mway 138550 Apr 17 13:09 ztmp9

Details

Version
1.4.8

Event Timeline

peppebx set Version to 1.4.8.
peppebx added a subscriber: peppebx.

That is okay. One reason for this is the encoding of big integer numbers; if
such a randomly generated number has the high bit set, a leading zero needs to
be inserted.