Re: sash (was Re: demo vs. real package: FYI (was ...))
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 that it won't install it. I think you should just use useradd to edit the password file. You mean without ensuring that the password is useful? I've already elected to give the admin a choice (whether or not to add the account -- that'll be in the next release). The problem with password prompting is that it doesn't fit well into an automated or gui install. Under these circumstances do you still feel it's useful to add a locked account? -- Raul
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 this issue. Thanks, -- Raul
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 problems, if root forgets to change that password when they change the main root one? Yes I did. There's not a lot I can do about this beyond advising the sysadmin that it's a good idea. It might be a good idea to write a tool to automate this reminder [Perhaps generalizing it so that if one instance of a uid has its password changed and other instances do not change the account that got changed will get a mail message suggesting that the other accounts get changed.] But I've not undertaken this project, at least not yet. I want to get sash right first. [There's still some subtle issues that I think I can handle better. See bugs.debian.org/sash for details.] -- Raul
Re: sash (was Re: demo vs. real package: FYI (was ...))
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... -- [-]
Re: sash (was Re: demo vs. real package: FYI (was ...))
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, Joey Hess wrote: I suppose you have considered the security problems, if root forgets to change that password when they change the main root one? Yes I did. There's not a lot I can do about this beyond advising the sysadmin that it's a good idea. Will this affect people who upgrade? It would be very unpleasant to upgrade from slink and have a new root user. Even for new installs, I disagree with your decision. sash is useful without another root account; however you require users who wish to use it this way to read your documentation on undoing the damage (which you hopefully provide) and take the (hopefully small) risk that you mess up the passwd file. My opinion on prompting in the postinst is that, for all its disadvantages, there is a legitimate place for it within the current system. One question on sash install (not upgrade) would be fine if there is no clear default. Andrew -- Don't forget that Linux became only possible because 20 years of OS research was carefully studied, analyzed, discussed and thrown away. - kernel hacker Ingo Molnar
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 you require users who wish to use it this way to read your documentation on undoing the damage (which you hopefully provide) and take the (hopefully small) risk that you mess up the passwd file. At the moment, I only provide documentation on what's happening, not suggestions on how to manage this. 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. My opinion on prompting in the postinst is that, for all its disadvantages, there is a legitimate place for it within the current system. One question on sash install (not upgrade) would be fine if there is no clear default. Ok, I'll put back a single install time question where the sysadmin has one of several options: sash is inert and doesn't manage the password file, sash will become the root shell, sash will create a sashroot account from the current root account and use that as it's shell. And some notes on how to change this. -- Raul
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 edit the password file. -- see shy jo
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 it. 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. Greg -- Greg Johnson [EMAIL PROTECTED] http://physics.clarku.edu/~gjohnsonfinger for PGP key
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 redesigned. On Mon, Sep 20, 1999 at 07:18:09AM +1000, Craig Sanders wrote: do they automatically set up sash as root's shell? They don't touch the root account. Instead, they clone it as sashroot and set the shell on the cloned account. cool. i was just checking that the discussion from two weeks ago on how/what to do hadn't been forgotten. This is mentioned in the package description. even better :) craig -- craig sanders
Re: sash (was Re: demo vs. real package: FYI (was ...))
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 main root one? -- see shy jo
