search for: passwordhashes

Hi all, Is there a way to get dovecot to recognize arbitrary password hash schemes when looking up a password in a database? I originally set up with #default_pass_scheme = MD5, and I would like to migrate to SHA512. Seeing as the scheme is actually stored in the password column along with the password in the format $_<scheme#>_$_<salt>_$_<passwordhash>_, it seems to me that

The wiki[1] says: If all the passwords are in same format, you can use default_pass_scheme to specify it. Otherwise each password needs to be prefixed with "{password-scheme}", for example "{plain}plaintext-password". Why doesn't dovecot recognize the crypt scheme identifier ($1$ for MD5-CRYPT, $6$ for SHA512-CRYPT etc.)? At the moment I have to have the following in my db

Hi all, I am running samba-server-3.0.6-4.1.100mdk, openldap-servers-2.1.25-6mdk, lib64sasl2-plug-digestmd5-2.1.15-10.1.100mdk. I have searched through the lists and I am wondering if I am the only one doing this kind of set-up.. Anyway question is as follows: In my ldap server I have normal posix accounts with plain text password that are sorted out by a sasl-regex in the slapd.conf and

On 08.09.2017 06:16, Kurt Fitzner wrote: > > > Hi all, > > Is there a way to get dovecot to recognize arbitrary password hash > schemes when looking up a password in a database? I originally set up > with #default_pass_scheme = MD5, and I would like to migrate to SHA512. > > Seeing as the scheme is actually stored in the password column along > with the password

Hi, I would be *VERY* interested in a reversed pwget (see http://www.martnet.com/~johnny/exploits/microsoft/NT/WinNT.passwordhashes.deobfuscation.html) to be able to automaticaly set first-time NT passwords ('smbpasswd -r' will only work if you first enter the 'previous' password) on our PDC (evt. remote from UNIX through some tcp (ssh?) connection). Bjart Kvarme seems to have written such a tool, called '...

Hello, this is the first time I write to the samba list and I hope my question is not off topic. I want to set up a samba server to replace an Active Directory for my Windows workstations. So far, I have a LINUX network that works perfectly, all my users are stored in a LDAP server and their authentication is done against a MIT Kerberos server. Hence all users have a valid kerberos ticket

I''m about to implement this, and I''m thinking of storing the user''s id and their hashed password in the cookie after a successful authentication. can any see an obvious security issue with this? I know the method is vulnerable to cookie theft but am i missing anything? thanks alan

Hello, I'm setting up a new server and, again, seek for a decently secure (from a security specialist's POV) way to store and verify user passwords in a database. Additionally now, GDPR requires me to use a solid state-of-the-art solution. My OS is Ubuntu 20.04, Dovecot version 2.3.7, database backend with PostgreSQL 12. Obviously, storing the plaintext password is a terrible idea.

The latest version of this document can be found at http://pobox.com/~bcwhite/ldap-upgrade.txt Last Updated: 2006-05-23 I just upgraded our company's network from a system created 6 years ago (NIS and SMBPASSWD) to an up-to-date one (for 2006, at least) including a central LDAP server. It was a far from painless experience, so I thought I'd write up the experience in the