Skip to content

Audit what survives a vault being forgotten, deleted or wiped #134

Description

@Esdex

What

When a vault stops existing - forgotten, deleted, or wiped by panic mode - what does Arcanum still hold about it? I want that answered path by path rather than assumed.

Why now

The media index survived. media_files has no foreign key to cascade from, and nothing deleted its rows, so removing a vault left behind the names and paths of every file that had been inside it. The vault itself is encrypted; the list of what was in it was sitting next to it in plain rows. Fixed in 6145cf4.

It was found by accident: a confirmation dialog was reworded to promise that the cache goes, and checking whether that was true is what turned it up. That is not a way to find the rest of them.

What to check

Every path by which a vault stops existing:

  • Forget, from the vault list and from the vault config menu
  • Delete the vault file
  • Panic mode, in each of its configured actions
  • A vault whose file is gone when Arcanum next looks

And for each, what is left:

  • thumbnails on disk
  • media_files rows
  • the persistable SAF URI permission taken when the vault was added from a picker - is it released, or does Arcanum keep a grant to a file it no longer knows about?
  • biometric credentials in the Keystore for that vault
  • the saved mount log, which quotes paths
  • anything in DataStore keyed by the vault id
  • crash logs, which can contain a container path

What "clean" means here

Nothing left that names the vault, its location, or anything that was inside it. A record that only says "a vault existed" is a different question and not this one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImprovement to an existing feature

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions