need details on PAM implementation

A place to discuss Dropline GNOME.

Moderator: Moderators

need details on PAM implementation

Postby Barx on Tue Aug 30, 2005 5:10 pm

Hi all

I saw in LQ forum that dropline implements PAM on slackware.

Now I haven't installed yet DL, so I haven't checked.

The question is: after installing DL, do I can login users via PAM ?

I need to authenticate users on logon on a radius server, and the easiest way seem to use PAM, which isn't included in slack.

I don't have any other thing to do with PAM, only login users (to allow surf on the internet)

Tnx all in advance for any reply
Barx
Lurker
Lurker
 
Posts: 3
Joined: Mon Aug 29, 2005 5:16 pm

Re: need details on PAM implementation

Postby zborgerd on Tue Aug 30, 2005 10:19 pm

Barx wrote:Hi all

I saw in LQ forum that dropline implements PAM on slackware.

Now I haven't installed yet DL, so I haven't checked.

The question is: after installing DL, do I can login users via PAM ?

I need to authenticate users on logon on a radius server, and the easiest way seem to use PAM, which isn't included in slack.

I don't have any other thing to do with PAM, only login users (to allow surf on the internet)

Tnx all in advance for any reply


We only provide limited PAM functionality for very basic authentication. We have pam-enabled login via our Shadow update, for pam_console support. Additionally, we use some consolehelper stuff. Our GDM has pam support as well.

You could possibly use the Dropline Shadow and PAM packages to have a pam-enabled login capability without installing all of the Dropline GNOME packages. You would have to compile any other PAM modules that you might need as well, and modify your pam configurations accordingly in /etc/pam.d. Additionally, you could use our build scripts that are included in the packages. They are located in /usr/src/dropline-build-system (we include these with all recent updates so that users can see how we build them, and tweak them as needed). The PAM and Shadow scripts are still a work-in-progress though, as they have been ported over from the old build engine. There are still a few small tweaks that must be made to them.

These packs are intended for Slackware 10.1, and should not be used with older versions of Slackware.

http://prdownloads.sourceforge.net/drop ... z?download
http://prdownloads.sourceforge.net/drop ... z?download
http://prdownloads.sourceforge.net/drop ... z?download
http://prdownloads.sourceforge.net/drop ... z?download (optional)

If you do try to use the Dropline Shadow package, I would advise you to try logging into another console to verify that /bin/login still works *before* logging back out. This is always my failsafe when testing PAM and Shadow updates, because if you break something, it's much easier to simply "upgradepkg" back to the previous version instead of rebooting off of a boot CD because you've locked yourself out by breaking /bin/login. :) I've never verified whether or not they work completely on stock Slackware systems that don't include the rest of DLG. :)

If you would like to try to build your own packs from the scripts that are included in the packs, you should use the Dropline Build System.

http://droplinegnome.org/home/dagmar/dr ... 05.tar.bz2
Last edited by zborgerd on Thu Sep 15, 2005 1:15 pm, edited 4 times in total.
zborgerd
Site Admin
Site Admin
 
Posts: 3429
Joined: Thu Dec 12, 2002 2:20 pm
Location: Chicago, IL. USA

Postby wampl3r on Sat Sep 03, 2005 4:04 am

I recently went to install VMWare GSX on one of my Slack servers and discovered that it utilizes / requires PAM for authentication to its services. Being a Dropline user as well, I decided to try out the PAM packages on my stock server to see if it would work.

Through trial and error, I ended up installing the exact 4 packages listed above, copied in the VMWare provided pam.d file, and everything worked like a charm! I haven't seen a single side affect from updating the shadow package, and this server handles a variety of services and often has a high load.

fyi, its listed as optional above, but pam seems to be linked to cracklib and wouldn't authenticate without it so make sure its installed or you might not be able to login...

Hope that helps!
-Wamp
wampl3r
Runlevel 3
Runlevel 3
 
Posts: 40
Joined: Wed Feb 26, 2003 2:38 am
Location: Boulder, CO

Postby zborgerd on Sat Sep 03, 2005 4:16 pm

wampl3r wrote:I recently went to install VMWare GSX on one of my Slack servers and discovered that it utilizes / requires PAM for authentication to its services. Being a Dropline user as well, I decided to try out the PAM packages on my stock server to see if it would work.

Through trial and error, I ended up installing the exact 4 packages listed above, copied in the VMWare provided pam.d file, and everything worked like a charm! I haven't seen a single side affect from updating the shadow package, and this server handles a variety of services and often has a high load.

fyi, its listed as optional above, but pam seems to be linked to cracklib and wouldn't authenticate without it so make sure its installed or you might not be able to login...

Hope that helps!
-Wamp


Thanks for verifying this. Glad it works well for you.

I've corrected the cracklib thing above (I had typed it in a bit of a rush). I suspect that anything that uses the system-auth service (there are many things) will use Cracklib as well, and will indeed require that it is installed.
zborgerd
Site Admin
Site Admin
 
Posts: 3429
Joined: Thu Dec 12, 2002 2:20 pm
Location: Chicago, IL. USA

Postby Barx on Mon Sep 05, 2005 8:27 am

tnx a lot for the help, I'll try to install it and I'll report my results ..
Barx
Lurker
Lurker
 
Posts: 3
Joined: Mon Aug 29, 2005 5:16 pm

Postby zborgerd on Thu Sep 15, 2005 1:12 pm

The packs in my previous post were were built for Slackware 10.1. The following packs should only be used for 10.2, and will be included in the upcoming Dropline GNOME 2.12.0 release. Please do not install these on older versions of Slackware.

http://osdn.dl.sourceforge.net/sourcefo ... 86-2dl.tgz
http://osdn.dl.sourceforge.net/sourcefo ... 86-2dl.tgz
http://osdn.dl.sourceforge.net/sourcefo ... 86-2dl.tgz
http://osdn.dl.sourceforge.net/sourcefo ... 86-1dl.tgz (optional)
zborgerd
Site Admin
Site Admin
 
Posts: 3429
Joined: Thu Dec 12, 2002 2:20 pm
Location: Chicago, IL. USA


Postby zborgerd on Wed Sep 27, 2006 9:36 pm

New packs for 11.0, with many improvements:

http://osdn.dl.sourceforge.net/sourcefo ... 86-2dl.tgz
http://osdn.dl.sourceforge.net/sourcefo ... 86-2dl.tgz
http://osdn.dl.sourceforge.net/sourcefo ... 86-5dl.tgz
http://osdn.dl.sourceforge.net/sourcefo ... 86-4dl.tgz (optional)

These packs will be available in the 2.16.0 release of Dropline GNOME for Slackware 11.0. Please do not install them on anything older than Slackware 11.0.
zborgerd
Site Admin
Site Admin
 
Posts: 3429
Joined: Thu Dec 12, 2002 2:20 pm
Location: Chicago, IL. USA

Postby zborgerd on Sun Feb 18, 2007 6:16 pm

zborgerd
Site Admin
Site Admin
 
Posts: 3429
Joined: Thu Dec 12, 2002 2:20 pm
Location: Chicago, IL. USA

Postby vivir on Wed Sep 19, 2007 2:20 am

Is there any reason for this not to be similarly do-able
with 12.0 and New packs from 2.18.3 Pre-Release?
vivir
Runlevel 1
Runlevel 1
 
Posts: 7
Joined: Wed Sep 19, 2007 2:15 am
Location: Florida, USA

Postby Dagmar d'Surreal on Wed Sep 19, 2007 9:32 am

Not to do what? If you were looking to drop in a pam_radius module you could do that, but you're going to be on your own with respect to supporting it. None of us (that I'm aware of) even have a RADIUS server to test with, and it's those network-accessing modules that have been what's gotten PAM in trouble so many times in the past. Allow me to strongly recommend -fstack-protection-all on the pam_radius module just for starters.

Beyond that PAM for 12.0/2.18 should be working better than ever since I did a complete audit of how every single bloody piece of it goes together. This is not a task I would have wished on anyone, but it needed to be done.
Dagmar d'Surreal
Evil SubGenius
Evil SubGenius
 
Posts: 583
Joined: Sat Nov 27, 2004 5:23 pm

Postby vivir on Wed Sep 19, 2007 11:31 am

Sorry, I kind of hijacked this thread. I'm not concerned with
radius just yet, nor vmware, just adding PAM to a minimal slack12.

I wonder if dropping in only the (4 mentioned) DLG
2.18 packages, not the entire DLG, will work for Slack12
as mentioned in some previous threads, (which I can't
locate at the moment) or if there might be some additional
dependencies introduced by the new slack12 package layout.

What I really want is to run slack setup, replacing slack's
shadow with DGL shadow + pam, cracklib, and usermode,
and have that work "out of the gate".

Thanks
vivir
Runlevel 1
Runlevel 1
 
Posts: 7
Joined: Wed Sep 19, 2007 2:15 am
Location: Florida, USA

Postby vivir on Thu Sep 20, 2007 7:32 pm

Dagmar d'Surreal wrote:Beyond that PAM for 12.0/2.18 should be working better than ever since I did a complete audit of how every single bloody piece of it goes together. This is not a task I would have wished on anyone, but it needed to be done.



Did you, b any chance, build the pam_passwdqc piece?
<http://www.openwall.com/passwdqc/>
<http://linux.die.net/man/8/pam_passwdqc>

Since I, so far, only grabbed the DLG pam package I don't have a
development environment for all the pam stuff set-up.
The pam_passwdqc part apparently won't build all by itself.
I'll compile it all myself if necessary, but I'm hoping you've already done it.
Is there a slackbuild script for pam and friends readily available

Thanks
vivir
Runlevel 1
Runlevel 1
 
Posts: 7
Joined: Wed Sep 19, 2007 2:15 am
Location: Florida, USA

Postby vivir on Thu Sep 20, 2007 7:46 pm

vivir wrote:Is there a slackbuild script for pam and friends readily available


ok, found it in the package: usr/src/dropline-build-system/SCRIPTS/pam/build
vivir
Runlevel 1
Runlevel 1
 
Posts: 7
Joined: Wed Sep 19, 2007 2:15 am
Location: Florida, USA


Return to Dropline GNOME Discussion

Who is online

Users browsing this forum: Google [Bot] and 0 guests