This project uses Break Versioning.
v1.2.0-RC1 (2026-11-21)This is a release candidate for v1.2, with security fixes, new key algorithms, and public-key encryption for keychains. It needs Java 17+.
Please test carefully with copies of your existing data before upgrading production systems, and report any unexpected issues. Thank you! 🙏
Most users on default settings need no changes. Data written with default settings is readable by v1.1 and vice versa, so rolling back won't strand data unless you use the new algorithms, :key-pub, or RSA keys with a non-default JCA provider (see below).
Action is needed only if you:
:pbkdf-nwf :ref-5000-msecs: a typo gave this only ~10 msecs of work. It now takes ~5 secs as intended (~500x slower), so check your latency budget and re-encrypt existing data.:backup-key in *config*: this let a wrong password pass keychain-decrypt. Backup keys must now be given per call to decrypt.Recommended when decrypting untrusted data: enable the new opt-in :require-hmac? and :pbkdf-nwf-max options (see *config* docstring).
signed: reject MD5 and SHA-1 [0437fc1]:ba-akm: require a byte array [fc15cf2]:pbkdf-nwf :ref-5000-msecs: fix wrong work factor [1013203]keypair-creator: isolate buffer from custom RNGs [f3c50ff]keychain-add-*: preserve added keys [fdd519d]decrypt-with-2-keypairs: fix key lookup [bc4fabc]keychain-decrypt: don't return nil for non-key errors [85f0237]:backup-key [0de3910]KeyChains: don't share byte[]s with callers [8343902]ChainKeys: don't share symmetric byte[]s [11a110e]:random as direct encryption key [97f3cc1]sign: support SHA-512 ECDSA envelopes [b6d9069]KeyChains: clear error for out-of-range priorities [7037dd4]:x25519 [7b29928]:x25519 [330d557]:ed25519 [147641f]keychain-encrypt: support public keys [405c999]:require-hmac? decryption option [7c6fff1]:pbkdf-nwf-max decryption option [0b55255]sign: add RSA-PSS signature algorithms [3f6669e]v1.1.0 (2025-12-10)This is a minor maintenance release that should be a safe upgrade for folks on v1.0.0.
It introduces new utils to make it easier to de/serialize public parts of KeyChains.
v1.0.0 (2025-11-05)At long last- this is the first stable v1 release of Tempel! 🎉
It is functionally identical to (and bidirectionally data compatible with) v1.0.0-RC1 (2024-02-26), but now marked as "production ready".
⚠️ Important: this software is provided "as is" and without warranty of any kind. You use it at your own risk!
While Tempel has been written and tested with care, the nature of the problem domain inevitably means that it can be easy to misuse and sensitive to bugs.
Misuse or bugs can be especially harmful - potentially leading to security vulnerabilities or even permanent data loss!
Whenever you use cryptographic libraries/frameworks (including Tempel), please test very carefully and always back up important data!
Please report any unexpected issues! Possible security issues may be responsibly reported here, thank you! 🙏
v1.0.0-RC1 (2024-02-26)v1.0.0-RC1 (2024-02-26)Dep/s: Tempel is on Clojars.
Versioning: Tempel uses Break Versioning.
⚠️ This release is intended for development/testing with ephemeral or low-value data. Tempel v1.0 final is expected around May 2024.
Please report any problems and let me know if anything is unclear, inconvenient, etc. Thank you! 🙏
v1.0.0-beta1encrypt-keychain, decrypt-keychain aliasesv1.0.0-beta1 (2024-02-01)📦 Available on Clojars, this project uses Break Versioning.
⚠️ Please don't use this in production yet, this release is intended for early testers and for those that would like to give feedback. Please report any unexpected problems and let me know if anything is unclear, inconvenient, etc. Now's the ideal time to get changes in. Thank you! 🙏
v1.0.0-alpha1v1.0.0-alpha1v1.0.0-alpha1 (2023-11-13)📦 Available on Clojars, this project uses Break Versioning.
This is Tempel's first public pre-release.
⚠️ Please don't use this in production yet, this release is intended for early testers and for those that would like to give feedback. Please report any unexpected problems and let me know if anything is unclear, inconvenient, etc. Now's the ideal time to get changes in. Thank you! 🙏
Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |