resilar
resilar
Hmm... That's an interesting problem that I was unaware of. Thanks for notifying me. AFAIK the iOS use-case of sqleet is not very popular and there already exist (poor) workarounds,...
>Hm, yes, it could be done that way, but this is sort of hijacking PRAGMA key=... and could easily cause mistakes in using it. For example, this approach requires some...
Oops, sorry for the reference spam. Anyway, this took longer than expected. The implemented URI API in [uri branch](/resilar/sqleet#uri) is experimental. It is reasonably tested and in a usable state,...
Documentation and refactoring of the URI interface is still in progress. I have been busy lately. --- I just realized that the new `VACUUM INTO` command can be used to...
Commit 3fc3fc4 in `uri` branch adds [`README.md` documentation of the URI interface](https://github.com/resilar/sqleet/blob/3fc3fc4ca3244205349dec1450c0fc25c1b0a9cb/README.md). Some work is still needed before merging the feature into master. In particular, support for changing URI settings...
Based on initial testing, the `VACUUM INTO` thing seems to work perfectly for changing URI settings of an existing database.
Current [`uri`branch](https://github.com/resilar/sqleet/tree/uri) now supports changing database URI settings via `VACUUM INTO` command. ``` $ rm -f secrets.db skipped.db $ ./sqleet 'file:secrets.db?key=hunter2&salt=SALTsaltSALTsalt' 'CREATE TABLE f(x,y)' $ xxd secrets.db | head -n3...
I agree that (re)key on in-memory or temporary database should fail or at least return a warning. I'm afraid, though, that there is no clean way to implement this without...
Holy shit @ `SQLITE_HAS_CODEC` removal. That's a game changer, lol. SQLite3 patching or hacky VFS-based encyption it is then. That sucks.
I agree with your thoughts about VFS-based encryption. VFS encryption is the way forward, but it will require a lot of work to get all the details right (if it...