[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnutls-dev] GnuTLS vs OpenSSL vs NSS
From: |
Simon Josefsson |
Subject: |
Re: [gnutls-dev] GnuTLS vs OpenSSL vs NSS |
Date: |
Thu, 28 Jun 2007 11:48:55 +0200 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/22.0.95 (gnu/linux) |
Thanks for the additional information, I updated the page again.
(Although for some reason the gnu.org web pages aren't updated, but the
change is available from http://josefsson.org/gnutls/comparison.html
meanwhile.)
/Simon
Robert Relyea <address@hidden> writes:
> Sigh trying to keep up with email.
>
>
> thanks simon for updating the table..
>
> Simon Josefsson wrote:
>> address@hidden writes:
>>
>>
>>> Under portability concerns, NSS should read:
>>>
>>> NSS Platform requirements - NSPR* Network requirements - NSPR* thread
>>> safety- NSPR* (uses native platform threads when available, provides
>>> thread implementation if f necessary) Random Seed - set through native
>>> OS API, extra entropy grab from installed PKCS #11 modules,
>>> application can also add entropy on the fly
>>>
>>
>> Added most of it, but I don't understand the last part -- how is the
>> random seed set through a 'native OS API'? Does this refer to some NSPR
>> API? Or what OS APIs do you mean? I'm not aware of any standard APIs
>> for setting random seeds.
>>
> There isn't a standard API. For Unix/Linux it uses /dev/urandom if
> available, for Windows it uses CAPI. For all platforms it gets data
> from clock, and tries to open system files. NSS has a set of platform
> dependent functions is uses to determine randomness. You are right,
> they probably should live in NSPR.
>
> bob
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [gnutls-dev] GnuTLS vs OpenSSL vs NSS,
Simon Josefsson <=