Re: [gentoo-soc] Progress Report - OpenPAM modules

[Eric Thibodeau]

Since you seem to be hesitant about their role:

passwd: account information, which _used_ to also contain the encrypted 
password and had to be world readable (john the ripper,amongst others, 
made that a bad idea)
shadow: came along later on as a root-readable-only to thwart john which 
contains the following structure (essentially, account password and 
time-constrained validity):

       shadow manipulates the contents of the shadow password file, 
/etc/shadow. The structure in the #include file is:

           struct spwd {
                 char          *sp_namp; /* user login name */
                 char          *sp_pwdp; /* encrypted password */
                 long int      sp_lstchg; /* last password change */
                 long int      sp_min; /* days until change allowed. */
                 long int      sp_max; /* days before change required */
                 long int      sp_warn; /* days warning for expiration */
                 long int      sp_inact; /* days before account inactive */
                 long int      sp_expire; /* date when account expires */
                 unsigned long int  sp_flag; /* reserved for future use */
           }

But I feel somewhat stupid stating this since I am sure you already know 
all of this much more than I do...

Eric

mellos@×××××××.com wrote:
> Hello people,
>
> I'll take the first step and try to write something as close to a
> progress report as I can. Things have been moving quite slowly, soc-wise,
> over here since it's the middle of my semester exams and on top of that,
> we've had quite a lot of earthquake activity for the past few days which made
> things even worse ( I had to move for a few days to my parent's house ).
>
> However, since it's a progress report, I'll focus more on what I've
> managed to get done than what I haven't. The first module which I
> started working on was pam_unix, which is probably the most important as
> well as the most "troublesome" since it takes care of all user
> authentication and account management. All started well and the
> authentication routine seemed to develop in a fast and smooth manner.
> Soon I had it complete and did some very basic testing. All was nice...
>
> After that, it was time to go on account management. At first, things seemed
> quite simple since all that had to be done was to ensure that the
> authenticating user was using a valid tty/host/uname/pass and that the
> account was not expired. When I got down to do it, I realised that it's
> not as simple as I've been thinking. Since the goal of the project is to
> write modules which will be compatible with BSD as well as LINUX, I had
> to understand how exactly BSD login classes work, how to include them in
> the module for BSD compatibility and furthermore, whether to use the
> information for each user from /etc/shadow or /etc/passwd on Linux.
>
> I've done some work and I think that I got the BSD part complete but I
> still have to check whether both shadow and passwd can provide the
> correct info that is needed for account validation and go on with the
> account management function of unix pam.
>
> I believe that by the end of this week, I'll have finished pam_unix and
> then I'll decide whether it's better to check that it's working under all
> circumstances or leave debuging for later and go on with writing the
> rest of the pam modules.
>
> That's pretty much all I had to say. I'd like to hear how the rest of the
> gentoo gsoc-ers are doing with their projects as well.
>
> Regards,
> Seraphim
>
>
>
>

-- 
gentoo-soc@l.g.o mailing list