You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Signatures must be provided for software releases to achieve the OpenSSF Best Practices Silver Badge.
According to the Zowe Release v2 GitHub action (see https://github.com/zowe/zowe-release/actions/runs/4814098720/jobs/8571411479 for an example), we are already generating hashes and signatures for release packages (see console output below). Can we post these on the Zowe downloads page along with some guidance on where users can find the public key and how they can verify the signatures?
Note that in the past, Zowe.org appears to have provided signatures and hashes along with instructions on how to verify the signatures: https://www.zowe.org/post_download
The text was updated successfully, but these errors were encountered:
Note: Signatures must be provided for software releases to achieve the OpenSSF Best Practices Silver Badge.
According to the Zowe Release v2 GitHub action (see https://github.com/zowe/zowe-release/actions/runs/4814098720/jobs/8571411479 for an example), we are already generating hashes and signatures for release packages (see console output below). Can we post these on the Zowe downloads page along with some guidance on where users can find the public key and how they can verify the signatures?
Note that in the past, Zowe.org appears to have provided signatures and hashes along with instructions on how to verify the signatures: https://www.zowe.org/post_download
The text was updated successfully, but these errors were encountered: