From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] security [was Plan 9 versus CORBA?]
Date: Wed, 26 Sep 2001 11:41:52 -0400 [thread overview]
Message-ID: <200109261541.LAA25577@augusta.math.psu.edu> (raw)
In-Reply-To: <20010925133048.C0B6919A0F@mail.cse.psu.edu>
In article <20010925133048.C0B6919A0F@mail.cse.psu.edu> you write:
>> From: Dan Cross <cross@math.psu.edu>
>> Date: Mon, 24 Sep 2001 22:27:27 -0400 (EDT)
>> ...
>> A lot of people who are putting in, eg, end-to-end
>> crypto are doing so ``temporarily'' until the problems with the
>> wireless LAN are ``fixed.''
>> What's really needed is a holistic approach, ...
>> But, good luck selling that one. :-(
>
>But Plan 9 is deliberately a research system, where we have a chance
>to do it right and live in the system we build.
Yes, but I wasn't really refering to Plan 9 in the original message.
It was more generally about 802.11 installations. Sorry, it was off-
topic and not particularly clear.
>We're working to evolve Plan 9 so all services and protocols are
>sturdy enough to withstand life outside firewalls. We don't want to
>depend on WEP but on end-to-end authentication and encryption where
>needed.
Ooo... That's great.
>Besides the upgrades in explicit security mechanisms for Plan 9,
>we still find and fix buffer overflows occasionally. But there
>are only a few people to work on this at Bell Labs, so I appeal to
>the open source community to apply eyeballs and insight.
I don't think that the buffer overrun problem is really going to
be fixed until security critical software is written in a `safe'
language that's immune to that sort of thing. (Sorry, Dennis!)
But, at anyrate, I'm happy to peek at the code whenever I get a
chance. If nothing else, I've found it a good cure for co-worker-
induced stomach aches. :-)
- Dan C.
prev parent reply other threads:[~2001-09-26 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 13:30 Eric Grosse
2001-09-26 15:41 ` Dan Cross [this message]
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=200109261541.LAA25577@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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).