similar to: Different encrypted samba passwords than Unix passwords...

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

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

I have a RedHat Linux 9 server that I would like to allow users in my Windows 2000 domain to be able to map shares from without actually having an account on the system. Compiled samba, configured with "./configure --with-pam". Got the server into the domain, and regular "security = domain" seems to be working appropriately - providing there's a local account with the

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

On Fri, 14 Oct 2016 15:45:39 +0200 Ronny Forberger <ronnyforberger at ronnyforberger.de> wrote: > > > Am 14.10.2016 um 15:29 schrieb Rowland Penny via samba: > > On Fri, 14 Oct 2016 15:16:17 +0200 > > Ronny Forberger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 14.10.2016 um 15:05 schrieb L.P.H. van Belle via samba: >

> -----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

Hello man smb.conf encrypt passwords says: "This boolean controls whether encrypted passwords will be negotiated with the client. Note that Windows NT 4.0 SP3 and above and also Windows 98 will by default expect encrypted passwords unless a registry entry is changed." What does this mean? From my point of view it can mean 4 totally different things: 1) That when I run smbd with

Hello all, we use Samba to serve about 20 DOS/WfW/Win95 machines in 'security=share' mode. We use unix accounts as password validation, so I _know_ our Samba does not accept encrypted passwords. On Thursday, we added a NT4/SP3 box. I expected it not to logon before we made the plain-text password registry patch, but it did! It's a new NT installation (on a new AMD K6 box), so I

Any thoughts on setting breakpoints around hypercalls? ---------- Forwarded message ---------- From: Kip Macy <kip.macy@gmail.com> Date: Dec 26, 2005 12:14 AM Subject: setting breakpoints around hypercalls in a domU causes dom0 to lockup To: xen-devel <xen-devel@lists.xensource.com>, Keir Fraser < Keir.Fraser@cl.cam.ac.uk> Stepping through hypercalls (at the source level, not

Hello, Some weeks ago I reported my troubles with mixed-case passwords. I thought that using the option "password level" would solve my problems. Unfortunately I have ran into difficulties. Our students passwords are eight caracters long, with at least one number, one minor letter and one capital letter. I have set "password level = 6" (since there can be a maximum of 6

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

On Sat, 15 Oct 2016 18:17:18 +0200 Ronny Forberger <ronnyforberger at ronnyforberger.de> wrote: > > > Am 14.10.2016 um 16:00 schrieb Rowland Penny via samba: > > On Fri, 14 Oct 2016 15:45:39 +0200 > > Ronny Forberger <ronnyforberger at ronnyforberger.de> wrote: > > > >> > >> Am 14.10.2016 um 15:29 schrieb Rowland Penny via samba: >

Am 14.10.2016 um 16:00 schrieb Rowland Penny via samba: > On Fri, 14 Oct 2016 15:45:39 +0200 > Ronny Forberger <ronnyforberger at ronnyforberger.de> wrote: > >> >> Am 14.10.2016 um 15:29 schrieb Rowland Penny via samba: >>> On Fri, 14 Oct 2016 15:16:17 +0200 >>> Ronny Forberger via samba <samba at lists.samba.org> wrote: >>>

Am 15.10.2016 um 18:39 schrieb Rowland Penny via samba: > On Sat, 15 Oct 2016 18:17:18 +0200 > Ronny Forberger <ronnyforberger at ronnyforberger.de> wrote: > >> >> Am 14.10.2016 um 16:00 schrieb Rowland Penny via samba: >>> On Fri, 14 Oct 2016 15:45:39 +0200 >>> Ronny Forberger <ronnyforberger at ronnyforberger.de> wrote: >>>

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

Does anyone Know the procedure for Windows 2000 workstation, in order to not encrypt passwords. What I needed is something similar to the transcription I make below that works for windows nt4 and 98. Thank's Emanuel Duarte (Portugal) ********************************** This should take care of the "clear text password" problemsyou've encountered: For Win 98 (To enable

I just spent some time trying to figure out how to get OpenSSH to work correctly with NIS and PAM. It seems to work fine, apart from one minor worry I still have (see below). Feedback about grave security risks are welcome :) This is using RedHat 6.1 with updates and the OpenSSH 1.2.2p1-1 RPM's on the NIS server as well as the client. In short, my configuration is: /etc/nssswitch.conf:

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