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: Thu, 19 Oct 2017 17:37:15 +0200	[thread overview]
Message-ID: <599A9F23-E506-430E-8669-C4D08BB8EEB2@ipfire.org> (raw)
In-Reply-To: <662EFB16-5059-45D4-8C77-404702B06ECC@ipfire.org>

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

Have found an interesting report causing key lengths and their possible counter value --> https://www.heise.de/security/meldung/Hunderttausende-Infineon-Sicherheits-Chips-weisen-RSA-Schwachstelle-auf-3864691.html?wt_mc=rss.security.beitrag.atom .

If RSA 1024 is about 40 - 80 Dollars worth but RSA 2048 belongs from 20k to 40k which seems to be the today disposal values regarding that report, it might be interesting what happens with 4096 or 8192 :-) .

Only as a short beside tweet.

All the best,

Erik

      reply	other threads:[~2017-10-19 15:37 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
2017-10-19 15:37           ` ummeegge [this message]

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=599A9F23-E506-430E-8669-C4D08BB8EEB2@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