Hi Domingo,
SSH has received reports of this bug, and it has
been resolved for the next version, due out in June.
Best Regards,
Steph
"Fernandez Garcia, Domingo" wrote:
>
> Hey everyone!
> We have installed ssh-2.4.0 server on AIX4.3 and SSH Secure Shell Client for
> Windows.
> When we connect to the server, we obtain the message "WARNING: putuserattr
> SEC_COMMIT failed: No such file or directory". This seems to be related with
> the users of AIX. Looking for the structure of files, we find that the file
> /etc/security/lastlog is damaged.
> We observe that if we connect to the server with telnet it registers the
> connection correctly in the file lastlog, while if we connect with ssh the
> file lastlog is a not valid file.
> After to put a null lastlog, if we connect with ssh it registers in lastlog
>
> >more /etc/security/lastlog
> ;
> $^Kttyp0sipc5.si.unican.es
> lastlog: FIN
>
> Any idea?
> -------------------------------------------------
> Domingo Fernandez
> Servicio de Informatica. Universidad de Cantabria
> [EMAIL PROTECTED] Tfno. 942201084
> Fax 942201103
--
*********************************
Stephanie Thomas
Technical Support Specialist
SSH Secure Shell
GIAC Certified
Unix Security Administrator
SSH Communications Security Inc.
http://www.ssh.com/support/ssh
*********************************
