public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Mark recommended ciphers/algorithms
Date: Wed, 16 Dec 2015 09:06:07 +0100	[thread overview]
Message-ID: <op.x9p8sh1wcahio0@atl-uetersen.atlantisgmbh.local> (raw)
In-Reply-To: <1450214308.31655.190.camel@ipfire.org>

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

>> Weak is weak for every kind of hardware. So +1 for "weak".
>
> If we have "weak". Should we have "broken", too? For example we have to
> support MD5. I wouldn't say that MD5 is weak. It is more than that.

If we need to support it, it should be "broken", yes.


Lars

  reply	other threads:[~2015-12-16  8:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 14:18 [PATCH] Disallow OpenVPN DH params less than 1024 bits IT Superhack
2015-11-24 14:14 ` ue
2015-12-01 22:58   ` Michael Tremer
2015-12-02  9:07     ` IT Superhack
2015-12-02 10:47       ` Michael Tremer
2015-12-02 18:19         ` IT Superhack
2015-12-07 16:35         ` [PATCH] Mark recommended ciphers/algorithms IT Superhack
2015-12-10 17:16           ` Michael Tremer
2015-12-13 15:10             ` IT Superhack
2015-12-13 17:47               ` Larsen
2015-12-15 14:13               ` Michael Tremer
2015-12-15 15:03                 ` Larsen
2015-12-15 21:18                   ` Michael Tremer
2015-12-16  8:06                     ` Larsen [this message]
2015-12-18 16:12             ` IT Superhack
2016-01-01 16:54             ` IT Superhack
2016-01-04 16:31               ` Michael Tremer
2016-01-10 16:29                 ` IT Superhack
2016-01-10 22:22                   ` Michael Tremer
2016-01-02 13:03             ` ue
2016-01-04 16:36               ` 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=op.x9p8sh1wcahio0@atl-uetersen.atlantisgmbh.local \
    --to=larsen007@web.de \
    --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