From: lucio@proxima.alt.za
To: micah@stetsonnet.org, 9fans@cse.psu.edu
Subject: Re: [9fans] Secure ftp Again
Date: Mon, 4 Apr 2005 06:12:31 +0200 [thread overview]
Message-ID: <b64e09307b22983466d2cd9a91838716@proxima.alt.za> (raw)
In-Reply-To: <b3b4f6f305040320013c9864a9@mail.gmail.com>
> Let's implement Transport Layer Security inside all our application
> layer protocols!
I can see the logic in the IESG (thanks, again, Geoff) mandating TLS
as a negotiated layer _and_ I can see the nightmare it gives rise to.
Properly designed, this means there is a single implementation of TLS
(Russ's comments about a TLS-savvy kernel, more likely a kernel module
in the brave new world after Linux) and a reality of each school
implementing it slightly differently and totally incompatibly.
My gut feel is that applying namespace rules (OK!) would alleviate the
nightmare, just as factotum very successfully simplifies a different
aspect of security.
++L
next prev parent reply other threads:[~2005-04-04 4:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 23:11 Gregory Pavelcak
2005-04-03 3:05 ` Russ Cox
2005-04-03 5:05 ` lucio
2005-04-03 13:36 ` Russ Cox
2005-04-03 13:40 ` Devon H. O'Dell
2005-04-03 13:47 ` Russ Cox
2005-04-03 14:17 ` lucio
2005-04-03 23:05 ` geoff
2005-04-03 23:20 ` Russ Cox
2005-04-03 23:57 ` geoff
2005-04-04 1:05 ` geoff
2005-04-04 4:02 ` lucio
2005-04-04 11:57 ` Russ Cox
2005-04-04 2:17 ` Lyndon Nerenberg
2005-04-04 3:01 ` Micah Stetson
2005-04-04 4:12 ` lucio [this message]
2005-04-04 4:32 ` geoff
2005-04-04 11:09 ` C H Forsyth
2005-04-04 11:37 ` boyd, rounin
2005-04-04 11:51 ` Russ Cox
2005-04-04 23:40 ` geoff
2005-04-04 18:56 ` Tim Newsham
2005-04-03 21:06 ` Christoph Lohmann
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=b64e09307b22983466d2cd9a91838716@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
--cc=micah@stetsonnet.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;
as well as URLs for NNTP newsgroup(s).