Side note: I use mutt with gmail imap and have no problem whatsoever. http://wiki.linuxwall.info/doku.php/en:ressources:astuces:mu...
3,020 karma · joined March 15, 2010
https://signal.me/#eu/tJgEd9pEdyiankVrQI3j1y2n5jPNLW7y4cZ09RJ0Vhjh2mihvq9IwL6toyfg8Kma
Side note: I use mutt with gmail imap and have no problem whatsoever. http://wiki.linuxwall.info/doku.php/en:ressources:astuces:mu...
Expertise takes focus and time. At some point, you have to make a choice between knowing a bit of everything, or knowing one thing very well. There is no bad choice, both are valid careers.
That, plus excellent PGP support, just makes mutt a much better email client that any other existing ones, local or web.
Agent forwarding sharing is a big one though. Getting people to stop doing that automatically takes a lot of education. https://wiki.mozilla.org/Security/Guidelines/OpenSSH#SSH_age...
Of course, doing everything is much better.
$ ./cipherscan united.com
prio ciphersuite protocols pfs curves
1 RC4-SHA TLSv1,TLSv1.1,TLSv1.2 None NoneNo. It is not. Windows still sells millions of computers and everyone uses it, from households to corporations. It's here to stay for a very long time.
With Vault, you still need to figure out how to push secret zero (here a client authentication token). If you can solve that, why not push the secret you need to push directly, and bypass Vault entirely?
Netflix really needs sendfile() to work with TLS to enable HTTPS on all of its traffic, so they added some limited crypto support to the BSD kernel. What that paper really demonstrates is the need for a TLS stack in the kernel that can let userspace daemons benefit from low-level optimizations. I, for one, would love to see something like this added to the linux kernel!
This is great work from Netflix. They could have just said "screw it, it's too hard/expensive, we'll do HTTP". But instead they listened to a minority of their users that really cares about privacy and dedicated time and resources to fixing a hard problem. Really impressive work!
I'd note that many of us don't have a choice and must still use 1024 bits DHE parameters because of java 6 clients. It's unfortunate, and we hope they go away very very soon so we can upgrade to 2048 bits.
$ ./cipherscan jve.linuxwall.info
........................
Target: jve.linuxwall.info:443
prio ciphersuite protocols pfs curves
1 ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 ECDH,P-384,384bits secp384r1
2 ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 ECDH,P-384,384bits secp384r1
3 DHE-RSA-AES128-GCM-SHA256 TLSv1.2 DH,2048bits None
4 DHE-RSA-AES256-GCM-SHA384 TLSv1.2 DH,2048bits None
5 ECDHE-RSA-AES128-SHA256 TLSv1.2 ECDH,P-384,384bits secp384r1
6 ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2 ECDH,P-384,384bits secp384r1
7 ECDHE-RSA-AES256-SHA384 TLSv1.2 ECDH,P-384,384bits secp384r1
8 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2 ECDH,P-384,384bits secp384r1
9 DHE-RSA-AES128-SHA256 TLSv1.2 DH,2048bits None
10 DHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2 DH,2048bits None
11 DHE-RSA-AES256-SHA256 TLSv1.2 DH,2048bits None
12 DHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2 DH,2048bits None
13 AES128-GCM-SHA256 TLSv1.2 None None
14 AES256-GCM-SHA384 TLSv1.2 None None
15 AES128-SHA256 TLSv1.2 None None
16 AES256-SHA256 TLSv1.2 None None
17 AES128-SHA TLSv1,TLSv1.1,TLSv1.2 None None
18 AES256-SHA TLSv1,TLSv1.1,TLSv1.2 None None
19 DHE-RSA-CAMELLIA256-SHA TLSv1,TLSv1.1,TLSv1.2 DH,2048bits None
20 CAMELLIA256-SHA TLSv1,TLSv1.1,TLSv1.2 None None
21 DHE-RSA-CAMELLIA128-SHA TLSv1,TLSv1.1,TLSv1.2 DH,2048bits None
22 CAMELLIA128-SHA TLSv1,TLSv1.1,TLSv1.2 None None
23 DES-CBC3-SHA TLSv1,TLSv1.1,TLSv1.2 None None
Certificate: trusted, 2048 bit, sha256WithRSAEncryption signature
TLS ticket lifetime hint: 300
OCSP stapling: supported
Cipher ordering: serverThere's a number of edge cases but we can probably find a middle ground that works well enough for the general case.