Re: BSD chfn bug (aka ssh quirks/killing thread)

Subject: Re: BSD chfn bug (aka ssh quirks/killing thread)
From: Blue Boar (BlueBoarTHIEVCO.COM)
Date: Tue Dec 28 1999 - 16:06:02 CST

• Next message: mIV: "leaky kernel ? ;)"
• Previous message: Mark Rafn: "Re: ssh quirks..."
• In reply to: FARAZ JAMSHED: "Re: BSD chfn bug"
• Reply: Blue Boar: "Re: BSD chfn bug (aka ssh quirks/killing thread)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

FARAZ JAMSHED wrote:
>
> >>In message <Pine.LNX.4.20.9912251656310.23074->>100000pet.notbsd.org>
> >>"Stanislav N. Vardomskiy" writes:
> >>: This just *might* be a problem.
> >
> >Not the way you think. You have no control over the name of the file
> >created.
> >
> >Warner
>
> yes we could have control by setting the right UMASK settings...
>

The question posed was is there a way to get a file with the name you
want in /etc using the bug under discussion. Most folks (myself
included) fail to see how the umask setting helps with that. To
rename files, one has to have rights on the parent directory,
not the file itself.

So, if you've got an example of how umask helps, we'd love to
see it.

Other than that, we've all had our unix file permission refresher
for the week. People are starting to get nasty in their replies.
So, unless folks have some interesting technical points that
bring us closer to a security hole, I'm going to kill off
these threads.

                                        BB

• Next message: mIV: "leaky kernel ? ;)"
• Previous message: Mark Rafn: "Re: ssh quirks..."
• In reply to: FARAZ JAMSHED: "Re: BSD chfn bug"
• Reply: Blue Boar: "Re: BSD chfn bug (aka ssh quirks/killing thread)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b27 : Tue Dec 28 1999 - 17:57:07 CST