Password encryption calls

From: Richard Rogers <R.M.Rogers_at_staffs.ac.uk>
Date: Tue, 16 Jun 1998 14:04:20 +0100

Hi -

I've just converted my authorization database to auth.db format on a
development system (better late than never, but it does mean big changes to
our account creation scripts), and consequently had to change a daemon from
using getprpwnam() to the new getespwnam(). While I was doing this, it seemed
to make sense to migrate from the old undocumented bigcrypt() call to the
newer, documented crypt16(). However, I am unable to get this to work as
expected. Even short (<= 8 character) passwords are encrypted to a 24 (?)
character string, and neither they nor genuinely "long" passwords encrypt
successfully to the encrypted password stored in the auth database. For short
passwords, crypt() still works, and for either long or short passwords,
bigcrypt() still works.

Am I missing something here, or is something broken?

Thanks for any thoughts.

Richard

-----------------------------------
Richard Rogers
Information Technology Services
Staffordshire University
Tel: 01785 (+44 1785) 353395
E-mail: R.M.Rogers_at_staffs.ac.uk
  ...Who knows where the time goes?...
Received on Tue Jun 16 1998 - 15:06:53 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT