I think we need strong Deniable Encryption.
It is not the end of all problems, but it would help with situations where you are forced to provide a valdi decryption of your encrypted volumes.
All "current" projects considering deniable encryption appear to be outdated and unmaintained. They struggle to even survive.
We should make it easier for competent and motivated people to contribute or create new Deniable Encryption projects.
For that, I suggest we create a collection of all publicly available academic research, documentation, experience and even FOSS codebases of real-life implementations.
This could look like a "Deniable Encryption" version of: http://freehaven.net/anonbib/ (but we should probably not restrict ourselves to academic research but also documentation and anything useful.)
The idea is, if we ever start a project, contribute to a project, or add features to a project with Deniable Decryption in mind, it should be easy to get up to date on what we know of that field, where does the current theory stand on what is possible and what is not, exampels of failed attemps and analysis of why they failed as wel las how to improve them.
I'm sure there is a lot of knowledge out there on the matter, and the first step to get anything done is to make it easy to KNOW what/how to do anything.
I think we need strong Deniable Encryption.
It is not the end of all problems, but it would help with situations where you are forced to provide a valdi decryption of your encrypted volumes.
All "current" projects considering deniable encryption appear to be outdated and unmaintained. They struggle to even survive.
We should make it easier for competent and motivated people to contribute or create new Deniable Encryption projects.
For that, I suggest we create a collection of all publicly available academic research, documentation, experience and even FOSS codebases of real-life implementations.
This could look like a "Deniable Encryption" version of: http://freehaven.net/anonbib/ (but we should probably not restrict ourselves to academic research but also documentation and anything useful.)
The idea is, if we ever start a project, contribute to a project, or add features to a project with Deniable Decryption in mind, it should be easy to get up to date on what we know of that field, where does the current theory stand on what is possible and what is not, exampels of failed attemps and analysis of why they failed as wel las how to improve them.
I'm sure there is a lot of knowledge out there on the matter, and the first step to get anything done is to make it easy to KNOW what/how to do anything.