[Info-vax] stumped by SSH

[oswald.knoppers at gmail.com]

Op dinsdag 9 februari 2016 09:32:10 UTC+1 schreef Phillip Helbig (undress to reply):
> In article <yq6QVnz1WGw6 at eisner.encompasserve.org>,
> cornelius at eisner.decus.org (George Cornelius) writes: 
> 
> > I might at this point ask for a reproducer.  Make the simplest
> > possible user account which, upon cloning, reproduces the
> > problem.  This can eliminate a lot of extraneous issues that
> > have to be considered when you deal with real, preexisting
> > accounts.
> 
> It is the simplest account.  It's just an out-of-the-box account.  OK, 
> captive, but I changed that with no effect.  
> 
> > Think about what cloning does.  It copies the UIC by default,
> > retains various settings including device, directory,
> > LGICMD, and held identifiers. It preexpires the (no longer
> > valid) password.  If the UIC is the same, it will refuse
> > to create an identifier to match the new username, and this
> > anomaly will continue even if you later change the UIC
> > as a separate step.  There is, however, a variant to
> 
> Sorry, by "cloning" I mean that I set it up analogously to another 
> account, but of course it has its own UIC and the files in its login 
> directory are used by it.  
> 
> > With regard to complexity, I recommend testing
> > pure vanilla, non-captive accounts.  There are some
> > stringent requirements for the latter that are best
> > avoided at this point.
> 
> That's essentially what I'm doing.  As I said, I did change it to
> non-captive, but with no effect.

Is the password pre-expired for this user?