v1.2.1

v1.2.1

Changes

Added some features to increase security and general utility

• Data files 'data' fields are now encrypted using aes-256-gcm
• Added a timeout to terminate the app after no interaction was received for some time
• The contents of the data file are now entirely editable through the CLI
• Added a show-password option to change whether the password is hidden, masked, or shown
• Added the ability to create datafiles through the CLI with the --create-file flag
• Added a --quick flag to skip most confirmation prompts
• Added the option to export the data from the data file in an unencrypted manner
• Added an --import flag to import exported files (and also to convert v1.1.0 data files to v1.2.1)

How to import data files from v1.1.0 into the new CLI

1. Remove the 'checksum' property
2. Add a property 'version' with value 1
3. Convert all users that are just strings into user objects
4. Add missing properties to all user objects

Given the following data file ./old_data.json

{
    "checksum": "$argon2id$v=19$m=262144,t=20,p=4$a3kY9aYCESurePtX/tvwXg$nrdG3vH1m0Eq3wgF60zpr+V+T/LMO6VBz/et80PB",
    "services": {
        "example.com": [
            { "name": "admin", "salt": "abc", "length": 45, "note": "second-account uses this for recovery" },
            { "name": "second-account", "length": 25 }
        ],
        "home-server": [
            "admin",
        ]
    }
}

you will need to convert it to the following

{
    "version": 1,
    "services": {
        "example.com": [
            { "name": "admin", "salt": "abc", "length": 45, "note": "second-account uses this for recovery" },
            { "name": "second-account", "salt": "", "length": 25, "note": "" }
        ],
        "home-server": [
            { "name": "admin", "salt": "", "length": 30, "note": "" }
        ]
    }
}

You can then set up a new data file with node . --create-file ./data.json and import the data with node . -f ./data.json --import ./old_data.json