full-disclosure - openssl exploit code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3D875E5F.9030005@guninski.com>
From: guninski at guninski.com (Georgi Guninski)
Subject: openssl exploit code

Why don't someone just ask sf to confirm or deny this? (preferrably someone who 
posts to them, probably).

Georgi

Jonathan Rickman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> On Tue, 17 Sep 2002, hellNbak wrote:
> 
> 
>>Source?  URL?  Article?  I personally would be very surprised if this
>>happened.  But stranger things have happened.
> 
> 
> That would certainly account for the noticeable decline in bugtraq
> postings as of late. Could just be a slow month, but I can't recall ever
> seeing bugtraq as quiet as it has been for the last 3 days. Like you, I
> would be somewhat surprised to see a verifiable source for this
> information, but I would not be surprised to learn that this is the new,
> albeit unofficial, policy. Symantec has products out there too. Do you
> really believe that they would allow themselves to be outed, with no
> warning, on their own mailing list before they take time out to prep an
> advisory/fix? I don't. So the bottom line is, we do not have a single
> source for information anymore (assuming we ever have), because we'll
> probably have to look elsewhere for information regarding Symantec
> products...at the very least. Of course, I don't know that they are
> actually taking this stance, but I can't say I'd blame them for taking it
> if they did.
> 
> - --
> Jonathan Rickman
> X Corps Security
> http://www.xcorps.net
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.5.8
> 
> iQEVAwUBPYdRYzTwrX0N9QH/AQGuqgf+IlNolnQdSbbJQe88eETfrL4mWP3w0pt4
> gH+5lH1nr54lNG/XAtSL5nf6sqpgyPcDZOU66qBMD8UfZbe+p5EXqiXD0Oygj3YV
> C9VEy5WDq6Vq8PbW6NMjh9X/3ivckTnCCikLhiytFtUCJUM0Bia6SGD7qiz61qxV
> 8BOJebjCU0zOsLVIztHLEXRSRUwlsv5vKaworUeG7MHnDrVsTSQ6+TjVVey35G7l
> h8c6ELdyKLnGNVL1DiekdLcnLkB44Thjia5gIGvHNlPaZliC3/iaN9iHSp7Fz1EE
> 6Mfeh4Eb/VYKtzG6H2oDE8kCQTKEm49QpDpzRRYKpPuDnh5qWBO4lQ==
> =oJR6
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
> 
>