Is it possible to have accounts under DU 4.0 (with Enhanced Security)
that do _not_ have passwords?
(Actually, I know the answer to that -- it's "Yes".)
What we would _really_ like is for have all of the various "login"
mechanisms (telnet, rlogin, ftp, whatever) recognize the situation of
an account that actually _has_ a "null password". When such an account
is referenced, we do *not* want to even _see_ the password prompt.
There are some situations where a passwordless account is "desirable"
(read: "required"). Asking the user for a password leads to user
confusion. If one just hits RETURN at this point, one can log in.
However, if one types anything else, it's a "bad password". What we
desire is the situation where we can "wildcard" the password, such that
*any* response is acceptable. Better yet from our users' (and our)
points of view, if the account has no password, then don't even _ask_
for it.
So, is this second requirement possible?
If not, why not? Are there any plans to "correct" this?
(And if not, why won't it?)
As far as we have been able to determine, we _can_ make a null
password, but one must still _enter_ a "null password" to match. We've
been singularly unsuccessful in eliminating the password prompt for
these accounts.
Thanks in advance for any insight you can supply.
--
John G Dobnick "Knowing how things work is the basis
Information & Media Technologies for appreciation, and is thus a
University of Wisconsin - Milwaukee source of civilized delight."
jgd_at_csd.uwm.edu ATTnet: (414) 229-5727 -- William Safire
Received on Fri Aug 23 1996 - 00:30:23 NZST