BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Good and Bad Crypto
- Subject: [Discuss] Good and Bad Crypto
- From: tmetro+blu at gmail.com (Tom Metro)
- Date: Tue, 22 Apr 2014 16:15:23 -0400
- In-reply-to: <53567FBD.4010101@gmail.com>
- References: <14b5446b65314ece8402914040d7efb6@CO2PR04MB684.namprd04.prod.outlook.com> <5355DA7B.4070600@gmail.com> <53567FBD.4010101@gmail.com>
Richard Pieri wrote: > Google's methodology has not to my knowledge been publicized. Correct. >Tom Metro wrote: >> Source code analysis has the potential to find these, if the code is >> analyzed. Back-box testing will find them only if you are very lucky. > > This is laughably false. If it were even the least bit true then > Microsoft Windows would be the most secure operating system on Earth > because the code isn't available for scrutiny. What's laughable is that you write that on the same day that you chastised someone in another thread for "you taking a phrase out of context." Anyone who read this thread will recall that my comments were in the context of a certain class of errors. -Tom -- Tom Metro The Perl Shop, Newton, MA, USA "Predictable On-demand Perl Consulting." http://www.theperlshop.com/
- Follow-Ups:
- [Discuss] Good and Bad Crypto
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Good and Bad Crypto
- References:
- [Discuss] Good and Bad Crypto
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] Good and Bad Crypto
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] Good and Bad Crypto
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Good and Bad Crypto
- Prev by Date: [Discuss] Good and Bad Crypto
- Next by Date: [Discuss] Good and Bad Crypto
- Previous by thread: [Discuss] OpenBSD and LibreSSL
- Next by thread: [Discuss] Good and Bad Crypto
- Index(es):