Signature Question

[Clough, Samuel (USPC.PRG.Atlanta)]

To clarify I was signing a file as I was encrypting it.  I'm not sure
what sample I could provide besides the prints to standard out.

-----Original Message-----
From: David Shaw [mailto:dshaw at jabberwocky.com] 
Sent: Monday, September 15, 2008 6:26 PM
To: Clough, Samuel (USPC.PRG.Atlanta)
Cc: gnupg-users at gnupg.org
Subject: Re: Signature Question

On Sep 15, 2008, at 9:22 AM, Clough, Samuel (USPC.PRG.Atlanta) wrote:

> We recently moved our gpg processes from one server to another.  On  
> the new server, I installed the latest gpg build.  After that, one  
> vendor starting saying the signature on our files was bad.  I  
> checked and checked and gpg declared we were still signing them.  I  
> checked the gpg output between the old and new servers and found  
> that the new server was saying DSA/SHA signature applied whereas the  
> old version simply said DSA signature applied.  I rolled back to the  
> older version (1.2.1) and the vendor reported that our signatures  
> looked good.  I haven't seen anything in the notes or man page about  
> different signature methods.  Could someone explain to me what  
> changed with signing files?

Not enough information to say.  Please show an example of an old  
signature, and a new signature.  It has nothing to do with "DSA" or  
"DSA/SHA".  That's just a human-readable message.  Unless you did  
special configuration, all DSA signatures are DSA/SHA.

David 
--------------------------------------------------------

Princeton Retirement Group, Inc - Important Terms 
This E-mail is not intended for distribution to, or use by, any person or entity in any location where such distribution or use would be contrary to law or regulation, or which would subject Princeton Retirement Group, Inc. or any affiliate to any registration requirement within such location. 
This E-mail may contain privileged or confidential information or may otherwise be protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by any mistransmission. Access, copying or re-use of information by non-intended or non-authorized recipients is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail. 
The transmission and content of this E-mail cannot be guaranteed to be secure or error-free. Therefore, we cannot represent that the information in this E-mail is complete, accurate, uncorrupted, timely or free of viruses, and Princeton Retirement Group, Inc. cannot accept any liability for E-mails that have been altered in the course of delivery. Princeton Retirement Group, Inc. reserves the right to monitor, review and retain all electronic communications, including E-mail, traveling through its networks and systems (subject to and in accordance with local laws). If any of your details are incorrect or if you no longer wish to receive mailings such as this by E-mail please contact the sender by reply E-mail. 

--------------------------------------------------------