From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: OpenVPN/IPsec - Sweet32: Birthday attacks
Date: Mon, 29 Aug 2016 17:50:23 +0200 [thread overview]
Message-ID: <4A108ED6-A3B6-464A-9952-07BD7226059E@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi all,
i wanted to report a cross-site scripting vulnerability problem for OpenVPN and possibly also IPSec via the "SWEET32: Birthday attacks on 64-bit block ciphers which concerns the DES cipher incl. the 3DES variants but also the Blowfish cipher. The only way to fix it which i have currently recognized is to use other ciphers then those and another way for a faster implementation for OpenVPN is to renegotiate new keys more often. An example can be to use '--reneg-bytes 64000' in the configuration.
So my question is should we delete those ciphers from the OpenVPN/IPsec cipher lists and announce this problem to the community may via the Planet (have announced it already in the IPFire forum for OpenVPN) ?
Some deeper insides causing this problem can be found in here:
- https://sweet32.info/
- https://community.openvpn.net/openvpn/wiki/SWEET32
Greetings,
Erik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next reply other threads:[~2016-08-29 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 15:50 ummeegge [this message]
2016-08-30 6:11 ` IT Superhack
[not found] <90CA43F8-EDD0-4D1B-963F-5E66CCBD3212@ipfire.org>
2016-09-01 19:29 ` R. W. Rodolico
[not found] <EC575481-4F11-4DB6-800E-E2E46E3A1AD0@ipfire.org>
2016-09-10 6:49 ` R. W. Rodolico
2016-09-13 15:00 ` Michael Tremer
2016-09-14 19:04 ` IT Superhack
2016-09-15 11:06 ` Michael Tremer
[not found] <79F11CDE-1805-4EE3-8CF2-44A37BA39AE4@ipfire.org>
2016-09-15 11:13 ` Michael Tremer
2016-09-16 9:55 ` ummeegge
2016-11-12 10:04 ` 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=4A108ED6-A3B6-464A-9952-07BD7226059E@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