In a UNIX environment where authentication for SAS^® 9.4M6 is configured to use PAM calling SSSD, a Segmentation Violation error occurs if users are not defined in either /etc/passwd or /etc/shadow. In these cases, an asterisk is returned to the sasauth module by getpwnam(), resulting in a segmentation violation when sasauth attempts to encrypt the password.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	Base SAS	64-bit Enabled AIX	9.4_M6	9.4_M6	9.4 TS1M6	9.4 TS1M6
		64-bit Enabled Solaris	9.4_M6	9.4_M6	9.4 TS1M6	9.4 TS1M6
		HP-UX IPF	9.4_M6	9.4_M6	9.4 TS1M6	9.4 TS1M6
		Linux for x64	9.4_M6	9.4_M6	9.4 TS1M6	9.4 TS1M6
		Solaris for x64	9.4_M6	9.4_M6	9.4 TS1M6	9.4 TS1M6

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

A fix for this issue for SAS Threaded Kernel Secure 9.4_M6 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/E5U.html#64112

---

If you use SSSD through PAM to authenticate users whose user IDs are not defined in /etc/passwd or /etc/shadow, an asterisk is returned to sasauth, resulting in a Segmentation Violation error when calling crypt().

Type:	Problem Note
Priority:	high

Date Modified:	2019-04-30 09:44:55
Date Created:	2019-04-26 09:40:07