Skip to content

Releases: robinmoisson/staticrypt

2.3.0

21 Nov 21:49
Compare
Choose a tag to compare

Changelog

  • support passing the passphrase through environment variable STATICRYPT_PASSWORD, support .env files

2.2.0

20 Nov 18:28
Compare
Choose a tag to compare

Changelog

  • add the --share flag to get an URL containing the hashed password to auto-decrypt the file, as per #140
  • update default password template: show a spinner when checking if we need to decrypt through a saved remember-me value, to avoid flashing the green background (#142)
  • refactor the code to make it easier to contribute, thanks to @hurrymaplelad (PR #135, #137, #138 )
  • freshen up the README

Breaking changes

Custom password templates: Even though there was heavy refactoring, the injection of data shouldn't break existing custom password templates. The share functionality is new and will require you to update your custom template if you want to use it, of course.

2.1.1

23 Apr 18:09
Compare
Choose a tag to compare

Changelog

  • fix a bug where the .staticrypt.json file was created in the node_module/staticrypt/ folder instead of the directory calling the command when calling it through npx

2.1.0

23 Apr 10:32
Compare
Choose a tag to compare

Changelog

  • add config flag & file .staticrypt.json to automatically save the salt in between runs without needing the --salt flag (useful for not logging out users that checked remember me + making the remember me check work across multiple file, see discussion in #125)
  • hopefully automatically creating a file is not a breaking change. The config file saving can be disabled with --config false
  • better doc

Closes #125

2.0.3

28 Feb 11:38
Compare
Choose a tag to compare

Changelog

  • add the --salt option to generate & set a salt that can be shared while encrypting multiple files - this allows the "Remember me" feature to work across files and deployments (previously re-encrypting a file would log out the users)

Fixes #125

2.0.1

10 Feb 19:04
Compare
Choose a tag to compare

Breaking changes

  1. The password_template now requires a {salt} variable to be injected at encryption time, which will break old templates. If you are using a custom template, you should update it to get the new decryption logic.

  2. The default is now to include a "Remember me" checkbox on the password box. If you don't want this (see discussion in #124 and #120), you need to disable it explicitely on the CLI by including the --noremember flag.

Changelog

  • add "Remember me" button with option on the CLI, optional expiration, salted + hashed password stored in localStorage
  • add parameters in CLI and website to change all text on the default password template
  • update yargs
  • update README with contributing info

PR: #124