From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing core update 123
Date: Tue, 28 Aug 2018 21:00:14 +0200 [thread overview]
Message-ID: <702c4b152abe934ed04bbf1161f31c85bffdc198.camel@ipfire.org> (raw)
In-Reply-To: <002e01d43ef2$2baea2e0$830be8a0$@ministc.com>
[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]
Hi Paul,
an thanks for your feedback. Causing the OpenVPN messages:
Am Dienstag, den 28.08.2018, 18:11 +0100 schrieb Paul Titjen:
> OpenVPN
> Initially had the two crypto warnings so deleted all the cert data
> and then generated new DH parameters with 3076 value. Then generated
> new certificate data using the 3076 value. This removed the DH size
> warning but still leaves the following:
>
> Cryptographic warning
> Your host certificate is not RFC3280 compliant.
> Please update to the latest IPFire version and generate as soon as
> possible a new root and host certificate.
> All OpenVPN clients needs then to be renewed!
>
>
> I looked for any settings that I could apply in web GUI to set
> extendkeyusage with TLS Web Server Authentication in the cert
> generation to make the warning go away but could not find a way to do
> this.
The needed changes are already shipped https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=b66b02ab73863bcb9130300d8ef0eecdc51efde3
. To get the needed changes to your certificates and configuration,
you will need to renew the complete x509 which will also reset all existing clients.
You can find in here https://forum.ipfire.org/viewtopic.php?t=18852#p108144
a more detailed discussion about this topic whereby OpenVPN provides some infos also
in here https://community.openvpn.net/openvpn/wiki/DeprecatedOptions#a--ns-cert-type .
It is time until OpenVPN version 2.5 but ns-cert-type will be dropped then.
>
> + # Warning if certificate is not compliant to RFC3280 TLS
> rules
> + if (-f "${General::swroot}/ovpn/certs/servercert.pem") {
> + my $extendkeyusage = `/usr/bin/openssl x509 -noout
> -text -in ${General::swroot}/ovpn/certs/servercert.pem`;
> + if ($extendkeyusage !~ /TLS Web Server
> Authentication/) {
> + $cryptowarning = "$Lang::tr{'ovpn warning
> rfc3280'}";
> + goto CRYPTO_WARNING;
> + }
> + }
> +
> + CRYPTO_WARNING:
>
> Is OpenVPN going to require critical extends on the certs in the
> future?
Yes, see above.
>
> Hope this somewhat limited testing information helps.
Great, and thanks.
>
> Regards,
> Paul
>
>
>
next parent reply other threads:[~2018-08-28 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002e01d43ef2$2baea2e0$830be8a0$@ministc.com>
2018-08-28 19:00 ` ummeegge [this message]
[not found] <866vg4r1p6qm64uevcf2o7j7.1535490441019@email.android.com>
2018-08-29 5:53 ` ummeegge
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=702c4b152abe934ed04bbf1161f31c85bffdc198.camel@ipfire.org \
--to=ummeegge@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