This SAS Note provides instructions about how to validate your signatures for SAS Viya downloads. This information is related to the SAS Statement Regarding SAS^® Viya^® Orders That Contained An Incorrectly Distributed Intermediate Entitlement Server Private Key security bulletin. 

Verify That Any Downloaded Code Has Been Signed by SAS

Follow the instructions below to manually verify that the code-signing key used for SAS packages is installed on your system. This verification process ensures that the package is valid and originated from SAS. 

Linux Installations: 

In Linux installations, use the RPM Package Manager command to verify that the correct SAS code-signing key is used for your SAS packages. The following command confirms that all SAS packages are signed. The output shows "OK" for each valid signature and "NOT SIGNED" if the package has not been signed by SAS.

Windows Installations: 

Use the PowerShell cmdlet to validate signatures. Here is an example: 

This command generates the following table and displays a status of Valid for each valid signature and NotSigned if the package has not been signed by SAS.

Operating System and Release Information