New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deniable encryption #2402

Open
andrewdavidwong opened this Issue Oct 27, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@andrewdavidwong
Member

andrewdavidwong commented Oct 27, 2016

On 2016-10-26 16:19, tonyinfinity@tutanota.com wrote:

Usecase: If you are unexpectedly legally or extra-legally coerced to decrypt your laptop.

In order of most desired to least:

  1. Deniable FDE
    e.g. TrueCrypt/VeraCrypt-style hidden OS. I'm also not sure if these deniable encryption tools currently work with Qubes as is?

  2. Deniable encrypted partitions

  3. Deniable encrypted VMs

@quber

This comment has been minimized.

Show comment
Hide comment
@quber

quber Oct 31, 2016

Deniable encryption come with social danger and must not be include before serious thinking and discuss and community approve first.

In mailing list::

I will cough up my passphrase at the mere suggestion of torture. I would probably give up my passphrase if a scary person were to just ask nicely for it.

If Qubes were to incorporate any deniability features, I (and anybody who dislikes being tortured) would require a means to show absolutely that such features were not enabled. These are dangerous features because the moment they are incorporated we would all be using them, whether we are or not.

https://defuse.ca/truecrypt-plausible-deniability-useless-by-game-theory.htm

Read link before even thinking to work on this.

quber commented Oct 31, 2016

Deniable encryption come with social danger and must not be include before serious thinking and discuss and community approve first.

In mailing list::

I will cough up my passphrase at the mere suggestion of torture. I would probably give up my passphrase if a scary person were to just ask nicely for it.

If Qubes were to incorporate any deniability features, I (and anybody who dislikes being tortured) would require a means to show absolutely that such features were not enabled. These are dangerous features because the moment they are incorporated we would all be using them, whether we are or not.

https://defuse.ca/truecrypt-plausible-deniability-useless-by-game-theory.htm

Read link before even thinking to work on this.

@GustavMarwin

This comment has been minimized.

Show comment
Hide comment
@GustavMarwin

GustavMarwin May 24, 2018

As far as I'm concerned, I'll take my chances and vote for having plausible deniability on Qubes-OS.

To reply to quber: Say I simply work on something sensitive / valuable (knowledge) and I'm not under suspicion of anything. A way to login to Qubes-OS without having the "attacker" know about my "normal" work session would be very useful, no negative side effect.

Also maybe a better example, look at the trend at the border control where they ask to see "inside" every electronic you have. In that case again, should someone be asked to open their laptop there's nothing to lose at having a way to login to an "under duress session".

As far as I'm concerned, I'll take my chances and vote for having plausible deniability on Qubes-OS.

To reply to quber: Say I simply work on something sensitive / valuable (knowledge) and I'm not under suspicion of anything. A way to login to Qubes-OS without having the "attacker" know about my "normal" work session would be very useful, no negative side effect.

Also maybe a better example, look at the trend at the border control where they ask to see "inside" every electronic you have. In that case again, should someone be asked to open their laptop there's nothing to lose at having a way to login to an "under duress session".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment