updated roadmap (encryption is no longer a target)

Touffy · Sep 27, 2023 · 97c7318 · 97c7318
1 parent 37932da
commit 97c7318
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -181,11 +181,11 @@ It is implemented in [client-zip 2](https://github.com/Touffy/client-zip/tree/ma
 
 ### compression
 
-Limited use case. If the user is going to extract the archive just after downloading anyway, it's a waste of CPU. Implementation should be relatively easy with the new CompressionStream API.
+Limited use case. If the user is going to extract the archive just after downloading anyway, it's a waste of CPU. Implementation should be relatively easy with the new CompressionStream API. Incompatible with content-length prediction.
 
 ### encryption
 
-AES and RSA encryption could be implemented quite easily with [WebCrypto](https://www.w3.org/TR/WebCryptoAPI/). I just don't see any use case for it (but if there is one, compression would be relevant for it too).
+AES and RSA encryption could have been implemented with [WebCrypto](https://www.w3.org/TR/WebCryptoAPI/). However, only the proprietary PKWARE utility supports strong encryption of file contents **and metadata**. Well-supported Zip encryption methods (even using AES) do not hide metadata, giving you questionable privacy. Therefore, **this feature is no longer planned for client-zip**.
 
 ### performance improvements