[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: /etc/passwd - less security implementation 4 Slackware
'Messing' with libc is a nice game. I don't think that one can really
break something, if the function protos are not changed and no horrible
things are done in the code, about spinlocks, races and other such things.
Of course one would have to test it for a long time...
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
> ----------------------------------
>
>