HPR4377: store and the command 2p1d5u

This show has been flagged as Clean by the host. Standard UNIX manager management is one of those computing problems you probably don't think about often, because modern computing usually has an obvious default solution built-in. A website prompts you for a , and your browser auto-fills it in for you. Problem solved. However, not all browsers make it very easy to get to your s store, which makes it complex to migrate s to a new system without also migrating the rest of your profile, or to share certain s between different s. There are several good open source options that offer alternatives to the obvious defaults, but as a of Linux and UNIX, I love a minimal and stable solution when one is available. The command is a manager that uses GPG encryption to keep your s safe, and it features several system integrations so you can use it seamlessly with your web browser of choice. Install The command is provided by the Store project. You can install it from your software repository or ports collection. For example, on Fedora: $ sudo dnf install On Debian and similar: $ sudo apt install Because the word is common, the name of the package may vary, depending on your distribution and operating system. For example, is available on Slackware and FreeBSD as -store. The command is open source, so the source code is available at git.zx2c4.com/-store. Create a GPG key First, you must have a GPG key to use for encryption. You can use a key you already have, or create a new one just for your store. To create a GPG key, use the gpg command along with the --gen-key option (if you already have a key you want to use for your store, you can skip this step): $ gpg --gen-key Answer the prompts to generate a key. When prompted to provide values for Real name, Email, and Comment, you must provide a response for each one, even though GPG allows you to leave them empty. In my experience, fails to initialize when one of those values is empty. For example, here are my responses for purposes of this article: Real name: Tux Email: [email protected] Comment: My first key This information is combined, in a different order, to create a unique GPG ID. You can see your GPG key ID at any time: $ gpg --list-secret-keys | grep uid uid: Tux (My first key) [email protected] Other than that, it's safe to accept the default and recommended options for each prompt. In the end, you have a GPG key to serve as the master key for your store. You must keep this key safe. Back it up, keep a copy of your GPG keyring on a secure device. Should you lose this key, you lose access to your store. Initialize a store Next, you must initialize a store on your system. When you do, you create a hidden directory where your s are stored, and you define which GPG key to use to encrypt s. To initialize a store, use the init command along with your unique GPG key ID. Using my example key: $ init "Tux (My first key) <[email protected]>" You can define more than one GPG key to use with your store, should you intend to share s with another or on another system using a different GPG key. Add and edit s To add a to your store, use the insert command followed by the URL (or any string) you want to keep. $ insert example.org Enter the at the prompt, and then again to confirm. Most websites require more than just a , and so can manage additional data, like name, email, and any other field. To add extra data to a file, use edit followed by the URL or string you saved the as: $ edit example.org The first line of a file must be the itself. After that first line, however, you can add any additional data you want, in the format of the field name followed by a colon and then the value. For example, to save tux as the value of the name field on a website: myFake123 name: tux Some websites use an email address instead of a name: myFake123 email: [email protected] A file can contain any data you want, so you can also add important notes or one-time recovery codes, and anything else you might find useful: myFake;_;123 email: [email protected] recovery email: [email protected] recovery code: 03a5-1992-ee12-238c note: This is your personal , use company SSO at work List s To see all s in your store: $ list Store ├── example.com ├── example.org You can also search your store: $ find bandcamp Search : bandcamp └── www.bandcamp.com Integrating your store Your store is perfectly usable from a terminal, but that's not the only way to use it. Using extensions, you can use as your web browser's manager. There are several different applications that provide a bridge between and your browser. Most are listed in the CompatibleClients section of store.org. I use FF, which provides a Firefox extension. For browsers based on Chromium, you can use Browser with the Browser extension. In both cases, the browser extension requires a "host application", or a background bridge service to allow your browser to access the encrypted data in your store. For FF, the install script: $ wget https://codeberg.org/FF/ff-host/releases//latest/install_host_app.sh Review the script to confirm that it's just installing the host application, and then run it: $ bash ./install_host_app.sh firefox Python 3 executable located at /usr/bin/python3 executable located at /usr/bin/ Installing Firefox host config Native messaging host for Firefox has been installed to /home/tux/.mozilla/native-messaging-hosts. Install the browser extension, and then restart your browser. When you navigate to a URL with an file in your store, a icon appears in the relevant fields. Click the icon to complete the form. Alternately, a icon appears in your browser's extension tray, providing a menu for direct interaction with many functions (such as copying data directly to your system clipboard, or auto-filling only a specific field, and so on.) management like UNIX The command is extensible, and there are some great add-ons for it. Here are some of my favourites: -otp: Add one-time (OTP) functionality. -update: Add an easy workflow for updating s that you frequently change. -import: Import s from chrome, 1, bitwarden, apple-keychain, gnome-keyring, kee, last, and many more (including itself, in the event you want to migrate a store). The command and the store system is a comfortably UNIX-like management solution. It stores your s as text files in a format that doesn't even require you to have installed for access. As long as you have your GPG key, you can access and use the data in your store. You own your data not only in the sense that it's local, but you have ownership of how you interact with it. You can sync your stores between different machines using rsync or syncthing, or even backup the store to cloud storage. It's encrypted, and only you have the key. Provide on this episode. 672z2u