Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some arkanelinux deployments missing signature file #15

Open
user1-github opened this issue Nov 30, 2024 · 3 comments
Open

Some arkanelinux deployments missing signature file #15

user1-github opened this issue Nov 30, 2024 · 3 comments

Comments

@user1-github
Copy link
Contributor

user1-github commented Nov 30, 2024

Probably unrelated to Arkdep, but looking at repo.arkanelinux.org/arkdep/arkanelinux , I see that from time to time some deployments are missing their signature file - particularly 2024-09-08, 2024-10-09 and 2024-11-30.

When doing "sudo arkdep deploy" it doesn't cause any issue with the update, the signuture check just fails and the update continues as usual. But for the sake of security, it's better to make sure that every new deployment has its signature file.

@dennis1248
Copy link
Member

dennis1248 commented Nov 30, 2024

My fault, I sometimes forget to generate the signature because it is a manual process. I will automate this soon so it can't go wrong anymore.

I plan on automating the entire image creation process, so it automatically generates new images according to a set schedule.

I pushed a sig for 2024-11-30.

@user1-github
Copy link
Contributor Author

Thanks, also a suggestion - Arkdep should stop the update in case the sig file is not found, because I think that could theoretically be exploited.

@dennis1248
Copy link
Member

Thanks, also a suggestion - Arkdep should stop the update in case the sig file is not found, because I think that could theoretically be exploited.

If you set gpg_signature_check in /arkdep/config to 2 it will force this requirement. I will make this default in a future ISO release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants