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

Provide a secure method of upgrading Fury #53

Open
propensive opened this issue Mar 25, 2024 · 1 comment
Open

Provide a secure method of upgrading Fury #53

propensive opened this issue Mar 25, 2024 · 1 comment

Comments

@propensive
Copy link
Owner

There should be a fury upgrade option in the menu which checks for new releases on https://fury.build/. If a newer version is available, it should be placed in a special location. The launcher script should check that location before starting. If there is a file present, it should replace itself with the new version, and exec that (passing in all the same parameters).

Downloading should verify the downloaded file's checksum using a public key on Fury's classpath. Built artifacts should be distributed with corresponding .sig files.

@propensive
Copy link
Owner Author

This check should only be done when launching Fury; not for each invocation.

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

1 participant