public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Fix for '--ns-cert-type server is deprecated' .
Date: Tue, 17 Oct 2017 17:52:54 +0200	[thread overview]
Message-ID: <662EFB16-5059-45D4-8C77-404702B06ECC@ipfire.org> (raw)
In-Reply-To: <1508182831.19915.38.camel@ipfire.org>

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

Hi Michael,

> I generally like the idea. However, I am not sure if anyone will know how to use
> this.
this was also one of my concerns, you are probably right that this settings might not be clear for every one.

> Do all OSes support 12k RSA keys?
Have tested it so far on Linux and MAC (also older ones up to 10.7) systems but also in some N2N connections with older boards (JNC9C) where it was no problem. The generation time for the PKI but also for every new generated client grows by the usage of more bits but also the key exchange needs a little longer.

> Or should we rather not make this
> decision for our users and pick the best that works for everyone?
We did that some time ago where we double the bits from 1024 to 2048 (HOST) and 2048 to 4096 (ROOT). The OpenVPN hardening page suggests for a "future system near term use" specified to 10 years, 3072 bit or more --> https://community.openvpn.net/openvpn/wiki/Hardening#X.509keysize . The reference material is from a ENISA report from 2013 which is now also some time ago.

Another interesting topic might be ECC. Since OpenVPN-2.4.x elliptic curve crypto has been introduced whereby the comparison between RSA and ECC seems to be interesting in terms of the different Algorithm-key sizes. Haven´t found the original NSA paper but in here --> http://www.atmel.com/Images/Atmel-8951-CryptoAuth-RSA-ECC-Comparison-Embedded-Systems-WhitePaper.pdf under table one a security comparison can be found.

To get the whole ECC PKI into ovpnmain.cgi might be not so fast done but i think in a not so far future it might be also a standard.

Greetings,

Erik



  reply	other threads:[~2017-10-17 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 13:14 Erik Kapfer
2017-10-06 13:19 ` ummeegge
2017-10-11 10:58   ` Michael Tremer
2017-10-13 14:41     ` ummeegge
2017-10-16 19:40       ` Michael Tremer
2017-10-17 15:52         ` ummeegge [this message]
2017-10-19 15:37           ` 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=662EFB16-5059-45D4-8C77-404702B06ECC@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