similar to: PAM Account Checking with encrypted passwords

Hi, Andrew, Thank you very much. I have read some information about the samba PDC kerberos authentication as below. >> Anyone worked with a combination of Samba (TNG, or 2.x) running as a PDC for >> a network of primarily NT workstations, with the passwords being >> authenticated back into a Kerberos IV database? or a Kerberos V? > >> I'm trying to get this

Hello everybody, I?m using Red Hat 7.3 with Samba setup as a PDC, and I?m having a doubt. I am studying the directive "obey pam restrictions" because I would like to limit the number of logins with the same id. The documentation provided by SWAT tells me that encrypted passwords (like used by Windows98SE) will NOT follow these restrictions. Anybody could tell me if this information is

I was browsing the OpenSSH sources (which are very readable, thankyou very much) and noticed that PAM was only being told what host the user is logging in from for account processing - not for password processing. As I can see no reason not to put this in start_pam this is exactly what I have done - and attached a patch to this effect. This allows PAM to fill in rhost= in its audit messages

The LIBS line at the top of the Makefile read: LIBS=-lsec -lgen -lresolv -lsocket -lnsl -ldl Is there somewhere else that I need to add -lsocket? David -----Original Message----- From: Andrew Bartlett [mailto:abartlet@pcug.org.au] Sent: Thursday, February 28, 2002 4:22 PM To: David Edward Shapiro Cc: 'samba-technical@lists.samba.org'; 'samba@lists.samba.org' Subject: Re:

is turned on. Can anybody kind to confirm with me? Our network is using a mix of Win2k server, Win2k Pro, Win98, Win95 and WinMe machines, where the Win2k server is the domain controller and terminal service applications server and the Samba is a member fileserver of the domain. All workstations logon and mount the samba file services. We'd like to check if the problem could be solved by

As I have mentioned earlier on this list, I want to allow (relitivly) untrusted local users to SFTP to my server, as a secure method of remote file access. What I would like to do is to keep users within their home directory. I don't mind that it follows symlinks (if fact its probably a requirement), but some basic restriction on what users can see/access would be handy. The check I

Hi, I did as suggested, and still have the same problem. I am still able to login to samba with another users password that does not require password changes. This seems to me that the problem is related to PAM password changing. I have tried change the various PAM options in the smb.conf file, but cannot get it to work. Depending on the options, it either asks for a password or not. When it asks

All - Client: Win98, first version Server: Linux Mandrake, Samba 2.0.7 I'm trying to setup a Samba server to replace a customer's evil Windows 98 server, and have run into a problem. When used with encrypted passwords, it doesn't work. I tried all of the usual cures, and found that it worked perfectly if I enabled plaintext passwords in Win98. When I switched back to encrypted

network. I did read somewhere on the web (several years ago) of a guy who managed to boot windows from the net. With the start of Win 98/ME/ etc.etc it's not posible anymore. I currently use PXE to install machine from the net using bpbatch that works great only bpbatch is not really under developnt and the script language is a bit buggy. I see only one option to boot windows from the net and

when an nt 4.0 workstation or backup domain controller is joined to a domain, the trust account password is set to a well-known initial value. if you are concerned about internal network security, this is not really an acceptable risk: any captured network traffic can be decoded simply from knowing the name of the workstation, which is contained in the network traffic itself. the initial value

Is there a way for me to disable signing? I have looked around but couldn't find anything > -----Original Message----- > From: samba-bounces+ycayer=3webmedia.com@lists.samba.org > [mailto:samba-bounces+ycayer=3webmedia.com@lists.samba.org] > On Behalf Of Andrew Bartlett > Sent: Friday, July 25, 2003 20:01 > To: Yannick Cayer > Cc: samba@lists.samba.org > Subject: Re:

Andrew: Thanks for the heads up. As always, the support you guys give to an open source product amazes me. We worked with Jeremy & John Terpstra a few years ago when there was a problem with how AutoCAD was creating lock files (AutoCAD R14 running against SAMBA 1.9.something; it ended up being a timing issue that AutoDesk & Microsoft resolved, as well as samba 2.0 provided an

Jonathan Higgins wrote: > > A few more questions and comments... related to this topic > > If Kerberos is the back-end to LDAP.. there is no need to synchronize or store a >password in the LDAP tree.. just the principal for the user in the userpassword >attribute: userpassword = {kerberos}name@domain That is correct. I did not mean sync between Kerberos and LDAP, I mean sync

A few more questions and comments... related to this topic If Kerberos is the back-end to LDAP.. there is no need to synchronize or store a password in the LDAP tree.. just the principal for the user in the userpassword attribute: userpassword = {kerberos}name@domain in the smb.conf file do I need stuff like this? Unix password sync = yes passwd program =

MM = M Maki (1 Oct 2002) AB = Andrew Bartlett (2 Oct 2002) MM > I have a couple of Samba (2.0.7 & 2.2.0) servers I scanned with > Nessus and they reported a security hole of "Possible to login > to the remote host using a NULL session" I have a couple of NT > servers I disabled with a registry edit. Is there a way to > prevent this on the Samba

\\Pettit Connect As: Password: On the server side, I didn't get far because the domain name come up NULL so it failed on that test. Below are two logs log98.txt and log2000.txt that show full debug info. I might just have a stupid configuration or installation mistakes. I am sure that my basic configuration must work since it is a very typical setup. Any help will be highly appreciated

Cool, thanks alot, I really appreciate your time. I'm extremely pleased with 3.0.x's stability, I don't think local segment failover is really going to be a huge issue. Keep up the great work :) -- Cy > > > > Date: Fri, 30 Jan 2004 18:14:36 +1100 > From: Andrew Bartlett <abartlet@samba.org> > To: Cybr0t McWhulf <cybre@killcybre.org> > Cc:

The logs below still look like Samba is configured for encrypted passwords. As to your other mail, please, please use a more recent version than Samba 4.9 Andrew Bartlett On Sat, 2024-03-09 at 15:37 -0500, Tygre via samba wrote: > Hi there, > Sorry to come back to that, I tried to follow the code at > https://github.com/samba-team/samba/blob/master/source3/auth/auth.c#L214 > (and

OK we do all the steps in my previous missive and everything looks fine, landscape, collating the whole works. This is on a Laserjet 4000 with the latest PCL6 driver. The firm still has a good number of Laserjet 4s so we dutifully load up the latest PCL5E driver for the 4 and connect to the 4 on a couple of workstations. Everything goes to hell. Landscpae, collating and all other problems

I'm sure this has been discussed before, but would it then be possible to join a "real" NT4 or Win2k BDC to the Samba domain and establish the trust relation from our other Win2k? Or does the trust relationship have to be "registered" with the entire domain and therefore all the domain controllers? Khanh Tran Network Operations Sarah Lawrence College 1 Mead Way