We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the private key used te encrypt and decrypt the config values is stored inside the .comfy/config file in clear text.
.comfy/config
It would be better to store this private key (and some perhaps some other crypto informations) into a secure file like .comfy/privatekey or something.
.comfy/privatekey
I thought of some implementations, but none of them are satisfactory from the security and/or UX standpoint.
Any idea on how to implement a solution that is both secure and easy to use?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, the private key used te encrypt and decrypt the config values is stored inside the
.comfy/config
file in clear text.It would be better to store this private key (and some perhaps some other crypto informations) into a secure file like
.comfy/privatekey
or something.I thought of some implementations, but none of them are satisfactory from the security and/or UX standpoint.
Any idea on how to implement a solution that is both secure and easy to use?
The text was updated successfully, but these errors were encountered: