From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: decrypting S/MIME messages
Date: Sun, 29 Jul 2001 09:44:49 -0500 [thread overview]
Message-ID: <q6mhevvdcbi.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <eyae1nsxdg.fsf@vsu.ru> (Vladimir Volovich's message of "Sun, 29 Jul 2001 17:00:59 +0400")
>>>>> On Sun, 29 Jul 2001 17:00:59 +0400,
>>>>> Vladimir Volovich <vvv@vsu.ru> (vv) writes:
vv> Maybe, such arguments should not be added unconditionally, but better
vv> via some variable (e.g. smime-openssl-rand-argument) which defaults to
vv> nil but could be set to "/etc/entropy" or whatever.
My brain is so scattered. I can't find the reference now, but I
recall reading that openssl will at some future release by default
check for the existence of /var/run/egd-pool if /dev/random can't be
found.
--
Amos
next prev parent reply other threads:[~2001-07-29 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 16:26 Vladimir Volovich
2001-07-28 2:29 ` Simon Josefsson
2001-07-29 1:13 ` Simon Josefsson
2001-07-29 13:00 ` Vladimir Volovich
2001-07-29 14:44 ` Amos Gouaux [this message]
2001-07-29 20:14 ` Simon Josefsson
2001-07-30 9:39 ` Vladimir Volovich
2001-07-30 22:26 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q6mhevvdcbi.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).