-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, There are a number of TC-forks around, not all of them are compatible to classical TC or to each other (eg VeraCrypt). In future the TC-forks will come up with new features in UI or on device-level. Some may introduce new container-formats etc. being non-interoperable with other TC-forks I would like to suggest to start to document the classical TC-formats (ciphers and container formats) as a starting point, so that projects can claim being compliant/compatible to. This spec should be driven format over time, in cooperation with other forks, so that the forks and their file-formats keep compatible to each other. If there is no such document/spec around yet as starting point, I would be willing to start such documentation effort, as I think that this is a very important thing to do. - -- At the time of writing, no warrants have ever been served to me, Frank Rehberger, nor am I under any personal legal compulsion concerning the CipherShed project. I do not know of any searches or seizures of my assets. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTqQvvAAoJEJHkRciZLMhMliEQAJk7OBQk7SJrehds35RziZ4g iVX0L9of62bC2W1Iy7Mrn0SoVBSgDGDAHsNLa+FcGChkS/vnIb6nmTjsIz97D3PY esJ8VrIozXZcvfMBfR51FXAk+91lTYfdKzqAUh+KIEUUIFd9+oun3BzvmXwlU7Uk Y3T65al/tM4QitWda8d5U8RC67x9/IorbpEYoynKw+v+jwFkqaiq8vR9fd62Fu15 pfoBRPI8BFwcnQH9sTCZ7qsaQ63HIMMzgWAe3pbkYi4GAbXlhgCGFz7QWGdvPBjY /97lUnSXT2LkGsxc9X4OSaEb9rx1wrfE9CguveQ4ZE56QRg/mgJtMSaO97FRt4iY rGqspu1o1tiWJP4RN0nlvgNNio2F2Cjp0ru2Rv3MXoF/VgADCc/Ay4Htufg/CA3C lWM9INqJiDswQ70u7+nSmN8rcmA87Xlbd8Bjam2Cq89xxyNC8aYVE9vaRzZpW46h YwR5KwrB70LoxSxt+RyVhz83PpD65k+Wpqsh4KJKNqMPR7DLZ2kuG2M2WBORMsiM Ys0bpAm/k4hXp760lahXbWMQCv9TLIvACRb1tkZN5MoaSNbRbRbNP43kkblnhVL8 9aRFy2TJfi+DscR3nUqirtW2zp5LLjQ0fbJaX1Xz36YlGtljAE5rcK3dwwF68XYp 3Xih4T3Ddi/PGBGk9ENF =q3KC -----END PGP SIGNATURE-----