\ No newline at end of file
diff --git a/taoensso.nippy.benchmarks.html b/taoensso.nippy.benchmarks.html
index d019cf9..103bf95 100644
--- a/taoensso.nippy.benchmarks.html
+++ b/taoensso.nippy.benchmarks.html
@@ -1,2 +1,2 @@
-taoensso.nippy.benchmarks documentation
\ No newline at end of file
diff --git a/taoensso.nippy.compression.html b/taoensso.nippy.compression.html
new file mode 100644
index 0000000..3a1dc97
--- /dev/null
+++ b/taoensso.nippy.compression.html
@@ -0,0 +1,5 @@
+
+taoensso.nippy.compression documentation
Positional factory function for class taoensso.nippy.compression.DefaultSnappyCompressor.
+
default-snappy-compressor
Default org.iq80.snappy.Snappy compressor.
+
\ No newline at end of file
diff --git a/taoensso.nippy.encryption.html b/taoensso.nippy.encryption.html
new file mode 100644
index 0000000..7872895
--- /dev/null
+++ b/taoensso.nippy.encryption.html
@@ -0,0 +1,40 @@
+
+taoensso.nippy.encryption documentation
Alpha - subject to change.
+Simple no-nonsense crypto with reasonable defaults. Because your Clojure data
+deserves some privacy.
->DefaultAES128Encryptor
(->DefaultAES128Encryptor key-cache)
Positional factory function for class taoensso.nippy.encryption.DefaultAES128Encryptor.
+
default-aes128-encryptor
Alpha - subject to change.
+Default 128bit AES encryptor with multi-round SHA-512 keygen.
+
+Password form [:salted "my-password"]
+---------------------------------------
+USE CASE: You want more than a small, finite number of passwords (e.g. each
+ item encrypted will use a unique user-provided password).
+
+IMPLEMENTATION: Uses a relatively cheap key hash, but automatically salts
+ every key.
+
+PROS: Each key is independent so would need to be attacked independently.
+CONS: Key caching impossible, so there's an inherent trade-off between
+ encryption/decryption speed and the difficulty of attacking any
+ particular key.
+
+Slower than `aes128-cached`, and easier to attack any particular key - but
+keys are independent.
+
+Password form [:cached "my-password"]
+---------------------------------------
+USE CASE: You want only a small, finite number of passwords (e.g. a limited
+ number of staff/admins, or you'll be using a single password to
+ encrypt many items).
+
+IMPLEMENTATION: Uses a _very_ expensive (but cached) key hash, and no salt.
+
+PROS: Great amortized encryption/decryption speed. Expensive key hash makes
+ attacking any particular key very difficult.
+CONS: Using a small number of keys for many encrypted items means that if any
+ key _is_ somehow compromised, _all_ items encrypted with that key are
+ compromised.
+
+Faster than `aes128-salted`, and harder to attack any particular key - but
+increased danger if a key is somehow compromised.
map->DefaultAES128Encryptor
(map->DefaultAES128Encryptor m__5665__auto__)
Factory function for class taoensso.nippy.encryption.DefaultAES128Encryptor, taking a map of keywords to field values.
+
\ No newline at end of file
diff --git a/taoensso.nippy.html b/taoensso.nippy.html
index 777f609..c6f252b 100644
--- a/taoensso.nippy.html
+++ b/taoensso.nippy.html
@@ -1,13 +1,13 @@
-taoensso.nippy documentation
Deserializes frozen bytes to their original Clojure data type. Enable
+`:legacy-mode?` to read bytes written by Nippy < 2.x.
+
+WARNING: Enabling `:read-eval?` can lead to security vulnerabilities unless
+you are sure you know what you're doing.
thaw-from-bytes
(thaw-from-bytes ba & {:keys [read-eval? compressed? password], :or {compressed? true}})
DEPRECATED: Use `thaw` instead.
\ No newline at end of file
diff --git a/taoensso.nippy.utils.html b/taoensso.nippy.utils.html
index 65af72a..39650df 100644
--- a/taoensso.nippy.utils.html
+++ b/taoensso.nippy.utils.html
@@ -1,8 +1,8 @@
-taoensso.nippy.utils documentation