Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for age encryption #441

Open
rosstimson opened this issue Aug 14, 2024 · 0 comments · May be fixed by #442
Open

Support for age encryption #441

rosstimson opened this issue Aug 14, 2024 · 0 comments · May be fixed by #442

Comments

@rosstimson
Copy link

It would be great to support age for encryption as well as the existing gpg support.

There is already age.el which might help.

It might be enough to even allow the setting of a custom file extension, if it is possible to say make the file extension .org.age and age.el is already installed I suspect it would transparently encrypte/decrypt.

fapdash added a commit to fapdash/org-journal that referenced this issue Aug 25, 2024
- require age.el if the package is installed
  https://github.com/anticomputer/age.el
- add new customizable variable `org-journal-encryption-extension` to
  control the file extension appended to the file name to trigger
  transparent encryption
- recognize `.age` files as journal files
- generate encrypted files based on chosen file extension instead of
  hard coding `.gpg`
- support `.age` files in `org-journal-re-encrypt-journals`
    - only re-encrypt files for the currently chosen encryption
      extension
    - functional change: don't edit/re-save files that aren't
      encrypted. I assume that they where handled by this function in
      the past was an oversight and not intended.
    - allow multiple recipients for `age` encryption

closes bastibe#441
@fapdash fapdash linked a pull request Aug 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant