From: geoff@collyer.net
To: micah@stetsonnet.org, 9fans@cse.psu.edu
Subject: Re: [9fans] Secure ftp Again
Date: Sun, 3 Apr 2005 21:32:19 -0700 [thread overview]
Message-ID: <77158a75ac9ee53bb9de3e5763b11f16@collyer.net> (raw)
In-Reply-To: <b3b4f6f305040320013c9864a9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
Avoiding this was sort of thing was surely part of the motivation for
IPsec, but presotto points out (I hope I'm not misrepresenting him)
that implementing IPsec, at least in the kernel, is messy, requiring
lots of state and the ability to interrupt and restart cryptographic
computations at awkward times. I've wondered off and on if it might
be feasible and cleaner in a user-mode file server. tcpmux (rfc 1078)
looks easier in user-land.
[-- Attachment #2: Type: message/rfc822, Size: 3266 bytes --]
From: Micah Stetson <micah.stetson@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Secure ftp Again
Date: Sun, 3 Apr 2005 20:01:30 -0700
Message-ID: <b3b4f6f305040320013c9864a9@mail.gmail.com>
> But the trend is towards negotiating TLS after chatting over the
> connection a bit. IMAP, SMTP, and POP all have a separate command to
Let's implement Transport Layer Security inside all our application
layer protocols!
Micah
next prev parent reply other threads:[~2005-04-04 4:32 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
2005-04-04 4:32 ` geoff [this message]
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=77158a75ac9ee53bb9de3e5763b11f16@collyer.net \
--to=geoff@collyer.net \
--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).