Hi, I apologize for the PGP snafu caused by my email being word wrapped subsequent to signing (if you manually remove all the errant line wraps, it should validate correctly) and also this being a new key for Intrusec as it is the first alert released
You can verify the newest information relating to this alert on our web page at http://www.intrusec.com/55808.html, and I promise to improve our signing, key distribution, and posting process before our next alert. -Dave ------------------- David J. Meltzer [EMAIL PROTECTED] CTO, Intrusec, Inc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2003 6:59 AM To: David J. Meltzer; [EMAIL PROTECTED] Subject: Re: [Full-Disclosure] Intrusec 55808 Trojan Analysis Hello David, +++++++++++++++++++++++++++++ gpg: armor header: Hash: SHA1 gpg: original file name='' gpg: armor header: Version: GnuPG v1.2.2 (MingW32) gpg: Signature made 06/19/03 21:24:53 using DSA key ID F55C043B gpg: requesting key F55C043B from x-hkp://sks.keyserver.penguin.de gpg: armor header: Version: SKS 1.0.3 gpg: pub 1024D/F55C043B 2003-06-19 Intrusec, Inc. <[EMAIL PROTECTED]> gpg: key F55C043B: public key "Intrusec, Inc. <[EMAIL PROTECTED]>" imported gpg: Total number processed: 1 gpg: imported: 1 gpg: BAD signature from "Intrusec, Inc. <[EMAIL PROTECTED]>" gpg: textmode signature, digest algorithm SHA1 +++++++++++++++++++++++++++++ Same here; bad signature -- Best regards, slpl <mailto:[EMAIL PROTECTED]> _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
