[cryptography] Web Cryptography API (W3C Working Draft 8 January 2013)

yersinia yersinia.spiros at gmail.com
Sun Mar 10 16:34:34 EDT 2013


On Sun, Mar 10, 2013 at 6:58 PM, ianG <iang at iang.org> wrote:

> On 10/03/13 20:25 PM, yersinia wrote:
>
>> On Sun, Mar 10, 2013 at 12:20 PM, D. J. Bernstein <djb at cr.yp.to
>> <mailto:djb at cr.yp.to>> wrote:
>>
>>     Ryan Sleevi writes:
>>      > What use case makes the "NaCl" algorithms (whose specification is
>>     merely
>>      > 'use NaCl', which boils down to "Use Salsa+Curve25519") worthwhile?
>>
>>
>>     Of course, this doesn't imply that NaCl is what developers want, but
>>     high-profile applications such as DNSCrypt are in fact using NaCl in
>>     ways that seem easily generalizable to other applications.
>>
>>
>> There are linux distributions that do not consider or cite NaCl. If an
>> Open Source developer did not follow other sources of discussion he not
>> would know it. I dunno why. Perhaps it is due to the FIFS 140. I am
>> sorry if the observation is OT.
>>
>
>
> One would hope that someone would put a little more thought into crypto
> than "it's available in Linux...."
>
>
> You are certainly right. Many operating systems are perhaps too much
conservative in their security systems, encryption is no exception. But the
spread of good libraries like Naci, in commercial  or open source product,
requires more effort from everyone. It is not so simple.

>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.randombit.net/pipermail/cryptography/attachments/20130310/61eeda43/attachment.html>


More information about the cryptography mailing list