Cat Okita wrote:
On Sat, 21 Feb 2009, Peter Gutmann wrote:
This points out an awkward problem though, that if you're a commercial
vendor
and you have a customer who wants to do something stupid, you can't
afford not
to allow this. While my usual response to requests to do things
insecurely
On Tue, 17 Feb 2009, James Hughes wrote:
I find this conversation off the point. Consider other trades like
woodworking. There is no FAQ that can be created that would be applicable to
building a picture frame, dining room table or a covered bridge. A FAQ for
creating a picture frame would be
On Sat, 21 Feb 2009, Peter Gutmann wrote:
This points out an awkward problem though, that if you're a commercial vendor
and you have a customer who wants to do something stupid, you can't afford not
to allow this. While my usual response to requests to do things insecurely is
If you want to
Ben Laurie b...@links.org writes:
I totally agree, and this is the thinking behind the Keyczar project (
http://www.keyczar.org/):
If we're allowed to do self-promotion I'll have to mention cryptlib, which had
as one of its principal design goals what was later stated by Ian Grigg as
there
Stephan Neuhaus wrote:
Yes, there's a need for a crypto practices FAQ to which one can refer.
I disagree because you cannot force developers to read (and understand)
these FAQs. Instead, there is a need for APIs that are difficult to use
in an insecure way. For example, Peter Gutmann's
Stephan Neuhaus wrote:
Many mistakes in crypto coding come from the fact that API developers
have so far very successfully shifted the burden of secure usage to the
application developer, the API user. But I believe this hasn't worked
and needs to be changed.
I totally agree, and this is the
On Feb 14, 2009, at 12:54 PM, David Molnar wrote:
Ben Laurie wrote:
[snip discussion of bad crypto implementation practices]
Because he is steeped in the craft
knowledge around crypto. But most developers aren't. Most developers
don't even have the right mindset for secure coding, let alone
Ben Laurie wrote:
[snip discussion of bad crypto implementation practices]
Because he is steeped in the craft
knowledge around crypto. But most developers aren't. Most developers
don't even have the right mindset for secure coding, let alone correct
cryptographic coding. So, why on Earth do
