[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: /etc/passwd - less security implementation 4 Slackware
Only stuff that is dynamically linked, is dynamically linked.
pam is good, for Red Hat. I don't run Red Hat, except to take a good look
at the features etc. The rpm system pisses me off almost as bad as
Winblows 'intelligent installs'. Ira Abramov found a way around some of
the things rpms do, so they don't do them to him.
On Thu, 1 Jan 1998 gal@netvision.net.il
wrote:
>
> On 31-Dec-97 Peter L. Peres wrote:
> >
> > Ok, I use Slackware a lot and it has only shadow and /etc/passwd based
> > security. I want to implement a dbm-based ACL scheme. It should not cover
> > X running on that machine.
> >
> > The question is, what needs to be changed except crypt, getpwent, etc in
> > libc. I assume that I will recompile all the required servers and
> > utilities, and the libc, and the kernel.
>
> I think you only need to mess with libc, since every thing is dynamic
> linked you don't have to recompile anything else.
> But I don't think messing with libc is a good thing.
>
> You better get all the utilities and servers who use authentication compiled
> with pam (RH5/4.2) this packages let you change your security as you wish
> with out the recompiling of nothing but your new authentication module.
>
>
> >
> > anyone ?
> >
> > TIA, Peter
>
> ----------------------------------
> E-Mail: gal@netvision.net.il
> Date: 01-Jan-98
> Time: 02:12:15
>
> This message was sent by XFMail
> ----------------------------------
>
>