[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Signed messages

Bill - I also could not read your signed message - it came in with the blue encrypted icon.  When I opened it using a hex editor, it was of course not encrypted - I could actually read your text - but for some reason, Outlook (at least my Outlook - both 2000 and 2003) was interpreting the SMIME package as encrypted and not decoding it properly.  I do experience this problem (very infrequently) with incoming e-mail   I will send a signed e-mail to the listserv shortly using my J&J cert and Outlook 2000 as the client, just for test purposes.  Of course the signature will show up as invalid because you don't have my trusted root (it is publicly available on the internet through an SSL-secure site using a VeriSign cert, URL https://www.jnj.com/jjeds/index.html?secure=true, so don't be surprised when that happens.
 

Richard A. Guida
Director, Information Security

Johnson & Johnson
Room GS8217
410 George Street
New Brunswick, New Jersey  08901
Phone:  732 524 3785

-----Original Message-----
From: owner-ietf-ltans@xxxxxxxxxxxx [mailto:owner-ietf-ltans@xxxxxxxxxxxx]On Behalf Of Bill Russell
Sent: Wednesday, June 14, 2006 10:36 PM
To: ietf-ltans@xxxxxxx
Subject: Signed messages

Has anyone else had any trouble sending signed messages to the listserv?  I noticed Peter's are going through, but two of mine have gone out signed and get distributed as signed/encrypted (which my own client can't even read).  I'm not sure if that is a product of using an Entrust plug-in rather than native S/MIME for Outlook, but just curious if anyone else has had any similar problems.
 
Thanks,
 

Bill Russell, CISSP, ISSAP

Vice President

Mount Airey Group, Inc.

http://www.mountaireygroup.net

Cell: 571-334-1671

Fax: 703-738-7715