account. And that's a
> > really elegant and clean solution, IMHO.
>
> If someone wants to write such a module, I'd be more than happy
> to include it in the sash package.
I would be willing to do so if nobody has volunteered yet.
marek
pgp4qaCoCHHAU.pgp
Description: PGP signature
elegant and clean solution, IMHO.
If someone wants to write such a module, I'd be more than happy
to include it in the sash package.
Aside: currently sashroot is optional, and I also offer the option to
change sashroot's password every time sash is reconfigured. Other options
inclu
* 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
* 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
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 becau
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'
* 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
> > t
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 -
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
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,
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
circumstances do you still feel it's useful to add
> > a locked account?
>
> How about to include following small script
> (maybe "/sbin/sashpasswd" with permission 0700 or 0744):
>
> #! /bin/sh
> PATH=/usr/bin
> passwd root
> passwd s
d, but it may go difficult work as
the passwd package has so many patches, and not so efficient work to hack
with other package, at least for me, I feel. It may be better just to use it.
You wrote:
| Ok, I'll put back a single install time question where the sysadmin has
| one of sev
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
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 probl
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
&
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
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
ut 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 req
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...
--
[-]
inder [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
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
stinst/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 she
t 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.
This is mentioned in the package description.
--
Raul
The README says:
The purpose of this program is to make replacing of shared libraries
easy and safe. It does this by firstly being linked statically, and
secondly by including many of the standard utilities within itself.
I needed it the other day. And maybe other's could need it, too. So maybe
25 matches
Mail list logo
