Deleting wrongly encrypted history entries on server

[ellie]

Hey!

@atuinuser

it just creates a new one I assumed

That’s right!

Ah I see - you can resolve this with the following, though note that data encrypted with the wrong key is unrecoverable

Sync v2 testing

So, first I’d disable auto_sync to make sure no hosts push bad history atuin store purge - this will delete all records in the store that cannot be decrypted with the current key atuin store verify - verify that the previous operation was successful atuin store push --force - this will delete all records stored remotely, and then push up local data. Run this on the machine that has been purged atuin store pull --force - this does the opposite to (3). Delete all local data in the store, and pu…

In future, and to anyone reading this from search engines; Please do not manually copy around key files. atuin login has a process to automatically migrate keys if you try to login with a different one