similar to: encrypted passwords: what negotiation with what client?

Hello, I'd be very grateful if anyone could share their ideas on this problem. The situation is this: I have a Solaris 8 machine running Samba 2.2.1a. The global configuration has "security = USER" and originally had "encrypt passwords = NO". I was able to map drives to shares on this machine from my WinNT 4 SP 5 workstation when I set the registry key advised by the

I am trying to use Samba between a RedHat Linux 9 system and several Win98 PC's. From the Win98 systems, I can see and access the Linux folders I have made available. I can see the Win98 PCs and their shared directories from the Linux box. Understanding that Win98 requires encrypted passwords, I have set the "encrypt passwords" keyword in the smb.conf file to "yes".

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

NT4.0 SP4 gives me this error when trying to access a Samba 3.0.23c server. \\Omega300\files is not accessable The specific network password is not correct. omega300 is the samba server, running samaba 3.0.23.c on SCO Openserver 5.0.7. omg180 is a Windows NT4 SP4 box. omega is a Windows 98 box. Passwords are not encrypted. We are also using VisionFS (SCO's smb product, which they no longer

Hi, we have following situation: I migrated our company mailserver from POP3 only to dovecot with IMAP and POP. We need to have unencrypted POP3 from our internal network, and the subnet our mailserver is in. Additionally, we now want to allow encrypted IMAP from the internet (for some defined accounts), preferably with TLS (which means I open Port 143 in our firewall). Now, how can I

I have an old Samba network that uses unencrypted passwords. At the time, the posts were running win95. These days they are running win98 for the most part, but introducing new machines onto the network means fiddling with the EnablePlainTextPassword registry key. So currently, all the machines use plain-text passwords. I want to modify them all to use encrypted passwords. Naturally, I want to do

Hi, I'm looking for some help to migrate from plain text to encrypted passwords. I'm using smbpasswd for authentication on a FreeBSD 4.9 server with samba 2.2.8. When we set up our server, we had Win95 clients with plain text passwords. As we introduced Win98 clients, we just kept with the plain text passwords. Now we are looking at XP clients and enctrypted passwords. My understanding

Hi there, I have looked for a solution to my problem on the Internet (and in particular this mailing list), but couldn't find one, probably due to searching for the wrong thing :-) I have an RPI running Samba version 4.9.5-Debian. "pdbedit -L" shows that the user "smbuser" exists. I used "smbpassword" to set the password of "smbuser". I also have

I have an NT Network and as one of the first steps in eliminating NT from my shop I need to be able to mount some of my NT shares on my Linux boxes. When I execute: smbmount //NTXX/ShareName /NTShare it asks me for a password. I enter the correct password (yes I've checked my capslock key and made sure I typed it correctly) but I get the following error. 10819: session setup failed:

Hey all first post, I recently set up an Apple Xserve running Mac OS X server v. 10.2.4 as a SMB file server for a network of mixed win2k, win98, and Mac (classic) boxes (samba version 2.2.3). I currently have Open Directory setup to pull Active Directory users and groups via ldap from the PDC, as well as SMB pass through authentication (so winbindd is not needed). Everything is currently up

Hi, is there any way to get dovecot to use "ssl_require_client_cert = yes" for encrypted connections only? For unencrypted connections there can't be any client certificate, and I can't disable unencrypted connections altogether (I limit them by firewall to our own network). Rainer Frey -- Software Development ------------------------------------------------------ Inxmail

On Mon, 2024-03-04 at 20:10 -0500, Tygre via samba wrote: > Hi there, > I have looked for a solution to my problem on the Internet (and > in particular this mailing list), but couldn't find one, probably due > to searching for the wrong thing :-) > I have an RPI running Samba version 4.9.5-Debian. "pdbedit -L" > shows that the user "smbuser" exists. I

Anyone got any experience/suggestions for a way to store a directory of sensitive information on a CentOS box? This directory contains many scripts and output files, I need it backed up but not unencrypted and don't want to store it in a tar file type archive as when it needs to be accessed and have scripts executed/data generated, it needs to be untarred/unencrypted and I don't know the

Hello Why is it necessary to specify encrypt passwords = no to make Samba server start using solely /etc/passwd? Isn't it possible to tell Samba server that on the way between a client and the server, the passwords sould be encrypted, and after decryption, they will be checked against /etc/passwd and not smbpasswd, tdb or whatever backend? Cl<

Recently Microsoft introduced some network improvements which made it impossible to connect to Samba without using encrypted passwords. There is a way-around for NT4.0 (SP3) by changing a registry entry. This has been published by Microsoft in their knowledge-base. With WIN95 OSR2.1 and the vredir patch (vredir.vxd and vnetsup.vxd dated June, 2nd 1997 or later) the behaviour is very similar to

Hello, I'm using geli on laptop PC with only one HDD. Disk is divided into two slices, ad0s1 and ad0s2. Second slice (ad0s2) is encrypted with GEOM ELI using two-factor authentication - passphrase plus keyfile on USB drive. FreeBSD is installed on ad0s2.eli and first slice is not used by this system so let's say that I've got a full disk encryption. Now my question - is it safe

On 21/11/2016 17:21, Brian Candler wrote: > I'd quite like to be able to fetch a ticket using the keytab I found a solution to that part by using a different form of principal name with "hostname$" root at client-ad:~# kinit -k -t /etc/krb5.keytab 'CLIENT-AD$@AD.EXAMPLE.NET' root at client-ad:~# klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal:

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

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 below) but I still can't understand why one Samba client can connect, but the other can't. I can't understand why, with one client, the code would go into "check_samsec.c:183" (and return "sam_account_ok") while, with

On Tue, 22 Nov 2016 15:19:34 +0000 Brian Candler via samba <samba at lists.samba.org> wrote: > On 21/11/2016 17:21, Brian Candler wrote: > > I'd quite like to be able to fetch a ticket using the keytab > > I found a solution to that part by using a different form of > principal name with "hostname$" > > root at client-ad:~# kinit -k -t