Maybe if we beat on SSH Communications enough they could finally get
all the features into ssh2 that were in ssh1.
Jon
On Wed, Jun 13, 2001 at 10:42:44AM -0500, Shane Williams scribbled:
> On Tue, 12 Jun 2001, Jonathan Burelbach wrote:
>
> > We are having problems with ssh communications ssh-2.4.0 non-commercial
> > on solaris 8. When an account is created so that the user must change
> > the password on login or the password has expired, they never get the
> > prompt to change passwords unless they specifically use a ssh1 client
> > to log in. The syslog shows the following messages:
>
> I asked this question of the commercial ssh a year ago and at least at
> that time, the answer was "password expiration doesn't work, but we're
> working on it." I'd be elated if somebody can correct me on this
> since from my perspective this makes ssh nearly worthless.
>
> As it stands, if I want to expire my users passwords, which is a good
> thing, I have to tell them to use telnet, which is a bad thing. And
> it's not just a matter of passing the password in the clear that once,
> it's that it confuses the issue of why ssh is so important in the
> first place. I don't need one more thing impeding my users from
> adopting ssh.
>
> --
> Public key #7BBC68D9 at | Shane Williams
> http://pgp.mit.edu/ | Systems Administrator UT-GSLIS
> =----------------------------------+-------------------------------
> All syllogisms contain three lines | [EMAIL PROTECTED]
> Therefore this is not a syllogism | www.gslis.utexas.edu/~shanew
--
=========+=========+=========+=========+=========+=========+=========+
Jonathan Burelbach [EMAIL PROTECTED]
Unix Systems Administrator [EMAIL PROTECTED]
NIH/CIT/DCSS/SOSB;12 South Dr.;Bldg 12B/2N207;Bethesda (301) 496-7372
