manbytesgnu_site

Source files for manbytesgnu.org
git clone git://holbrook.no/manbytesgnu_site.git
Info | Log | Files | Refs

20220112_clortho.rst (1305B)


      1 Clortho
      2 #######
      3 
      4 :date: 2022-01-12 15:03
      5 :modified: 2022-01-12 15:03
      6 :category: Code
      7 :author: Louis Holbrook
      8 :tags: crypto,hash,sha512,bash,cli
      9 :slug: clortho
     10 :summary: A key value store at your fingertips
     11 :lang: en
     12 :status: draft
     13 
     14 
     15 Ever since I started using the pass_ CLI as my password manager, I've found myself putting all sorts of stuff in there; usernames, email, urls, crypto addresses, api keys, you name it.
     16 
     17 It makes total sense that some of these items are in there. For example, I store the url to a service together with the password, usually accompanied by the username and the email used [1]_. No password recoveries needed.
     18 
     19 However, I've also started putting in things like crypto addresses, or even token smart contract addresses in there, it seems less of a good fit. One thing is that it spams the password directory. But another more sinister issues is that it's pretty clear for anyone reading the directory what items you are storing data for.
     20 
     21 
     22 Hiding the key
     23 ==============
     24 
     25 So what if I want to store key/value pairs, and at the same time I want to hide what I am storing?
     26 
     27 ..
     28 
     29         .. [1] I use a different email for each service I sign up to, and for every other context I have to leave my email for something.
     30 
     31 ..
     32         
     33         .. _pass: https://www.passwordstore.org/