github.com/StackExchange/blackbox/v2@v2.0.1-0.20220331193400-d84e904973ab/docs/advanced.md (about)

     1  Advanced Techniques
     2  ===================
     3  
     4  
     5  # Using Blackbox without a repo
     6  
     7  If the files are copied out of a repo they can still be decrypted and
     8  edited. Obviously edits, changes to keys, and such will be lost if
     9  they are made outside the repo. Also note that commands are most
    10  likely to only work if run from the base directory (i.e. the parent to
    11  the .blackbox directory).
    12  
    13  Without a repo, all commands must be run from the same directory
    14  as the ".blackbox" directory.  It might work otherwise but no
    15  promises.
    16  
    17  
    18  # Mixing gpg 1.x/2.0 and 2.2
    19  
    20  WARNING: Each version of GnuPG uses a different, and incompatible,
    21  binary format to store the keychain.  When Blackbox was originally
    22  created, I didn't know this.  Things are mostly upwards compatible.
    23  That said, if you have some admins with GnuPG 1.x and others with GnuPG 2.2,
    24  you may corrupt the keychain.
    25  
    26  A future version will store the keychain in an GnuPG-approved
    27  version-neutral format.
    28  
    29  
    30  # Having gpg and gpg2 on the same machine
    31  
    32  NOTE: This is not implemented at this time. TODO(tlim) Use GPG to find
    33  the binary.
    34  
    35  In some situations, team members or automated roles need to install gpg
    36  2.x alongside the system gpg version 1.x to catch up with the team's gpg
    37  version. On Ubuntu 16, you can ```apt-get install gnupg2``` which
    38  installs the binary gpg2. If you want to use this gpg2 binary, run every
    39  blackbox command with GPG=gpg2.
    40  
    41  For example:
    42  
    43  ```
    44  GPG=gpg2 blackbox_postdeploy
    45  ```
    46