transcrypt v2.0.0

*** WARNING: Re-encryption will be required when updating to version 2.0.0! ***

This is not a security issue, but the result of a bug fix to ensure that the salt generation is consistent across all operating systems. Once someone on your team updates to version 2.0.0, it will manifest as the encrypted files in your repository showing as changed. You should ensure that all users upgrade at the same time...since transcrypt itself is small, it may make sense to commit the script directly into your repo to maintain consistency moving forward.

Steps to Re-encrypt

After you've upgraded to v2.0.0...

1. Display the current config so you can reference the command to re-initialize things:

   $ transcrypt --display
   The current repository was configured using transcrypt version 1.1.0
   and has the following configuration:
   
     GIT_WORK_TREE:  /home/elasticdog/src/transcrypt
     GIT_DIR:        /home/elasticdog/src/transcrypt/.git
     GIT_ATTRIBUTES: /home/elasticdog/src/transcrypt/.gitattributes
   
     CIPHER:   aes-256-cbc
     PASSWORD: correct horse battery staple
   
   Copy and paste the following command to initialize a cloned repository:
   
     transcrypt -c aes-256-cbc -p 'correct horse battery staple'
   

2. Flush the credentials and re-configure the repo with the same settings as above:

   $ transcrypt --flush-credentials
   $ transcrypt -c aes-256-cbc -p 'correct horse battery staple'
   

3. Now that all of the appropriate files have been re-encrypted, add them and commit the changes:

   $ git add -- $(transcrypt --list)
   $ git commit --message="Re-encrypt files protected by transcrypt using new salt value"
   

Changelog

Fixed

• Force the use of macOS's system sed binary to prevent errors (#50)
• Fix cross-platform compatibility by making salt generation logic consistent (#57)

Changed

• Add an EditorConfig file to help with consistency in formatting (#51)
• Use unofficial Bash strict mode for safety (#53)
• Reformat files using the automated formatting tools Prettier and shfmt
• Ensure that transcrypt addresses all ShellCheck static analysis warnings