Subject: Re: Hardware detection question/problem - msg#00148

Previous Message by Date: click to view message preview

Re: [pamldap] pam_ldap.so and Debian...making it work!

I noticed that the common-session is included under the login config.  Although; I can't think of what session would have to do with user authentication. Also, since there is "auth" lines in the login config perhaps I should include the pam_ldap.so at the top of the login config?  **I included comments showing how the respective config file is set.** Debian Testing /etc/pam.d/login: auth        requisite        pam_securetty.so     #Disallows root logins except on tty's.. auth        requisite        pam_nologin.so     #Disallows other than root logins when /etc/nologin exist auth        required        pam_env.so          #Parses /etc/environment @include    common-auth                   #auth    required    pam_login.so @include    common-account             #account     required    pam_login.so @include    common-session             #session    required    pam_unix.so session        optional    pam_lastlog.so # prints last login info upon succesful login session        optional    pam_motd.so  # prints the motd upon succesful loing session        optional    pam_mail.so    standard    noenv # prints status of users mbx upon login Is there a "test" that would ensure that pam_ldap.so is being called?  Just looking at the auth.log is not providing much except pam_unix.so entries. Thanks, Tim Jordan On Thu, 2004-04-29 at 16:23, Joshua McClintock wrote: Even though you changed this in the common-* pam configs, /etc/pam.d/login is probally not 'including' the common configs. If you trying to login via the console (tty), I believe the getty calls login which uses /etc/pam.d/login. On Thu, 2004-04-29 at 03:54, Tim Jordan wrote: > I'm having a frustrating day trying to get my one box that is running > Openldap to use pam_ldap.so for authentication via slapd. > > Running Debian Testing. > > I have configure openldap properly. I can search and have already > migrated local accounts up to Openldap. > > I can see my directory nicely using GQ. > > I have modified the > /etc/pam.d/common-auth...common-password...common-account.. > respectivly to reflect: > > auth required pam_ldap.so > account required pam_ldap.so > password required pam_ldap.so > > I have restarted the server then logged in with my user account (tim). > > I then reviewed the /var/log/auth.log and see that authentication is > still using pam_unix.so. It's really confusing to understand this > becasue I commneted out all the pam_unix.so for the pam.d config files > above. > > If anyone can advise me on a good method for troubleshooting pam_ldap > or perhaps enlighten me if debain does things differently the using > the common-* config files. > > Thank you, > Tim Jordan >

Next Message by Date: click to view message preview

Re: [pamldap] pam_ldap.so and Debian...making it work!

On Thu, 2004-04-29 at 09:01, Tim Jordan wrote: > I noticed that the common-session is included under the login config. > Although; I can't think of what session would have to do with user > authentication. > > Also, since there is "auth" lines in the login config perhaps I should > include the pam_ldap.so at the top of the login config? > > **I included comments showing how the respective config file is set.** > > Debian Testing /etc/pam.d/login: > auth requisite pam_securetty.so #Disallows root > logins except on tty's.. > auth requisite pam_nologin.so #Disallows other than > root logins when /etc/nologin exist > auth required pam_env.so #Parses > /etc/environment > > @include common-auth #auth required > pam_login.so > @include common-account #account required > pam_login.so > @include common-session #session required > pam_unix.so > > session optional pam_lastlog.so # prints last login info > upon succesful login > session optional pam_motd.so # prints the motd upon > succesful loing > session optional pam_mail.so standard noenv # prints > status of users mbx upon login > > > Is there a "test" that would ensure that pam_ldap.so is being called? > Just looking at the auth.log is not providing much except pam_unix.so > entries. > > Thanks, > Tim Jordan I just modified /etc/pam.d/login a little: auth requisite pam_securetty.so auth requisite pam_nologin.so auth required pam_env.so auth required pam_ldap.so auth required pam_unix.so nullok use_first_pass account [module_unknown=ignore default=die success=done user_unknown=ignore \ system_err=ignore service_err=ignore authinfo_unavail=ignore] \ pam_ldap.so account required pam_unix.so session required pam_unix.so session optional pam_lastlog.so session optional pam_motd.so session optional pam_mail.so standard noenv password sufficient pam_ldap.so password required pam_unix.so nullok obscure min=4 max=8 md5 This is off a stock Debian Woody box. Local logins do auth against LDAP. It works great, unless my LDAP server is unavailable. Then, the box is locked out. This is why I haven't put this into production yet. If you want ssh to auth against LDAP, then you have to modify /etc/pam.d/ssh using the same lines as above. -- Brendon Colby Unix Systems Administrator Lightedge Solutions, Inc.

Previous Message by Thread: click to view message preview

Re: Hardware detection question/problem

Dave Marples <dave@xxxxxxxxxxx> wrote: > The latest discover seems to be called 'discover', and it won't > auto-update due to dependencies, so [apt-get install discover] is your > friend. The current version in sarge (for me at least) fixes most of the > problems I had with NICs etc....only outstanding issue was that alsa > wouldn't load. That was due to discover being _too_ good and loading the > i810 module when I really wanted the one from alsa....a suitable line in > /etc/discover.conf to ignore the sound module fixed that. Could you post (or email to me) your /etc/discover.conf? I am having trouble getting alsa to work, and I don't see a reference to alsa in my /etc/discover.conf: <?xml version="1.0"?> <!-- $Progeny: discover.conf 3839 2003-11-17 04:25:01Z dsp $ --> <!DOCTYPE conffile SYSTEM "conffile.dtd"> <conffile> <busscan scan="default"> <bus name="ata"/> <bus name="pci"/> <bus name="pcmcia"/> <bus name="scsi"/> <bus name="usb"/> </busscan> </conffile> > Everything's peachy again... That's what I'm hoping for. <g> Ruben

Next Message by Thread: click to view message preview

yelp

Holbrook, Govenment don't want me to sell UndergroundCD !Check Your spouse and staff Investigate Your Own CREDIT-HISTORY hacking someone PC! Disappear in your city bannedcd2004 http://www.9001hosting.com/cd/ thermostat,the latter gave.