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
{{ message }}
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.
I think deployiso should have 2 more options available, one to sign the iso with "gpg -b" and another that generates a hash. It is very important to verify hashes and sigs for the iso to demonstrate that the iso didn't get corrupt during download and that it is signed by a artix dev which means there isn't anyway that something malicous is in the iso.
The text was updated successfully, but these errors were encountered:
But that doesn't stop somebody from distributing a fake iso with a different key than ours. The iso needs to be signed after it is fully generated with a .sig file that we upload to SF. If the .sig file does not contain our keys that means it was modified by somebody else who is not a developer of artix. That is the only way to ensure that the iso is from us and not from somebody else who gained ftp access to a server.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think deployiso should have 2 more options available, one to sign the iso with "gpg -b" and another that generates a hash. It is very important to verify hashes and sigs for the iso to demonstrate that the iso didn't get corrupt during download and that it is signed by a artix dev which means there isn't anyway that something malicous is in the iso.
The text was updated successfully, but these errors were encountered: