[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <008e01c3371c$0e8a9140$be01a8c0@ian>
From: djm at intrusec.com (David J. Meltzer)
Subject: Intrusec 55808 Trojan Analysis
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
djm@...rusec.com
CTO, Intrusec, Inc.
-----Original Message-----
From: slpl@...info.pt [mailto:slpl@...info.pt]
Sent: Friday, June 20, 2003 6:59 AM
To: David J. Meltzer; full-disclosure@...ts.netsys.com
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.
<security@...rusec.com>
gpg: key F55C043B: public key "Intrusec, Inc. <security@...rusec.com>"
imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: BAD signature from "Intrusec, Inc. <security@...rusec.com>"
gpg: textmode signature, digest algorithm SHA1
+++++++++++++++++++++++++++++
Same here; bad signature
--
Best regards,
slpl <mailto:slpl@...info.pt>
Powered by blists - more mailing lists