You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
closesbastibe#441
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.The text was updated successfully, but these errors were encountered: