Re: [Full-disclosure] nuclear plants reach software quality levels

2011-03-30 Thread Graham Gower
On 30 March 2011 21:53, Peter Osterberg j...@vel.nu wrote: Risk would be a lot higher than 10 percent if it was, say, 300 years since the last tsunami Time to go back to school. Or, perhaps you'd like to come play at my casino... ___

Re: [Full-disclosure] glibc and alloca()

2011-02-25 Thread Graham Gower
On 25 February 2011 18:52, Maksymilian Arciemowicz c...@securityreason.com wrote: Chris Evans scarybeasts at gmail.com writes: Linux distribution might still have vulnerabilities in this area. proftpd use gnu libc implementation http://www.proftpd.org/docs/RELEASE_NOTES-1.3.4rc1  + Updated

Re: [Full-disclosure] OpenBSD has Open Backdoored Software Distribution - admitted by Theo

2010-12-22 Thread Graham Gower
On 23 December 2010 13:54, The Sp3ctacle sp3cta...@gmail.com wrote: It shouldn't be that hard to bindiff the code compiled with with the shipped compiler with the code from a compiler that predates the latest backdoor shenanigans.  You could decompile the binary code and then ask a

Re: [Full-disclosure] Allegations regarding OpenBSD IPSEC

2010-12-15 Thread Graham Gower
On 16 December 2010 09:50, Larry Seltzer la...@larryseltzer.com wrote: Has anyone read this yet? http://www.downspout.org/?q=node/3 Seems IPSEC might have a back door written into it by the FBI? Surely the thing to do now is not to audit *your own* OpenBSD code, but to audit the OpenBSD

Re: [Full-disclosure] OpenBSD IPSEC has backdoor

2010-12-14 Thread Graham Gower
On 15 December 2010 12:05, musnt live musntl...@gmail.com wrote: Original e-mail is from Theo DeRaadt Is my question: Why is now Theo cower like rat. Is because his stance from the beginning: we is audit everything for make me believe Theo was is also on the payroll. Enjoy everyone. I have