Skip to content

Maybe more explanations needed? #153

@ndrean

Description

@ndrean

If I encrypt a field, it has a hash version in the db. It seems (?) that the encryption key is an env key (the rotation if I read correctly) so that when you query, you may need to hash the input, query against the hash column and then with this code decrypt the corresponding value at that row. Is this ti? Is this automated in some way? It is not clear for me.

  • If I query an (encrypted) field, I want to pass the field as it is in the query, so that the type is in charge of the process above (-> hash, query, decode).
  • If I insert a field (to be encrypted). I just want to pass the field, and the type automatically inserts the corresponding hash.

Is this the way it works?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions