Replies: 3 comments
-
Why? File systems can already be encrypted, as can files. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Why? File systems can already be encrypted, as can files. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the heads-up @rzmk . We should look into this when we revisit #1982. And to your question @ondohotola , the ambition is to have a "PDF for data" - that includes metadata, schema, is secure, traceable, and have the ability to manage permissions even after sending the data. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Seems like a relatively new crate libsodium-rs is available based on the libsodium API and there are examples of usage in the README. Could be useful to integrate with qsv or behind a feature flag since users might need libsodium installed on their system (not sure if they need to have libsodium installed or not but installation instructions for the major OSes are available in the README). Some ideas I have are encrypting data, columns, cells, file(s), etc. The Kryptor CLI tool could be viewed for reference use cases of libsodium in a CLI tool particular for file encryption and signing.
Beta Was this translation helpful? Give feedback.
All reactions