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
[email protected]
I would like to be able to view the public key for other nodes via my mobile app. This is currently not possible today.
Having access to see the public key for other nodes would allow me to verify their key while in the field. Additionally, I could use this field for my own node to share my public key without having to go to the authentication page. Going to the authentication page reveals my private key along with my public key, both in plain text, which is a security issue.
This feature would increase security for senders and receivers, raising the bar for security of the system as a whole.
No response
The text was updated successfully, but these errors were encountered:
This is a much better solution. Keep the security menu the same and add the public key to the node card and make the field selectable.
Sorry, something went wrong.
No branches or pull requests
Contact Details
[email protected]
Tell us your idea.
I would like to be able to view the public key for other nodes via my mobile app. This is currently not possible today.
Having access to see the public key for other nodes would allow me to verify their key while in the field. Additionally, I could use this field for my own node to share my public key without having to go to the authentication page. Going to the authentication page reveals my private key along with my public key, both in plain text, which is a security issue.
This feature would increase security for senders and receivers, raising the bar for security of the system as a whole.
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: