From: Tom Rymes <trymes@rymes.com>
To: documentation@lists.ipfire.org
Subject: Re: Cryptography
Date: Thu, 06 Feb 2014 09:15:09 -0500 [thread overview]
Message-ID: <52F398ED.2080901@rymes.com> (raw)
In-Reply-To: <1391694769.21794.92.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On 02/06/2014 8:52 AM, Michael Tremer wrote:
<snip>
> * Briefly(!) explain the algorithms there are and point out advantages
> and disadvantages. Of course can never give advice to use exactly this
> algorithm, but we can say which are considered unsafe to use.
<snip>
Michael,
This isn't documentation-related, but is relevant tot he subject you
brought up. Perhaps it would be worthwhile to change the user interface
to add an element that requires a user to "Enable insecure encryption
methods" before using protocols that are considered weak?
That way a user could still use those methods if required for
interoperability, but it would be clear that it is not recommended for
security reasons.
Tom
next prev parent reply other threads:[~2014-02-06 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 13:52 Cryptography Michael Tremer
2014-02-06 14:15 ` Tom Rymes [this message]
2014-02-06 14:25 ` Cryptography Michael Tremer
2014-02-07 10:58 ` Cryptography ummeegge
2014-02-08 14:37 ` Cryptography Michael Tremer
2014-02-09 20:59 ` Cryptography ummeegge
2014-02-06 14:25 ` Cryptography 5p9
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=52F398ED.2080901@rymes.com \
--to=trymes@rymes.com \
--cc=documentation@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