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.

Sign up for GitHub

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

Jump to bottom

Store unlock information remotely #1

Open

duck-nukem opened this issue Jan 5, 2021 · 1 comment

Owner

duck-nukem commented Jan 5, 2021

Machines should have a unique machine ID.
A remote entity should store encryption keys per machine id (e-mail, remote http server, etc)

Owner Author

duck-nukem commented Jan 24, 2021 •

edited

Loading

Thoughts:

Communication with a remote server
- can be traced to owner
- can be shut down by the hosting company
Send email
- would need to store credentials for SMTP auth?
Key format
- would be reversible, keygens would appear

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment