Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
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,
I don't know if any other users of Solaris 10 have discovered this, but there seems to be an exploit when using an "_" in your password. For example, if you password is "florida_19", all you would have to type is "florida_" or any combination: "florida_*" and it will give you access to the account.
Give me a reply if you have noticed this...or if there is a fix for it.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
There's no fix as there is no bug, Solaris password management has no built-in limitation, it's the underlying pam module configuration that set its requirements.
The default traditional unix crypt algorithm is based on a 56 bits hash, hence more than 8 characters are useless.
If you want support for longer passwords, you can change the crypt algorithm by setting CRYPT_DEFAULT=1 in /etc/security/policy.conf and uncommenting CRYPT_ALGORITHMS_DEPRECATE=__unix__ , or use a different pam module (e.g. LDAP).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.