On Thu, 9 Sep 1999, Julian Elischer wrote:
> I think he wants something like an "inverted chroot"
> (you can see out but others can't see in?
> (into all facets, e.g. process stats, etc.)
Then maybe he should begin by looking at the work Poul-Henning has done
on jail(8) code? Is that what you're suggesting?
>
> julian
>
>
> On Wed, 8 Sep 1999, Chuck Robey wrote:
>
> > On Wed, 8 Sep 1999, Gustavo V G C Rios wrote:
> >
> > > Dear gentleman,
> > >
> > > i am a computer science student, and this semester i had to began my
> > > project to get graduated. After looking for some interesting topics on
> > > many sources, one rised up:
> > > Privacity on Shared Environments.
> > >
> > > My ideia is to add system facilities to improve privacity for users on
> > > shared environment like, for instance, FreeBSD.
> > >
> > > One clear example:
> > > No user(but only that ones previous allowed to) should be able to see
> > > other users process. This facility have to be done at kernel level,
> > > (that's what i think).
> > >
> > > There is many more thing like this, that could improve system privacity.
> > > This would be my cents to FreeBSD Project.
> > >
> > > So, what you think about this project? Is it cool enough to be done? Is
> > > it waste of time? I would really like to have your feedback. Please,
> > > report me something.
> > >
> > > Again: i would really enjoy hearing from you wizards what you have to
> > > say!
> >
> > You have a little problem with our language, and it's making it
> > difficult to tell if you know enough to start hacking. There are
> > already lots of extra security measures on FreeBSD; if you want to
> > research this, and perhaps come up with something extra, you'd certainly
> > want to look at the "pam" facility (man pam), which would probably be
> > where you'd want to do your work.
> >
> > From your words above, it *seems* like you're saying that facilities
> > like this don't already exist; they do indeed. Adding more is possible,
> > but you'd need to find a niche that's been overlooked. If you just
> > started hacking without looking at what's already there, your chance of
> > getting it accepted is virtually nil.
> >
> > We want to be willing to accept new code, but that code has to fit into
> > the architecture of FreeBSD.
> >
> >
> >
> > ---------------------------+-----------------------------------------------
> > Chuck Robey | Interests include any kind of voice or data
> > [EMAIL PROTECTED] | communications topic, C programming, Unix and
> > 213 Lakeside Drive Apt T-1 | carpentry. It's all in the design!
> > Greenbelt, MD 20770 | picnic.mat.net: FreeBSD/i386
> > (301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha
> > ---------------------------+-----------------------------------------------
> >
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
---------------------------+-----------------------------------------------
Chuck Robey | Interests include any kind of voice or data
[EMAIL PROTECTED] | communications topic, C programming, Unix and
213 Lakeside Drive Apt T-1 | carpentry. It's all in the design!
Greenbelt, MD 20770 | picnic.mat.net: FreeBSD/i386
(301) 220-2114 | jaunt.mat.net : FreeBSD/Alpha
---------------------------+-----------------------------------------------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
