PAM Software Binary Distribution and Signatures

PAM Binary Components with MD5, SHA512 and PGP signatures

PGP public key fingerprint:

Copy

85CA89FD4F9619F02E5DFB5486C9E8312C12ADD2

PAM Component Integrity

To verify the integrity of each PAM binary, we provide the MD5 and SHA-512 checksums and an OpenPGP signature. After you download any binary, you should calculate a checksum for your download and make sure if matches ours above. You may also match the OpenPGP signature against the provided key file.

Windows Integrity Check

You can use Microsoft methods to check the binary’s checksum or any other method you are comfortable using. In the example below, we will use CertUtil in PowerShell to calculate the hashes.

Copy both the downloaded binary and the MD5 or SHA512 hash file to the same directory and from within this location execute the command:

MD5:
Copy
```
CertUtil -hashfile <FILE> MD5
```
SHA512:
Copy
```
CertUtil -hashfile <FILE> SHA512
```

Compare the computed hash to make sure it matches the value from the download hash file.

You can verify the PGP signature using the below command, if available, or another Windows-based OpenPGP verification tool like Gpg4win.

PGP:
Copy
```
gpg --verify <FILE.asc>
```

Linux Integrity Check

To verify hashes on Linux, copy both the downloaded binary and the MD5 or SHA512 hash file to the same directory and from within this location execute the command:

MD5:
Copy
```
md5sum <FILE>
```
SHA512:
Copy
```
shasum -c <FILE.sha512>
```

Compare the computed hash to make sure it matches the value from the download hash file.

You can verify the PGP signature using the below command from this same directory with the downloaded PGP file:

PGP:
Copy
```
gpg --verify <FILE.asc>
```
PGP2:
Copy
```
gpg2 --verify <FILE.asc>
```

PGP public key:

Copy