From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] encrypting 9P traffic
Date: Thu, 28 Jul 2011 11:34:12 +0200 [thread overview]
Message-ID: <20110728113412.12b929f4@wks-ddc.exosec.local> (raw)
In-Reply-To: <870be0732e4f6bb93ca5798f1aa65231@terzarima.net>
> >Yes, but like you said earlier, it's SSLv2, not SSLv3.
>
> what's the advantage of using v3 for plan 9 connections?
> plan 9 uses only the record format of v2.
exportfs, import and cpu are the three last commands still using
devssl. When they will be migrated to devtls, devssl could be
definitely removed.
HTTP, SMTP, IMAP, POP and others already use both TLS 1.0 handshake
and record protocols.
It's easier to maintain a single encryption protocol than two.
Moreover, if you want to interact with foreign implementations,
they often don't implement SSL 2.0 anymore, or, at best, only
support the standard and weak ciphers of SSL 2.0, and not
the newest ones, standardized in TLS 1.0, 1.1, 1.2 and their
extensions (mostly AES, SHA1 and SHA2).
--
David du Colombier
next prev parent reply other threads:[~2011-07-28 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 23:43 John Floren
2011-07-27 23:49 ` Lyndon Nerenberg
2011-07-27 23:52 ` John Floren
[not found] ` <CAL4LZyjV6VOprS_=uR06TaRrLw8dmW79yhCD5CtFbKjKYR66AQ@mail.gmail.c>
2011-07-28 1:24 ` erik quanstrom
2011-07-28 1:27 ` erik quanstrom
2011-07-28 2:01 ` John Floren
2011-07-28 6:00 ` David du Colombier
2011-07-28 9:02 ` Charles Forsyth
2011-07-28 9:34 ` David du Colombier [this message]
[not found] ` <CAL4LZyiuZjc1MipCpG8uVMKc53Oj0aeyJV7jqzCfVhv7f5qeaQ@mail.gmail.c>
2011-07-28 12:42 ` erik quanstrom
2011-07-28 8:08 ` Steve Simon
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=20110728113412.12b929f4@wks-ddc.exosec.local \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).