Skip to main content

Verifying Access Server Downloads with SHA256SUM

When downloading Access Server files manually, you can ensure that the files you receive are authentic and have not been tampered with. One way to do this is by using SHA256 checksums, which provide a unique signature for each file. You can compare this signature with the one we provide to confirm the integrity of the downloaded files. If the checksum matches, you can be confident that the file is intact and authentic.

SHA256 checksums for Access Server files

Artifacts

File Name

SHA256SUM

openvpn-as-3.0.1_84b60e70-1.el8.x86_64.rpm

934106ffab7366eb4f4d98aab3fded809c5991b3604f0bd73bfc88a72ee4dc08

openvpn-as-3.0.1_84b60e70-1.el9.x86_64.rpm

a2cabc401b90b721a566360985b7467bea72a3cf7612e2230cf63e3b790e7af0

openvpn-as_3.0.1-84b60e70-Debian11_amd64.deb

d414a6715692fc5fac7086c4529c0e20df99752a8b0d7c1e80c96feacb3d5bc8

openvpn-as_3.0.1-84b60e70-Debian12_amd64.deb

ba1aca4491fdba3612f0a01c9fb1b199832d82db4d940f181ccc0621178fca10

openvpn-as_3.0.1-84b60e70-Ubuntu22_amd64.deb

09995a070a814fdb7ec40bb734cd230a11e595438eebfbbf54bcfbb4d0924c46

openvpn-as_3.0.1-84b60e70-Ubuntu22_arm64.deb

2450815874d6f8458400d8933548f663120819043fc4e555f3d2fb17926b7b59

openvpn-as_3.0.1-84b60e70-Ubuntu24_amd64.deb

5d1d630e3c5da3b613414e791a63c7413c07f97659a27377b532135ff1b453dc

openvpn-as_3.0.1-84b60e70-Ubuntu24_arm64.deb

df40adc8192f28b15f51921662386a3c5661180adc513a45beeaafaeb253b899

OAS_2.14.3.ova

562790650b79aecdc0b11465b0490f0e416d8569150628bceb608675ce10d4b5

OAS_2.14.3.zip

b3f6f4aa1b4d18b5754dc5b7f615dda9b8e179a9bd34a2a20ee496b13831970a

openvpn-as-bundled-clients_34_all.deb

78230a34b0d9b96774002f819fd709fdfe531621d5f794b5814cb698f091b56c

openvpn-as-bundled-clients-34-1.noarch.rpm

972dd2d162ac142d3882927990892fe134fa9e5726586df232f61adef57c1f32

Scripts

File Name

SHA256SUM

Version

install.sh

a290bb65ded603ed4647cd1aca53f0159d981a57366f3dd551013bf91444f625

1.6

bridge-down.sh

279a3321fd2760d6eb1acb0ba71c9b862bc33c9ced1efa775142d4697b28a848

1.0

bridge-up.sh

5538ee6e9d6cb2e2bb5882d54c69fd044ca89375c1406ad5432877d01369c091

1.0

aws-updown.sh

8ecd0465d6ba39ba376c76f129aaa6ac303c47f9783810b25fe1591e6270a77b

1.0

ipsec.conf

4da7378f563f079ecd635b2fb7201308ab33269b707a71b687c234a6dfb9167d

1.1

ipsec.secrets

46fe56cd944fb8c87c7fbf24d50c9730e361228be5b57a5de04dac0f901fff35

1.0

pascrs.py

a260aaf39d7b8d3cf6474a852c69a50c7929c4839d5a323a1671fbc69949e9b2

1.0

pasvar.py

4c1c45fa98b39d3372a7da1fcc6437241cb46a111ae98cb60a3e08c5428c0a44

1.0

post_auth_custom_auth.py

55f2fdb1d7b38d635b57443f4ab0e9aee2717d94e06ec5b14c36ca4a36397a08

1.0

post_auth_ip_address_checking.py

c62a78ec338815f9548f77d76166b5a2c050d79db6471fcf9f7fc040fa7d3741

1.0

post_auth_ldap_autologin_dbsave.py

8fefb1df6a82dda1181fcb25ae9ae21a44e437196e4829d963ec53394d9ce537

1.1

post_auth_mac_address_checking.py

608074f2de974145d9fd7646359504ab6f07759c4db8f8ab7ff290c4caa1af76

2.1

post_auth_pas_only.py

b4cf2e3d497516c59a4a7ba55aa8a3cbf538940122543652ab03d0f6eabb486f

1.1

post_auth_radius_mapping.py

0d838425e6387e2b0846c86e6ae30c2abc583b938c866911dbbdb306850410b1

2.1

post_auth_saml_group_mapping.py

fac6bea6ecb35c1e069ebe7a2f70460b71071c268661def4ecb80502001ec8e6

1.1

SHA256SUM is a tool that generates a 256-bit hash (a unique string of characters) for a file. A calculation based on the file's contents generates this hash, and if even one byte of the file changes, the hash will be completely different. By comparing the hash of your downloaded file with the official hash provided by us, you can verify that the file hasn't been altered or corrupted.

  1. Verifying the file ensures it wasn't corrupted during the download process.

  2. Comparing the checksum helps protect against any unauthorized modifications to the file.

  3. Downloading a file from an official source may not always guarantee safety if the file is intercepted and altered. To ensure the file is legitimate, you should verify the checksum.

We recommend using the install.sh script from the Access Server Portal, as it leverages the operating system's built-in package manager to automatically authenticate packages with a trusted signing key, eliminating the need for manual verification. However, if preferred, you can manually validate the install.sh script's integrity using the SHA256 checksum provided in the table above.

For offline installations, you can manually check the integrity of any downloaded files using the provided SHA256 hashes. To verify a downloaded file, follow these steps:

  1. Connect to the console and get root privileges.

  2. Download the install script from the Access Server portal or manually download the Access Server file.

  3. Calculate the checksum of your downloaded file:

    sha256sum openvpn-as-x.deb1
    

    1

    Replace the filename with the file you want to check the integrity of.

  4. After running the command, the tool returns a checksum.

  5. Compare the checksum with the one listed for the file in the scripts table. If it matches, your file is authentic.

  • If you're using the installation script from the Access Server Portal, you can verify the integrity of install.sh by comparing the SHA256SUM and version from the scripts table.

  • The easiest way to ensure the authenticity of Access Server installation files is to use our install script, which leverages the operating system's built-in package manager to authenticate downloaded packages using a trusted signing key. This eliminates the need for manual file verification. However, suppose you prefer downloading the installation files manually, such as for offline installations. In that case, you can authenticate their integrity by comparing the files against the provided SHA256 hashes to ensure they haven't been tampered with or corrupted.