public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] del_rand: Deletion of RAND file in openssl config
Date: Tue, 29 Jan 2019 13:51:20 +0000	[thread overview]
Message-ID: <7F378D72-5CB1-4911-ABA9-008F72ECF87C@ipfire.org> (raw)
In-Reply-To: <46ec14e20a50fac15924ef1f2dc624882f0d7fbe.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

What is the reason that openssl.cnf is excluded in the updater?

> On 29 Jan 2019, at 13:17, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Just as a reminder cause i haven´t found it in Git, this one might be
> important for the OpenSSL update and IPSec.
> 
> Best,
> 
> Erik
> 
> 
> Am Dienstag, den 08.01.2019, 20:33 +0100 schrieb Erik Kapfer:
>> Fixes #11943
>> 
>> Since the kernel RNG should do this, there is no need for this
>> anymore.
>> 
>> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
>> ---
>> config/ovpn/openssl/ovpn.cnf | 2 --
>> config/ssl/openssl.cnf       | 2 --
>> 2 files changed, 4 deletions(-)
>> 
>> diff --git a/config/ovpn/openssl/ovpn.cnf
>> b/config/ovpn/openssl/ovpn.cnf
>> index 40daf2a0a..96c3dcb09 100644
>> --- a/config/ovpn/openssl/ovpn.cnf
>> +++ b/config/ovpn/openssl/ovpn.cnf
>> @@ -1,5 +1,4 @@
>> HOME				= .
>> -RANDFILE			= /var/ipfire/ovpn/ca/.rnd
>> oid_section			= new_oids
>> 
>> [ new_oids ]
>> @@ -17,7 +16,6 @@ certificate			= $dir/ca/cacert.pem
>> serial				= $dir/certs/serial
>> crl				= $dir/crl.pem
>> private_key			= $dir/ca/cakey.pem
>> -RANDFILE			= $dir/ca/.rand
>> x509_extensions			= usr_cert
>> default_days			= 999999
>> default_crl_days		= 30
>> diff --git a/config/ssl/openssl.cnf b/config/ssl/openssl.cnf
>> index 9d1e6e1ff..3b980fcd4 100644
>> --- a/config/ssl/openssl.cnf
>> +++ b/config/ssl/openssl.cnf
>> @@ -1,5 +1,4 @@
>> HOME		= .
>> -RANDFILE	= /var/tmp/.rnd
>> oid_section	= new_oids
>> 
>> [ new_oids ]
>> @@ -17,7 +16,6 @@ certificate	= $dir/ca/cacert.pem
>> serial		= $dir/certs/serial
>> crl		= $dir/crls/cacrl.pem
>> private_key	= $dir/private/cakey.pem
>> -RANDFILE	= $dir/tmp/.rand
>> x509_extensions	= usr_cert
>> default_days	= 999999
>> default_crl_days= 30
> 


  reply	other threads:[~2019-01-29 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 19:33 Erik Kapfer
2019-01-29 13:17 ` ummeegge
2019-01-29 13:51   ` Michael Tremer [this message]
2019-01-29 13:52     ` Michael Tremer
2019-01-29 15:11       ` ummeegge
2019-01-29 15:44         ` Michael Tremer

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=7F378D72-5CB1-4911-ABA9-008F72ECF87C@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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