From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Cryptography
Date: Thu, 06 Feb 2014 14:52:49 +0100 [thread overview]
Message-ID: <1391694769.21794.92.camel@rice-oxley.tremer.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Hello list,
since Snowden, there is a lot going on about cryptography as he said
that nothing else will help against mass surveillance than strong
cryptography.
IPFire provides a lot of services that use (strong) cryptography like
the VPN services OpenVPN and strongswan and some others like tor.
We can do a lot so that users are able to use these services in the most
secure manner, but I think with that comes is still some education about
the DOs and DON'Ts needed.
So I was thinking that it would be nice to create a section on our wiki
about cryptography and to aggregate all information that is important to
know at one spot. We can refer to the content from the OpenVPN and IPsec
pages for example to suggest which cipher is best to use.
I created some pages about hardware random number generators and
hardware crypto processors that are commonly used and supported by
IPFire. Additionally to that, I can image to add things like these:
* 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.
* Provide best practices to protect keys, etc. Explain what attacks are
possible so that people can prepare for them.
I don't want to this to be a huge part of the documentation and this is
probably documented somewhere else very well, but I would like to have
the basics in our wiki. Detailed explanations should be referenced and
not copied.
This is all to see over here:
http://wiki.ipfire.org/en/cryptography/start
Of course I would like to hear your opinions (if there is anybody out
there)!
-Michael
next reply other threads:[~2014-02-06 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 13:52 Michael Tremer [this message]
2014-02-06 14:15 ` Cryptography Tom Rymes
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=1391694769.21794.92.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--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