My public key block appears different on keyservers
Hello. I have uploaded my public key (GnuPG v2.0.10 (Darwin)) via command line and copy / paste methods into keys.gnupg.net and pgpkeys.mit.edu and when I look up the key on the systems they are different. I have been looking at this problem for a few days and uploading my keys to servers. So far none have shown me the same key that I produce on my machine. Here are the public keys with enough info to see the difference. keys.gnupg.net: -BEGIN PGP PUBLIC KEY BLOCK- Version: SKS 1.1.0 mQGiBEhZtL8RBACqrmsYj2U7VxEyWW36DLXfCt2qoRewdmT++GvUfYyu9RN3d2nK44SmxKFw 8uCa1WspSZuYpbDlS14y+4Ar4wf89DW5M7LF602v5uym4e6NiajT+q9DCi6P+wvLIFftgR7R . . . /shVjyh/iu7Bx2Lmqe/XmaliMw== =r14a -END PGP PUBLIC KEY BLOCK- keypgp.mit.edu -BEGIN PGP PUBLIC KEY BLOCK- Version: PGP Key Server 0.9.6 mQGiBEhZtL8RBACqrmsYj2U7VxEyWW36DLXfCt2qoRewdmT++GvUfYyu9RN3d2nK 44SmxKFw8uCa1WspSZuYpbDlS14y+4Ar4wf89DW5M7LF602v5uym4e6NiajT+q9D . . . bvyUKtbqAKCRbg0KVNDbvJJh8QBAioR0MF9MkACfZP7IVY8of4ruwcdi5qnv15mp YjM= =KWPX -END PGP PUBLIC KEY BLOCK- this is my public from my computer: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2.0.10 (Darwin) mQGiBECfWS8RBADGQWXHmjwFI4cjg3J72/vtclQPUOLV+9JjBjwqZSvXjjABiuqG 6d72S/+s3NgT7Ou1dtFm9ZgbZNNl4IWZsFXkpYIV3OTU2Q56aV9JWJ5kD2XYKCUX . . . 0QCePWCt+1K/qeHQvn/3k6d9UBToYIw= =OCgw -END PGP PUBLIC KEY BLOCK- I have tried looking for a reason why this might be and my hypothesis is that the key server software is determining my public key based on it's coding and hence the differences. Have I mucked something up somewhere? Thanks for any suggestions or pointers to information. I appreciate it. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: My public key block appears different on keyservers
On Jul 1, 2009, at 9:05 AM, Matt Gantner wrote: Hello. I have uploaded my public key (GnuPG v2.0.10 (Darwin)) via command line and copy / paste methods into keys.gnupg.net and pgpkeys.mit.edu and when I look up the key on the systems they are different. I have been looking at this problem for a few days and uploading my keys to servers. So far none have shown me the same key that I produce on my machine. Not a bug or a problem. OpenPGP keys can be represented in many different, but functionally equivalent, ways. Different keyservers may choose different packet length types, etc. In your particular case, it looks like they just chose different places to place line breaks in the ascii output. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: My public key block appears different on keyservers
On Wed, Jul 1, 2009 at 10:15 PM, David Shaw wrote: > Not a bug or a problem. OpenPGP keys can be represented in many different, > but functionally equivalent, ways. Different keyservers may choose > different packet length types, etc. In your particular case, it looks like > they just chose different places to place line breaks in the ascii output. Hi David, that newline-placement was my first guess, but a closer look at the final three bytes (is that a CRC checksum ?) seems to tell a different story... Maybe the packet lengths are different? I know hardly anything about that detail > > David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Helping a friend setting up with gpg and gpgoe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I got my friend to install WinPT which seems to include GnuPG. He created his keypair. He received my key and signed my key. He sent me my key back and he also sent me his key which I then signed and sent back to him. So far, so good. When he tried to send me a test message that was encrypted and signed, I had a problem. gpg command line and output:,/usr/bin/gpg2 --charset utf8 --batch --no-tty - --status-fd 2 -d --use-agent ,gpg: CRC error; 75B297 - DC375B,gpg: quoted printable character in armor - probably a buggy MTA has been used I then took the message and put it in its own file and re-ran the command: /usr/bin/gpg2 --charset utf8 --batch --no-tty --status-fd 2 -d \ --use-agent < msg Here's the output: [GNUPG:] ENC_TO 365AF334C8DCF2FD 16 0 [GNUPG:] USERID_HINT 365AF334C8DCF2FD Steven W. Orr [GNUPG:] NEED_PASSPHRASE 365AF334C8DCF2FD 448572E1F0BE3724 16 0 [GNUPG:] GOOD_PASSPHRASE gpg: encrypted with 2048-bit ELG key, ID C8DCF2FD, created 2009-05-01 "Steven W. Orr " [GNUPG:] BEGIN_DECRYPTION [GNUPG:] PLAINTEXT 62 1246469472 [GNUPG:] PLAINTEXT_LENGTH 5 ouyeegpg: Signature made Wed Jul 1 13:31:12 2009 EDT using DSA key ID 2DEAE0D9 [GNUPG:] SIG_ID 66jyI28aSXZdKfZZHPYxaaB6rxI 2009-07-01 1246469472 [GNUPG:] GOODSIG $fingerprint_and_address gpg: Good signature from $address [GNUPG:] VALIDSIG 39D66598BCB7627A7C232C3069F3AAFF2DEAE0D9 2009-07-01 1246469472 0 4 0 17 2 00 39D66598BCB7627A7C232C3069F3AAFF2DEAE0D9 [GNUPG:] TRUST_FULLY [GNUPG:] DECRYPTION_OKAY [GNUPG:] GOODMDC [GNUPG:] END_DECRYPTION Is there something obvious that he needs to do? Does he have to send 7-bit ASCII? I'm not sure how to proceed. TIA - -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkpLsqYACgkQRIVy4fC+NyRYzwCfe54jIJeeOov4uCPLe9bZqc0k 1PUAn2LcDLCV9kmkoaoxEX6yTnCMRlrh =YPfP -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Anyone afraid of quantum computer?
Hello, its more a curiosity for me now, but I remember one university lecturer saying, that successful quantum computer would make public key cryptography useless. Some experiment here: http://www.physorg.com/news165418586.html Opinions on if we are likely to experience it, the public key demise? K. signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Anyone afraid of quantum computer?
Kārlis Repsons wrote: > Opinions on if we are likely to experience it, the public key demise? Our largest superpositional computer can store about five qubits. We'd need to hit about 5000 qubits before public key cryptography would be in trouble, and about 1 qubits before it would be in a lot of trouble. Once you see IBM put together a 3000-qubit computer, then will be the time to start worrying about public-key cryptography. At present, superpositional computation is science fiction. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Anyone afraid of quantum computer?
On Jul 1, 2009, at 12:26 PM, Kārlis Repsons wrote: Hello, its more a curiosity for me now, but I remember one university lecturer saying, that successful quantum computer would make public key cryptography useless. Some experiment here: http://www.physorg.com/news165418586.html Opinions on if we are likely to experience it, the public key demise? More practically, harnessing the GPU's via something like OpenCL is probably closer to reality. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpg2 does not detect smart card adapter
Hi! I am using the OpenPGP Card with a "Gemplus GemPC Twin 00 00" smart card adapter and it works fine with gnupg 1. But gnupg 2 does not find my smart card adapter and tells me "OpenPGP Karte ist nicht vorhanden: Umbekanntes IPC Kommando" (OpenPGP card ist not available: unknown IPC command). My system is Ubuntu and I used its gnupg(1) and gnupg2 packages. Also removing libccid and pcscd did not help. Any idea how to fix it? ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Solved: Helping a friend setting up with gpg and gpgoe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/01/09 15:01, quoth Steven W. Orr: > I got my friend to install WinPT which seems to include GnuPG. He created his > keypair. He received my key and signed my key. He sent me my key back and he > also sent me his key which I then signed and sent back to him. So far, so > good. > > When he tried to send me a test message that was encrypted and signed, I had a > problem. > > gpg command line and output:,/usr/bin/gpg2 --charset utf8 --batch --no-tty > --status-fd 2 -d --use-agent ,gpg: CRC error; 75B297 - DC375B,gpg: quoted > printable character in armor - probably a buggy MTA has been used > > I then took the message and put it in its own file and re-ran the command: > > /usr/bin/gpg2 --charset utf8 --batch --no-tty --status-fd 2 -d \ > --use-agent < msg > > Here's the output: > > [GNUPG:] ENC_TO 365AF334C8DCF2FD 16 0 > [GNUPG:] USERID_HINT 365AF334C8DCF2FD Steven W. Orr > [GNUPG:] NEED_PASSPHRASE 365AF334C8DCF2FD 448572E1F0BE3724 16 0 > [GNUPG:] GOOD_PASSPHRASE > gpg: encrypted with 2048-bit ELG key, ID C8DCF2FD, created 2009-05-01 > "Steven W. Orr " > [GNUPG:] BEGIN_DECRYPTION > [GNUPG:] PLAINTEXT 62 1246469472 > [GNUPG:] PLAINTEXT_LENGTH 5 > ouyeegpg: Signature made Wed Jul 1 13:31:12 2009 EDT using DSA key ID > 2DEAE0D9 > [GNUPG:] SIG_ID 66jyI28aSXZdKfZZHPYxaaB6rxI 2009-07-01 1246469472 > [GNUPG:] GOODSIG $fingerprint_and_address > gpg: Good signature from $address > [GNUPG:] VALIDSIG 39D66598BCB7627A7C232C3069F3AAFF2DEAE0D9 2009-07-01 > 1246469472 0 4 0 17 2 00 39D66598BCB7627A7C232C3069F3AAFF2DEAE0D9 > [GNUPG:] TRUST_FULLY > [GNUPG:] DECRYPTION_OKAY > [GNUPG:] GOODMDC > [GNUPG:] END_DECRYPTION > > Is there something obvious that he needs to do? Does he have to send 7-bit > ASCII? I'm not sure how to proceed. > > TIA > I was able to solve the problem. I'm replying to the list for everyone and for all future generations. He was sending text and html as separate attachments. For reasons that are not completely clear to me, I was able to verify and decrypt the message from inside Thunderbird/Enigma by selecting: View->Message Body As->Plain text. So, people shou7ld always *send* plain text, but in case they don't, this trick may help the situation. - -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkpME+0ACgkQRIVy4fC+NySB1ACePLJLgztm8GpjRX9a1PQPPziy fz4AniWMr9tBxdOyvImLfobLB7w/gcRk =Za8J -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Solved: Helping a friend setting up with gpg and gpgoe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Steven W. Orr wrote: > He was sending text and html as separate attachments. For reasons that are > not completely clear to me, I was able to verify and decrypt the message from > inside Thunderbird/Enigma by selecting: View->Message Body As->Plain text. > > So, people shou7ld always *send* plain text, but in case they don't, this > trick may help the situation. This is because switching Thunderbird's View Setting to Plaintext is actually telling the MUA to 'convert' to plaintext which strips out _all_ HTML character encoding. This is a Thunderbird Setting and not an Enigmail Setting. It is for the benefit of folks who desire to never Open HTML Email. JOHN ;) Timestamp: Wednesday 01 Jul 2009, 23:08 --400 (Eastern Daylight Time) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10-svn5046: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKTCTXAAoJEBCGy9eAtCsPoO8H/1EUcR1bM1qA2cO8jddAY64J MEMIMZrHduS2qEVaE82AJa6P2Uv4eI8WVa9IZYWIYNHR/K1BKVqG5bRk8YYXNxWB 2xy+Jb5Ks8qI+8xYtLi11OkOp6Y8Bb3WU9K9emKCAe7+SKP+cUQarIsnTYvPLk/J gjqaLlHJKl8X3O8dpSQRwA9pO8HCmw+fIlWuH22cNHOtl5jb5hy//+9OpKctSsHX ZSh2eassbQrMJC8pN/1Q8Jv9WPXDlmf9xJZnmQVMyOkgT5SBQlIziRwKRZqxh2Ca A0EymtlDbVVyOc8EeBF6EMDCVo+SDFRXv7ejBkmjXViaFr3DIPKW+KGlAs9Z6Zk= =SRbn -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
