On Sun, 18 Nov 2007 12:10, [EMAIL PROTECTED] said:
> Indeed. And you should call abort() instead of exit() in the library.
I will consider this.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
* Werner Koch:
> On Thu, 15 Nov 2007 13:19, [EMAIL PROTECTED] said:
>
>> M null c 1 3
>> which creates /dev/null, but does not contain a line to create
>> /dev/random. It also contains the comment:
>
> So the fix should be pretty easy:
>
> M random c 1 8
> M urandom c 1 9
Indeed.
On Thu, 15 Nov 2007, Marco d'Itri wrote:
> On Nov 15, Werner Koch <[EMAIL PROTECTED]> wrote:
>
>> So the fix should be pretty easy:
>>
>> M random c 1 8
>> M urandom c 1 9
> I oppose this "solution", the only devices which *must* be created
> statically (and are available in the standard init
On Thu, 15 Nov 2007 15:32, [EMAIL PROTECTED] said:
> I oppose this "solution", the only devices which *must* be created
> statically (and are available in the standard initramfs indeed) are null
> and console.
With this reasoning you may also change Linux to allow /dev/random to be
a module. It
On Nov 15, Werner Koch <[EMAIL PROTECTED]> wrote:
> So the fix should be pretty easy:
>
> M random c 1 8
> M urandom c 1 9
I oppose this "solution", the only devices which *must* be created
statically (and are available in the standard initramfs indeed) are null
and console.
SSL is not used
On Thu, 15 Nov 2007 13:19, [EMAIL PROTECTED] said:
> M null c 1 3
> which creates /dev/null, but does not contain a line to create
> /dev/random. It also contains the comment:
So the fix should be pretty easy:
M random c 1 8
M urandom c 1 9
Shalom-Salam,
Werner
p.s.
Does
On Thu, 15 Nov 2007, Werner Koch wrote:
> On Thu, 15 Nov 2007 10:55, [EMAIL PROTECTED] said:
>
>> The only way forward I can see from here is to refer the issue to the
>> Technical Committee. If nobody objects or wants to do it themselves
>> I'll write up a summary when I have some free time.
>
>
On Thu, 15 Nov 2007 10:55, [EMAIL PROTECTED] said:
> The only way forward I can see from here is to refer the issue to the
> Technical Committee. If nobody objects or wants to do it themselves
> I'll write up a summary when I have some free time.
I still do not understand the problem. Do you say
On Mon, 5 Nov 2007, Marco d'Itri wrote:
On Nov 05, Werner Koch <[EMAIL PROTECTED]> wrote:
I still do not consider calling exit(2) in a library acceptable under
any condition.
So you want abort () instead? I consider this a bad option in this case
because exit handlers would not be run.
I the
On Nov 05, Werner Koch <[EMAIL PROTECTED]> wrote:
> > I still do not consider calling exit(2) in a library acceptable under
> > any condition.
> So you want abort () instead? I consider this a bad option in this case
> because exit handlers would not be run.
I the function to fail with something
On Mon, 5 Nov 2007 13:37, [EMAIL PROTECTED] said:
> I still do not consider calling exit(2) in a library acceptable under
> any condition.
So you want abort () instead? I consider this a bad option in this case
because exit handlers would not be run.
Given the reluctance of many programmers to
On Nov 05, James Andrewartha <[EMAIL PROTECTED]> wrote:
> As the originator of the Debian bug the point I'm interested in is
> libgcrypt as used by libnss-ldap as used by udevd. If the lack
> of /dev/random during early boot is the true bug here, please reassign
> this bug back to Marco d'Itri and
Hi all,
As the originator of the Debian bug the point I'm interested in is
libgcrypt as used by libnss-ldap as used by udevd. If the lack
of /dev/random during early boot is the true bug here, please reassign
this bug back to Marco d'Itri and the udev package.
Thanks,
James Andrewartha
[please C
On Fri, 2007-11-02 at 11:02 +0100, Werner Koch wrote:
> On Thu, 1 Nov 2007 16:13, [EMAIL PROTECTED] said:
>
> > This is causing a problem for Pidgin as well. [0] If there's no entropy
> > device, then you can't use GnuTLS. However, that shouldn't prevent you
>
> There is a serious problem on you
On Thu, 1 Nov 2007 16:13, [EMAIL PROTECTED] said:
> This is causing a problem for Pidgin as well. [0] If there's no entropy
> device, then you can't use GnuTLS. However, that shouldn't prevent you
There is a serious problem on your system if gnutls and thus libgcrypt
are available but the system
On Mon, 2007-03-05 at 20:33 +0100, Werner Koch wrote:
> On Mon, 5 Mar 2007 19:40, [EMAIL PROTECTED] said:
>
> > in this specific case (libnns-ldap failing due to missing
> > /dev/(u)random devices in early boot when connecting to the ldap
> > server using a ssl protected session.) the only thing
On Mon, 5 Mar 2007 19:40, [EMAIL PROTECTED] said:
> in this specific case (libnns-ldap failing due to missing
> /dev/(u)random devices in early boot when connecting to the ldap
> server using a ssl protected session.) the only thing actually using
> gcrypt directly is gnutls.
You simply can't us
On 2007-03-04 Werner Koch <[EMAIL PROTECTED]> wrote:
> On Sat, 3 Mar 2007 11:10, [EMAIL PROTECTED] said:
> > currently log_fatal() ends up invoking exit(2). Is this really the
> > right thing to do? It does not give applications using libgcrypt any
> Yes. It allows application to run an atexit
18 matches
Mail list logo
