Openssh not logging to btmp

[Ken Penland_1]

Ok, I just installed the openssh depot provided by HP: T1471AA_A.03.61.002_HP-UX_B.11.00_32+64

I noticed that doing a last, shows every connection as being "still logged in" and lastb does not show any failed logins at all.

when trying it via telnet, last and lastb both work as expected.

I searched the itrc, and I have seen a couple other people that have similar problems, but no real answers that I could find....has anyone seen this issue before and have a solution for it?

[Donny Jekels]

do your self a huge favor. loose hp's port and compile OpenSSH yourself.

let me get off my soap box.

in sshd_config enable
UseLogin yes
UsePam yes

keep rocking .... go opensource
Donny

[Ken Penland_1]

UseLogin fixed the last portion, it now shows the login/logout times, but lastb is still broke....

the UsePam option didnt work:

/opt/ssh/etc/sshd_config: line 83: Bad configuration option: UsePam
/opt/ssh/etc/sshd_config: terminating, 1 bad configuration options


as for using HP's vs compiling my own, I actually did start out downloading the latest and greatest and trying that, but it didnt supported a trusted HPUX environment, so I went with HP's version, which did ;)

[Steven E. Protter]

I'm using the HP depot on ssh and respectfully disagree with the first post.

You may have a permission problem on the btmp file

My installation is correctly loggin all ssh logins.

Here are the permissions
on the btmp file.

/var/adm/btmp

rw root:other

No other permissions.

My guess is there is a daemon or permission problem.

inetd -c might help.

I have found the HP port of openssh to be excellent and reliable.

SEP

[Ken Penland_1]

nope, my perms are the same...seems if it were a daemon or permissions problem, it wouldnt work for telnet either..but it does...

[Ken Penland_1]

if it helps, here is everything that is NOT a comment in my sshd_config file:

# grep -v "^#" sshd_config

Protocol 2

AuthorizedKeysFile .ssh/authorized_keys


KerberosAuthentication yes

X11Forwarding yes
X11UseLocalhost no
UseLogin yes

Banner /etc/issue

Subsystem sftp /opt/ssh/libexec/sftp-server

[Donny Jekels]

SEP, no dis-respect. try using scp of large files with HP's port. >2Gb.

anyway, not to discredit HP for their work on porting openssh to hp, much needed I guess. but very late in the game. I am running ssh at 64 bits for way to long to switch to their verion. whihc is compiled at 32 bts

[Kevin Wright]

I see this problem as well, and do not know if there's a fix.

Inetd -c only effects the internet daemon, inetd, causing it to re-read the conf file, /etc/inetd.conf.
Ssh runs a standalone daemon, sshd, which is not called by inetd, therefore will have no effect.

[Mic V.]

Hopefully HP is following this thread. :)

[Steven E. Protter]

I've tested HP's latest port 3.6.12 with 20 GB Golden image files.

The times were admirable.

Of course I made sure the target filesystem had largefiles enabled.

I did not sense any disrespect or anything.

Just an amicable disagreement.

With minimal work the latest depot should perform nicely.

Though compiling openssh is a good excersize. Wish I had time for that.

knocked off a couple of ugly support calls in the last two days, hence more time to post here.

SEP

[Ratzie]

Had the exect same problem a couple of months ago. Went thru days of trouble shooting, and patching, my system was patched up to date!!!

Placed a support call with HP, and they are aware of the problem and it will be fixed in the next release.

They did send me a "Prerelease" of A.03.71.000

I can send it to you if you want.

Fixed the problem, presto!!!

[Andrew Cowan]

No disrespect SEP, but I have to agree with Donny here. I'm working with "official" ports from IBM and "HP" here, and they both have bugs in them.

I understand the convenience of getting a "packaged" version of OpenSSH, however, all HP have done is to compile it using the options that the technician thought would be the mostly likely to suit most people, and therein lies the problem. SSH in common with other security products is highly configurable, and where possible people should take the time to build their own binaries.

You should also ALWAYS ALWAY test every release at the lowest level since due to the nature of open-source development, bugs do creep in.