You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd love to be able to access SQL tables, encrypted by the SQLCipher via Velociraptor. It could be as optional argument addition of key to the existing SQLlight plugin, or creating the new one.
Happy to work on the feature myself. But before I invest too much time in it, was wondering, if there are any general concerns that I should consider or push back on landing such a feature on main brunch, from the core developers.
Thank you
The text was updated successfully, but these errors were encountered:
It would be a nice addition - the issue is more about how to pass key material to the plugin. For other plugins we sometimes pass key material in the environment or in secrets or in parameters. I dont know much about SQLCipher but does it use the same key for all the rows in the same file or does it have more fine grained control?
The other issue is that we need to make sure the sqlite bindings are built hermetically (i.e. without linking external libraries) so this means compile the C code directly in the build process. I am not sure how you can enable that extension in practice.
As far as I know usually key will be available on the machine locally, one key for the whole DB.
Would it be possible to use VQL to extract key and pass it to sqlite plugin? Wondering if something like that is already done in the user friendly manner.
I'd love to be able to access SQL tables, encrypted by the SQLCipher via Velociraptor. It could be as optional argument addition of
key
to the existing SQLlight plugin, or creating the new one.Happy to work on the feature myself. But before I invest too much time in it, was wondering, if there are any general concerns that I should consider or push back on landing such a feature on main brunch, from the core developers.
Thank you
The text was updated successfully, but these errors were encountered: