Re: How to 'un-sign' a key?

2009-05-08 Thread Andrew Berg
John W. Moore III wrote: Joel C. Salomon wrote: Folks, I foolishly signed a key I had not verified well, and the signed version is on a keyserver. How can I unsign it? Select the Key with the offending Signature and revoke the Signature. the command is --revsig form the Edit Key

Re: Use other hash than SHA-1

2009-05-08 Thread Raimar Sandner
On Friday 08 May 2009 02:09:31 David Shaw wrote: One fear that I've seen talked about for SHA-1 is that an attacker can create a duplicate document such that if you signed document or key A, they could come up with a document or key B that your signature would equally apply to. That fear is

Re: Use other hash than SHA-1

2009-05-08 Thread Raimar Sandner
On Friday 08 May 2009 09:14:27 Raimar Sandner wrote: On Friday 08 May 2009 02:09:31 David Shaw wrote: One fear that I've seen talked about for SHA-1 is that an attacker can create a duplicate document such that if you signed document or key A, they could come up with a document or key B

Re: Use other hash than SHA-1

2009-05-08 Thread David Shaw
On May 8, 2009, at 3:26 AM, Raimar Sandner wrote: On Friday 08 May 2009 09:14:27 Raimar Sandner wrote: On Friday 08 May 2009 02:09:31 David Shaw wrote: One fear that I've seen talked about for SHA-1 is that an attacker can create a duplicate document such that if you signed document or key

GPG Confirmation

2009-05-08 Thread jnhemley
I was given a new key to use with our partner for encryption. Previously, the key was working fine. I removed all keys and then imported our key and then the partner's key. I set trust to ultimate. The encryption works but I now get a confirmation message.How can I get rid of this confirmation

delete bad UID from key on keyserver?

2009-05-08 Thread Anonymous Remailer
Hi, One of my email accounts is unusable so I deleted the UID from my key and uploaded it to the keyserver. That accomplished nothing so now I figured out I should of invalidated the UID and then uploaded it. I can't do that now because I deleted the UID from my key. I have to get rid of this

gpg: WARNING: standard input reopened

2009-05-08 Thread Patrick Mabie
Hello I was just wondering , can I fix this ? RPM version 4.4.2.3 gnupg-1.4.5-14.x86_64 CentOS 5.3 x86_64 kernel : 2.6.18-128.1.10.el5 rpmbuild -bb Documents/Rpm/Spec/q7z-64.spec --sign Generating signature: 1005 gpg: WARNING: standard input reopened gpg: WARNING: standard input reopened

Re: delete bad UID from key on keyserver?

2009-05-08 Thread John W. Moore III
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Anonymous Remailer wrote: One of my email accounts is unusable so I deleted the UID from my key and uploaded it to the keyserver. That accomplished nothing so now I figured out I should of invalidated the UID and then uploaded it. I can't do

Re: delete bad UID from key on keyserver?

2009-05-08 Thread John Clizbe
Anonymous Remailer wrote: Hi, One of my email accounts is unusable so I deleted the UID from my key and uploaded it to the keyserver. That accomplished nothing so now I figured out I should of invalidated the UID and then uploaded it. I can't do that now because I deleted the UID from my

Cannot Decryption via UNIX shell script

2009-05-08 Thread Bob Yang
Hi All, I hit error when using the below script. gpg -e key file EOF yes EOF Error: It is NOT certain that the key belongs to the person named in the user ID. If you *really* know what you are doing, you may answer the next question with yes Use this key anyway? Does anyone come across this

Re: gpg: WARNING: standard input reopened

2009-05-08 Thread David Shaw
On May 8, 2009, at 3:16 PM, Patrick Mabie wrote: Hello I was just wondering , can I fix this ? RPM version 4.4.2.3 gnupg-1.4.5-14.x86_64 CentOS 5.3 x86_64 kernel : 2.6.18-128.1.10.el5 rpmbuild -bb Documents/Rpm/Spec/q7z-64.spec --sign Generating signature: 1005 gpg: WARNING: standard

Re: GPG Confirmation

2009-05-08 Thread David Shaw
On May 8, 2009, at 10:37 AM, jnhemley wrote: I was given a new key to use with our partner for encryption. Previously, the key was working fine. I removed all keys and then imported our key and then the partner's key. I set trust to ultimate. The encryption works but I now get a