I'm collecting some info on the password hashing algorithms in use on various Unix systems. So far I have:
Code:
no $ legacy unix crypt
$1$ MD5
$2$ Blowfish on BSD
$2a$ alternate Blowfish on BSD
$md5$ Sun's alternate MD5
$3$ a Microsoft hash
$4$ not used?
$5$ RedHat proposed Sha-256
$6$ RedHat proposed Sha-512
Does anyone have any more info? I'm particularly interested in what happened to $4$ and some info on which Microsoft hash is represented by $3$. And I would be interested to learn about any algorithms I missed.
Hi,
how can one find that which encryption algorithm the system is using for keeping the user password in the /etc/passwd or /etc/shadow file.
Is it
1: Hashing ( which considers only first 5 letters of password)
2: MD5 (Which allows arbitry length passwords)
Thanks,
~amit (0 Replies)
So I have two files that I want to put together via hashes and am having a terrible time with syntax. For example:
File1
A apple
B banana
C citrusFile2
A red
B yellow
C orangeWhat I want to enter on the command line is:
program.pl File1 File2And have the result... (11 Replies)
Hi,
I'm looking for linear hashing implementation in C language. Please help.
PS: I have implement this on Ubuntu 10.04 Linux on 64 bit machine. (1 Reply)
Hello,
I'm having an issue with my password hashing. In /etc/shadow all the passwords hashes start with $1$. The security people want me to change it so the password hash starts with $5$ or $6$. So this is what I did to fix this.
I changed CRYPT_DEFAULT for 1 to 6
CRYPT_DEFAULT=6When I create a... (0 Replies)
So, I am writing a script that will read output from Bulk Extractor (which gathers data based on regular expressions). My script then reads the column that has the URL found, hashes it with MD5, then outputs the URL and hash to a file.
Where I am stuck on is that I want to read the bulk... (7 Replies)
Hi,
Our security audit person generated a report for Solaris-10 servers and mentioned this suggestion - "All passwords should be hashed using bcrypt. Solaris 10 supports this blowfish-based hash algorithm with the identifier 2a. To verify this, ensure the password hashes start with $2a$.... (2 Replies)
Discussion started by: solaris_1977
2 Replies
LEARN ABOUT HPUX
crypt_r
crypt(3C)crypt(3C)NAME
crypt - generate hashing encryption
SYNOPSIS
Obsolescent Interfaces
DESCRIPTION
crypt():
is the password encryption function. It is based on a one way hashing encryption algorithm with variations intended (among other things)
to frustrate use of hardware implementations of a key search.
key is a user's typed password. salt is a two-character string chosen from the set this string is used to perturb the hashing algorithm in
one of 4096 different ways, after which the password is used as the key to encrypt repeatedly a constant string. The returned value points
to the encrypted password. The first two characters are the salt itself.
Obsolescent Interfaces
generate hashing encryption.
WARNINGS
The return value for points to data whose content is overwritten by each call.
and are obsolescent interfaces supported only for compatibility with existing DCE applications. New multithreaded applications should use
SEE ALSO crypt(1), login(1), passwd(1), getpass(3C), passwd(4), thread_safety(5).
STANDARDS CONFORMANCE crypt(3C)