Privacytools.io: New section - Hard disk/Filesystem Encryption

[p43b1]

Privacytools.io could suggest using the Linux Unified Key Setup or LUKS to encrypt internal/external hard drives and usb thumb drives.

https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup

[ghost]

1. VeraCrypt

[loganmarchione]

I have the code for this, but didn't create a branch for https://github.com/privacytoolsIO/privacytools.io/pull/156 (I commited to master), so I can't create a PR until that PR is closed.

[Atavic]

1. Gostcrypt

[2E0PGS]

VeraCrypt I can vouch for.

Also you can use PGP to encrypt files:
Keybase.io also have a PGP encrypted file sharing service. Also they have PGP encrypted git repos.

Most Linux have disk encryption options. Also Android too. You have to decrypt the home folder on boot time.

[blacklight447-ptio]

Veracrypt and luks would seem like good options, I know also that veracrypt is audited.
@nitrohorse , would you have time to make a PR for this?

[nitrohorse]

I believe we already mention VeraCrypt and LUKS 👍🏼 https://www.privacytools.io/software/encryption-tools/#encrypt

[blacklight447-ptio]

So can this issue be closed?

[Mikaela]

https://www.privacytools.io/software/encryption-tools/ - I guess so.

[beerisgood]

Also Bitlocker for Windows

[blacklight447-ptio]

We already list veracrypt, no need to list Microsoft's closed source alternative.

[beerisgood]

@blacklight447-ptio well, Bitlocker works better with Windows 10 & uEfi then VeraCrypt.
Also it's native available - but only for Pro and higher version

[blacklight447-ptio]

I know, but we generally tend to follow the model: we don't require software to be opensource if there is no alternative, in this case there is: veracrypt, thus we require it to be open source. Bitlocker does not fall over it. plus the requirement to have an more expensive windows license for it makes me weary to recommend it.

[2E0PGS]

No mention of phone encryption still however. Suggest using Android's encryption.

⁣Cheers,

On 29 Aug 2019, 11:45, at 11:45, blacklight447 [e-mail] wrote:

I know, but we generally tend to follow the model: we don't require
software to be opensource if there is no alternative, in this case
there is: veracrypt, thus we require it to be open source. Bitlocker
does not fall over it. plus the requirement to have an more expensive
windows license for it makes me weary to recommend it.

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/privacytoolsIO/privacytools.io/issues/152#issuecomment-526131562

[blacklight447-ptio]

to my knowledge, all phones encrypt by default for a few years now, same story for IOS.

[2E0PGS]

Android isn't by default in my experience.

⁣--
Peter Stevenson (2E0PGS)
http://www.m3pgs.co.uk​

On 29 Aug 2019, 11:49, at 11:49, blacklight447 [e-mail] wrote:

to my knowledge, all phones encrypt by default for a few years now,
same story for IOS.

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/privacytoolsIO/privacytools.io/issues/152#issuecomment-526132599

[blacklight447-ptio]

google says its the default since android 5.0:https://source.android.com/security/encryption/full-disk

[dawidpotocki]

I know, but we generally tend to follow the model: we don't require software to be opensource if there is no alternative, in this case there is: veracrypt, thus we require it to be open source.

VeraCrypt is not free, it is a combination of source-available code and
code under Apache 2.0.

[blacklight447-ptio]

Well yes, but I meant open source, not fsf free

[dawidpotocki]

Well yes, but I meant open source, not fsf free

Still not open source and they pretty much mean the same thing.
https://web.archive.org/web/20131029185711/http://projects.opensource.org/pipermail/license-discuss/2013-October/001313.html

[blacklight447-ptio]

What part of veracrypt has no aviable source?

[dawidpotocki]

What part of veracrypt has no aviable source?

There is source, but you can't do "whatever you want", this part is
coming from TrueCrypt, which VeraCrypt forked.

https://lists.opensuse.org/opensuse-buildservice/2008-10/msg00055.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364034
https://lists.freedesktop.org/archives/distributions/2008-October/000276.html

[blacklight447-ptio]

i know, but its what i meant, its opens source, we can see how it runs and compile it yourself, you just cant do everything you want with it.