* Raul Miller said:
> On Sat, Sep 25, 1999 at 01:27:51PM +0200, Marek Habersack wrote:
> > The proposal, as I can see it, is to write a PAM module that could
> > be added to /etc/pam.d/passwd to ask whether the just-changed root
> > password should be cloned into the sashroot account. And that's a
On Sat, Sep 25, 1999 at 01:27:51PM +0200, Marek Habersack wrote:
> The proposal, as I can see it, is to write a PAM module that could
> be added to /etc/pam.d/passwd to ask whether the just-changed root
> password should be cloned into the sashroot account. And that's a
> really elegant and clean s
* Michael Neuffer said:
> * Raul Miller ([EMAIL PROTECTED]) [990923 16:15]:
> > On Thu, Sep 23, 1999 at 07:32:50AM -0500, Ashley Clark wrote:
> > > Couldn't sash include a PAM module that would change the password to
> > > match root's password whenever it was changed? Or am I oversimplifying
> > >
* Ruud de Rooij ([EMAIL PROTECTED]) [990924 08:40]:
> Michael Neuffer <[EMAIL PROTECTED]> writes:
>
> > * Raul Miller ([EMAIL PROTECTED]) [990923 16:15]:
> > > On Thu, Sep 23, 1999 at 07:32:50AM -0500, Ashley Clark wrote:
> > > > Couldn't sash include a PAM module that would change the password to
Hi.
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Raul Miller) writes:
> I've filed a wishlist bug against the passwd package to have sash
> included. [If you've also done this, let me know the bug number
> so I can merge them?]
I have not done, and will not because I knew you already did
Michael Neuffer <[EMAIL PROTECTED]> writes:
> * Raul Miller ([EMAIL PROTECTED]) [990923 16:15]:
> > On Thu, Sep 23, 1999 at 07:32:50AM -0500, Ashley Clark wrote:
> > > Couldn't sash include a PAM module that would change the password to
> > > match root's password whenever it was changed? Or am I
* Raul Miller ([EMAIL PROTECTED]) [990923 16:15]:
> On Thu, Sep 23, 1999 at 07:32:50AM -0500, Ashley Clark wrote:
> > Couldn't sash include a PAM module that would change the password to
> > match root's password whenever it was changed? Or am I oversimplifying
> > things?
>
> I don't have enough
On Thu, Sep 23, 1999 at 02:38:46PM -0400, Ben Collins wrote:
> Just out of curiosity, does sash support the standard -c command line
> option yet? If not, I wouldn't really consider pushing it as a root
> shell since it will break a lot of scripts (from cron and elsewhere).
$ sash -c date
Thu Sep
On Thu, Sep 23, 1999 at 09:53:45AM -0400, Raul Miller wrote:
> On Thu, Sep 23, 1999 at 07:32:50AM -0500, Ashley Clark wrote:
> > Couldn't sash include a PAM module that would change the password to
> > match root's password whenever it was changed? Or am I oversimplifying
> > things?
>
> I don't h
On Thu, Sep 23, 1999 at 07:32:50AM -0500, Ashley Clark wrote:
> Couldn't sash include a PAM module that would change the password to
> match root's password whenever it was changed? Or am I oversimplifying
> things?
I don't have enough confidence in Debian's pam, yet, to insist that
everyone that
On Thu, Sep 23, 1999 at 11:06:48AM +0900, Taketoshi Sano wrote:
> and (here is my proposal)
>
> d) sash will create a locked sashroot account with useradd, and
>display the message to use sashpasswd above as soon as possible.
That's an interesting idea. I'll think about it.
> By th
On Wed, 22 Sep 1999, Taketoshi Sano wrote:
> In article <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] (Raul Miller) writes:
>
> > > 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 ad
Hi.
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Raul Miller) writes:
> > 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 -- t
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 t
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
> >
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
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
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; howe
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
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...
--
[-]
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
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 th
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 co
23 matches
Mail list logo
