Leading up the garden path with crypto capabilities #2625
adminy
started this conversation in
Documentation
Replies: 1 comment
-
What you said is indeed correct, but I believe that the original intention of SurrealDB's design encryption is to build multiple different levels of management user systems. To ensure security, this operation is completed before the management system goes online and does not involve the client. Adding internal management users to the client itself is an extremely dangerous thing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I understand that is really cool that you can encrypt information inside the database, and these are pretty cool features of surreal, but don't encourage bad practices in the docs, where you hash the login password as that should be completely client side. Before it reaches any sort of protocol to get to surreal, it should arrive in the encrypted form. Docs counter the intuition of that practice.
Beta Was this translation helpful? Give feedback.
All reactions