Menu

#194 Field separator conflict in access.conf

feature-request
closed-fixed
modules (176)
5
2002-05-07
2002-04-22
Anonymous
No

pam_access uses colon field separator in access.conf.

It does conflict with {x|g|k}dm, what sets PAM_TTY
to "hostname:display"

pam_access errors: "Bad field count" and users with
restricted access can log in.

Im propose to use new separator character.

Discussion

  • Andrew G. Morgan

    • milestone: 101532 --> feature-request
    • assigned_to: nobody --> agmorgan
    • status: open --> closed-fixed
     
  • Andrew G. Morgan

    Logged In: YES
    user_id=37107

    I've opted to leave the behavior of this module defaulting
    as it was.
    However, I've added a new module argument "fieldsep=" which
    support
    changing the field separator to whatever you want. The
    documentation
    changes suggest using '|' to be more X friendly.

    Cheers

    Andrew

    Checking in CHANGELOG;
    /cvsroot/pam/Linux-PAM/CHANGELOG,v <-- CHANGELOG
    new revision: 1.126; previous revision: 1.125
    done
    Checking in doc/modules/pam_access.sgml;
    /cvsroot/pam/Linux-PAM/doc/modules/pam_access.sgml,v <--
    pam_access.sgml
    new revision: 1.4; previous revision: 1.3
    done
    Checking in modules/pam_access/access.conf;
    /cvsroot/pam/Linux-PAM/modules/pam_access/access.conf,v
    <-- access.conf
    new revision: 1.3; previous revision: 1.2
    done
    Checking in modules/pam_access/pam_access.c;
    /cvsroot/pam/Linux-PAM/modules/pam_access/pam_access.c,v
    <-- pam_access.c
    new revision: 1.7; previous revision: 1.6
    done

     

Log in to post a comment.

MongoDB Logo MongoDB