HP-UX Secure Shell A.05.80.001, A.05.80.002, and A.05.80.004 Release Notes, July 2011 (5900-1844)

Table 2 Scenarios where pam_setcred Generates Error Messages (continued)
Error MessagesKeyServ RunningUsePrivUser
Permission deniednonoroot
Permission deniednononon-root
Permission deniedyesyesroot
No messageyesyesnon-root
Permission deniedyesnoroot
Permission deniedyesnonon-root
• A Kerberos ticket on a Secure Shell server system gets inadvertently deleted in the following
scenario:
1. User U1 creates a Kerberos ticket file on a Secure Shell server system, S1.
2. The SSH server on S1 is set up for PAM_KERBEROS authentication.
3. User U1 now remotely connects to the SSH instance on S1 using public-key authentication.
4. User U1 exits.
The kinit-generated ticket file created in Step 1 gets deleted when the user exits the Secure
Shell session.
Workaround: Create the Kerberos ticket file (Step 1) in a non-default location and selectively
communicate this file name to Secure Shell processes using the KRB5CCNAME environment
variable.
• The chroot functionality does not work if the UseLogin configuration directive in
sshd_config is set to YES.
• In a chroot-ed environment, you do not see a subset of syslog messages. HP-UX Secure Shell
writes syslog messages during authentication and when the session is terminated. The syslogd
daemon reads the syslog messages written by all subsystems and reports it to the /dev/log
file. In a chroot-ed environment, the sshd daemon writes its syslog messages to
<newroot>/dev/log. You cannot link the <newroot>/dev/log file to the /dev/log
file, so you are not able to view the subset of syslog messages.
Workaround: Please see HP-UX - How to Configure SFTP Logging in a Chrooted Environment?
Users of chroot-ed HP-UX Secure Shell environments must be aware that a subset of messages
written by the sshd daemon will not show up in syslog.
• QXCR1000868044
This occurs when sshd is being used by SIM System Insight Manager and the CMS and gWLM.
In some systems, when kerberos authentication is set to yes, ChallengeResponseAuthentication
is commented out in sshd_config, and kerberos is not configured in the system, sshd will have
a very long timeout.
• QXCR1001102145
ssh-keygen displays only the first key and does not handle multiple keys present in a file. This
issue is same as http://bugzilla.mindrot.org/show_bug.cgi?id=1319
• NO JAG
ECDSA key storing on LDAP server is NOT supported on HP-UX Secure Shell A.05.80.
HP-UX and the strong random number generator
HP-UX Secure Shell requires that a random number generator to be located on the system. It
searches for /dev/urandom and /dev/random (in that sequence) on the system and uses the
8 HP-UX Secure Shell A.05.80