[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <005301c22f2a$a0743f20$0aaca5c2@vitalograph.ie>
From: fulldisclose at uuuppz.com (James Martin)
Subject: Symantec Buys SecurityFocus, among others....
> Release exploits with the vaguest of descriptions as to how they work
> (lost for examples -- just copy'n'paste the "technical bits" of some
> of the security bulletins from MS...). Have the _only_ PoC code a
> compiled binary loaded with copyright notices forbidding reversing,
> etc. Be sure to use some "encryption" (extremely trivial is OK as
> complexity doesn't matter; can you say XOR?) in the PoC to "protect"
> the important secret (generally the overflow "string" itself). Be
Ummm surely just sniffing the exploit string being sent, will reveal the
string itself in 99% of cases (remote exploits that is). Is watching the
data a program sends across a network reverse engineering??
Regards
James
Powered by blists - more mailing lists