On Mon, Sep 20, 1999 at 02:46:09PM -0700, Joey Hess wrote:
Raul Miller wrote:
Also, if you can anticipate any failure modes where sash would damage
the password file I'd appreciate hearing about them. It's already
the case that if sash has any problem writing out the new password
file
On Mon, Sep 20, 1999 at 06:02:47PM -0400, Greg Johnson wrote:
Here's one (happend to me). I have a '+' at the end of my /etc/passwd file
for nis. sash tried to add the new root acccount at teh end of /etc/passwd
AFTER the +. didn't work.
That was sash 3.3-5
Sash 3.3-6 already addresses
Raul Miller wrote:
They don't touch the root account. Instead, they clone
it as sashroot and set the shell on the cloned account.
This is mentioned in the package description.
On Sun, Sep 19, 1999 at 03:39:30PM -0700, Joey Hess wrote:
I suppose you have considered the security
On Sun, 19 Sep 1999, Raul Miller wrote:
There's not a lot I can do about this beyond advising the sysadmin that
it's a good idea.
what about asking it before doing the actual cloning ? (should be
defaulted to no, imho). as i see the postinst for 3.3-6,
it does not ask...
--
[-]
On Sun, Sep 19, 1999 at 10:53:01PM -0400, Raul Miller wrote:
Raul Miller wrote:
They don't touch the root account. Instead, they clone
it as sashroot and set the shell on the cloned account.
This is mentioned in the package description.
On Sun, Sep 19, 1999 at 03:39:30PM -0700,
On Mon, Sep 20, 1999 at 01:37:43PM -0400, Andrew Pimlott wrote:
Will this affect people who upgrade? It would be very unpleasant to upgrade
from slink and have a new root user.
Hmmm...
Even for new installs, I disagree with your decision. sash is useful
without another root account; however
Raul Miller wrote:
Also, if you can anticipate any failure modes where sash would damage
the password file I'd appreciate hearing about them. It's already
the case that if sash has any problem writing out the new password
file that it won't install it.
I think you should just use useradd to
On Mon, Sep 20, 1999 at 02:20:12PM -0400, Raul Miller wrote:
Also, if you can anticipate any failure modes where sash would damage
the password file I'd appreciate hearing about them. It's already
the case that if sash has any problem writing out the new password
file that it won't install
On Fri, Sep 17, 1999 at 02:45:32PM -0400, Raul Miller wrote:
FYI, sash_3.3-5 (which has been sitting in Incoming for the
last couple weeks) no longer prompts at postinst time, as the
postinst/prerm scripts have been completely redesigned.
On Mon, Sep 20, 1999 at 07:18:09AM +1000, Craig
On Sun, Sep 19, 1999 at 06:30:37PM -0400, Raul Miller wrote:
On Fri, Sep 17, 1999 at 02:45:32PM -0400, Raul Miller wrote:
FYI, sash_3.3-5 (which has been sitting in Incoming for the
last couple weeks) no longer prompts at postinst time, as the
postinst/prerm scripts have been completely
Raul Miller wrote:
They don't touch the root account. Instead, they clone
it as sashroot and set the shell on the cloned account.
This is mentioned in the package description.
I suppose you have considered the security problems, if root forgets to
change that password when they change the
11 matches
Mail list logo
