Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.001
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.001.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.001.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.001.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.001.asc perl-win32-bin.exe.001
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.001.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.001: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.002
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.002.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.002.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.002.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.002.asc perl-win32-bin.exe.002
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.002.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.002: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.003
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.003.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.003.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.003.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.003.asc perl-win32-bin.exe.003
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.003.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.003: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.004
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.004.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.004.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.004.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.004.asc perl-win32-bin.exe.004
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.004.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.004: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.005
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.005.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.005.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.005.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.005.asc perl-win32-bin.exe.005
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.005.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.005: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.006
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.006.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.006.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.006.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.006.asc perl-win32-bin.exe.006
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.006.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.006: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.007
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.007.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.007.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.007.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.007.asc perl-win32-bin.exe.007
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.007.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.007: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.008
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.008.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.008.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.008.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.008.asc perl-win32-bin.exe.008
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.008.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.008: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.

Each official software release at the ASF is digitally signed with a detached PGP signature, as well as accompanying checksum files for extra verification. You can verify the PGP signatures using PGP or GPG.

Verifying the PGP signature

To verify the PGP signature, you will need the following files:

1. The release artifact itself: perl-win32-bin.exe.009
2. The perl release signing key list: perl.txt
3. The detached signature file: perl-win32-bin.exe.009.asc

Make sure you get these files from the official apache.org release distribution service, rather than from a mirror, as we cannot verify the authenticity of mirrors.

Once you have all the needed files, you can verify the release artifact as follows:

 % pgpk -a perl.txt
 % pgpv perl-win32-bin.exe.009.asc
 OR
 % pgp -ka perl.txt
 % pgp perl-win32-bin.exe.009.asc
 OR
 % gpg --import perl.txt
 % gpg --verify perl-win32-bin.exe.009.asc perl-win32-bin.exe.009
 

Verifying the checksum files

If you're unable to verify the PGP signatures, you can instead verify the checksums on the files. However, PGP signatures are superior to checksums, and we recommend you verify using PGP whenever possible.

The following checksum files are available for this release:

• perl-win32-bin.exe.009.md5 weak!

When multiple checksums are available, we recommend you use the strongest checksum algorithm found. In order of strength, they are: sha512, sha256, sha1, md5

Verifying SHA1, SHA256, and SHA512 checksums

Most Unix systems have a program called shasum included in their core distribution, which can be used here. To verify a checksum file, download it to the same directory as the relase artifact you downloaded, and run: shasum -c [checksum-filename]

The shasum program should emit the following response: perl-win32-bin.exe.009: OK. If the program indicates any errors or warnings, there may be authenticity issues with the artifact, and you should let us know at security@apache.org.

On Windows you can use the following command in a command line window to generate a checksum for the artifact, for instance: certutil -hashfile <filename> SHA512.

You can then compare this checksum value to the value in the checksum file.

Verifying MD5 checksums

Some older artifacts may only have an MD5 checksum file associated with it. As MD5 is now considered a weak algorithm, we strongly advise that users verify such artifacts using the PGP method described above. Should you have a need to verify the MD5 checksum file, you can use the Unix program md5sum in a similar manner to how SHA checksums are verified: md5sum -c [checksum-filename]. The response from the md5sum program is similar to that of the shasum program, and an OK response should always be expected.