similar to: NIS, PAM, OpenSSH. Seems to work perfectly (one minor concern)

On Tue, 3 Apr 2001, Niels Provos wrote: > Paul, something is broken in your openssh install. Definately. But is it the client or the server? I've sent it to the portable OpenSSH bug address. I'm using OpenSSH 2.5.2p2-1.7 on a RedHat 7.0 with all updates. Sometimes I can login fine, and sometimes I can't. It actually seems to almost alternate,

Hi, I have an auth module for PAM that I wrote a few years ago called pam_vsd.so. The idea is that a user must have a certain privilege before they can successfully authenticate. Without the privilege the PAM module will return PAM_PERM_DENIED. However I find that in OpenSSH 3.7.1p2, I can easily subvert this check simply by hitting return 3 times on connection i.e. [nick at localhost

I am appending some documentation by my colleague Bill Eldridge that was actually written for our dial-up service, but should work for you purposes as well. A couple notes. 1.)The user must exist in /etc/passwd on the Samba machine or login to the Samba box will fail. 2.)In the example, we don't set up home directories for the users, we are using it for dial in and they usually want to

Hi, i have a minor Problen with Samba 1.9.16p11 under RedHat 4.2 and samba 1.9.18 under RedHat 5.0. Getting the shares from NT or w95 are ok but in the messages log file i got tons of these messages: Feb 2 06:49:54 bell PAM_pwdb[3520]: get passwd; pwdb: structure is no longer valid Feb 2 06:49:59 bell last message repeated 93 times Feb 2 06:49:59 bell PAM_pwdb[3520]: 1 authentication

> We are trying to have linux authenticate to linux server running samba > 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all > authenticate to the linux server but we are having problems with blank > passwords or the user can type any password. We are using pam modules for > the authentication on the client machines. > I have included the config files for

> -----Original Message----- > From: Reed, Tameika > Sent: Monday, November 17, 2003 5:56 PM > To: 'samba@lists.samba.org' > Subject: Samba PDC trying rid null logins > > > > > We are trying to have linux authenticate to linux server running samba > 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all > authenticate to the

For some reason I get these messages in my logs. What wrong? Everythings seems to work fine! Oct 14 07:56:09 sloterdijk PAM_pwdb[11029]: 1 authentication failure; (uid=0) -> paul for samba service Oct 14 07:56:30 sloterdijk PAM_pwdb[11031]: 1 authentication failure; (uid=0) -> paul for samba service Oct 14 08:04:08 sloterdijk PAM_pwdb[11052]: 1 authentication failure; (uid=0) -> groot

Hi, I have recently upgraded from OpenSSH-3.5 to OpenSSH-3.8 on my Red Hat 6.2 servers. I use radius (pam_radius_auth) for ssh authentication. Since the upgrade ssh1 (putty 0.52) logins are failing. I've come to the conclusion that pam is skipping the radius section of the config file and is falling back to standard unix authentication. Is there any way of making ssh1 work with radius on

Hi there I'm running a samba cvs server in a windows domain with a W2K PDC. I want to authenticate windows users through ssh. I'm able to login with a windows user to the server on the server himself but when I want to login via a windows client It doesn't work. The connection is refused. Could it be something mis configured in my ssh pam module. This is my pam ssh module PAM

We are using OpenSSH (portable) version 3.0.1p1 on Linux 2.2.14-10 with RedHat's distribution of PAM 0.72-20.6.x for rsync'ing RRDTool data between two machines (among other things). When running 'rsync -essh -avz', everything works fine but the system log on the sshd side shows: PAM_pwdb[8021]: authentication failure; (uid=0) -> rrd for sshd service sshd[8021]: Accepted

retitle Traffic forwarding issue between Xen domU/dom0 thanks This week again this bug occurred again so we are trying to create some kind of reproduce algorithm. First we've created two virtual machines named koekiemonster.bofh.hq.mendix.net and netappsim.bofh.hq.mendix.net. We've added 29 vifs to koekiemonster.bofh.hq.mendix.net. During this tests we've always had a ping

I may be reading this wrong, but I'm trying to figure out why samba is sometimes trying to do a Unix password lookup to authenticate a samba connect. I have my samba passwords different than my Unix passwords. I'm using my own compiled version of Samba 1.9.18p10. I have an NT4 SP3 box and when I try to access a share through explorer on either of my two Linux boxes with encrypted

Hello. I have been trying to get Red Hat 9 workstations to authenticate via an NT 4 PDC. here is my /etc/pam.d/login file, auth required /lib/security/pam_securetty.so auth required /lib/security/pam_nologin.so auth sufficient /lib/security/pam_pwdb.so shadow nullok auth required /lib/security/pam_smb_auth.so nolocal account required

I tried upgrading from samba 1.9 to 2.0 on two seperate RedHat servers, and after both upgrades nobody could get authenticated. The windows boxes had the registry hacks to turn off encrypted passwords, and I'm authenticating out of passwd+shadow. I found many similiar posts on DejaNews and in the samba mailing list archives. I broke out strace and found the problem. Samba 2.0 tries to

Hello, Installed the binary RPM (http://de.samba.org/samba/ftp/Binary_Packages/redhat/RPMS/7.1/) for samba 2.2.2 on my redhat 7.1 server. I got winbind to work and my samba server is now using NT usernames and groups. I was very unsure about how modify the pam.d files. The only file I changed was the /etc/pam.d/samba file. I pulled this configuration from another mail post.

Hello all, I am not sure my original mail got through to the list (I haven''t received it back), so I attach it below. Anyhow, now I have a saved kernel crash dump of the system panicking when it tries to - I believe - deferred-release the corrupted deduped blocks which are no longer referenced by the userdata/blockpointer tree. As I previously wrote in my thread on unfixeable

Hello, I am have some interesting problems with the pam_winbind portion of samba 3.1. wbinfo -u and getent passwd works but when I login I get the following messages in /var/log/messages. Jan 5 11:09:36 hermes pam_winbind[9014]: write to socket failed! Jan 5 11:09:36 hermes pam_winbind[9014]: internal module error (retval = 3, user = `CSQ+shane' Jan 5 11:09:36 hermes PAM_pwdb[9014]: check

Hi all, I was wondering if someone could lend a little assistance. I recently setup SAMBA/Winbind to allow users to login to a Redhat 8 box using their Windows NT Domain credentials. All is working well in that regard. The issue I am having is getting regular UNIX based users to be able to login. The following is my PAM configuration. For example, if I try to login as root, it does not work.

Hello Andrew, I'm a little stuck with my login authentication for my Samba 3 box. With the new features in Samba 3 - Should I be able to provide username@domain & password at login that would authenticate me against our W2K ADS PDC and obtain my kerberos ticket? Please advise on the suggested way to authenticate against our Active Directory domain at login if I'm way off base on

Hello, I am running a RHEL5 server as a member in a NT4 domain. I am not using an AD. my nsswitch.conf and /etc/pam.d/{login,authconfig,samba} are configured accordingly. (auth-config in RHEL4 is now renamed to authconfig on RHEL5). My problem is that wbinfo -u & wbinfo -g work fine, but getent passwd only returns local linux users; Also smbclient -L localhost -Uusers will only work