Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi guys,
I'm trying to use john the ripper to crack my own password on my fc10. First I created the unshadowed file combining passwd and shadow. When I use john to crack it, it says "No password hashes loaded". One thing I 've noted is the hash for the password is very long. On my other systems, the hashes are shorter and I can crack those successfully using a fake worldlist( that contains my password) I created.
Can someone explain, whats going on? And how to do do it.
This is the the password hash from the system in question.
The fake word list was cheating. You should test the strength of your password without giving it the answer. Giving it the answer, it finished early so you don't know whether a cracker would be able to crack it using the same tool.
I don't see any colons, and the dots are throughing me. The "$6$" will indicate the password hash used. The characters between the second and third "$" are the salt.
The "$6$" is for the sha-512 hash. It looks like the results are uuencoded from a binary result.
-----
Out of the box, John supports (and autodetects) the following Unix crypt(3) hash types: traditional and double-length DES-based, BSDI extended DES-based, FreeBSD MD5-based (now also used on Linux and in Cisco IOS), and OpenBSD Blowfish-based (now also used on some Linux distributions). Also supported out of the box are Kerberos/AFS and Windows LM (DES-based) hashes.
-----
I wouldn't be surprised if there are patches floating around to support SHA, though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.