What is your encryption workflow?

I encrypt files and folders with axcrypt, and I encrypt my drives with pic related. I also upload very sensitive files to NordLocker.

Attached: file.png (280x280, 17.17K)

Other urls found in this thread:

github.com/bailey27/cppcryptfs
twitter.com/SFWRedditGifs

>What is your encryption workflow?
>I also upload very sensitive files to NordLocker.
glownigger shines so bright.

Attached: 1636894258362.jpg (705x1200, 138.05K)

i'm not a glownigger you schizo fuck.

>internal drives all have LUKS fde
>external drives are unencrypted with symmetrical gpg on any semi private files

>I also upload very sensitive files
>very sensitive
for YOUR data, to become actually worth something, you better have broken the law hard/long enough to make it worthwhile investigating
paranoia stems from selfishness in the sense that one thinks everything is about them
even on the case you were saving stuff such as some wallet info, it's not like someone will target you or could by that matter, it's plain retarded

I use this github.com/bailey27/cppcryptfs
Because (a) its per-file encryption makes it easy to do sync things without worrying about shitty programs stupidly resyncing the entire encrypted file when a tiny portion changed and (b) it's the first thing I found that did what I wanted and I'm lazy so whatever, it works. Is it proper encryption or does it have an obvious exploit based on a fundamental misunderstanding on encryption principals as is so often the case in small one-off projects? Maybe.

>i'm not a glownigger you schizo fuck.

Attached: 1630931124037.jpg (747x615, 58.94K)

For me is LUSK and GPG,

LUKS*

Got something to hide?

What are you encrypting, user?

i film lots of porn with partners so that's what i keep encrypted. that and surveillance footage for my property.

What kind of porn?

Attached: 1495493303797-g.jpg (649x652, 47.94K)

scat

Its a Windows port of gocryptfs, and gocryptfs has had a formal security audit.

what's your thisvid username

>FDE on all disks on all devices
>root disk unlocks via yubi with challenge
>sub disks use keyfiles stored in root disk
>tomb used for extra sensitive files, only opened when absolutely needed

Veracrypt rapes SSD performance because it doesn't have proper driver integration.

The best thing to do is combine hardware + Software encryption. I use class 0 hardware encryption + Bitlocker (make sure to enable extended PIN). This way you basically have double protection + nobody can fuck with your bootloader thanks to class 0. Yea, there's a risk that hardware encryption gets broken but that's why you have another layer of software encryption. When setting up hardware encryption, make sure to set a master password or better, set security level to maximum via hdparm. If you have an nvme drive class 0 will be tricky and you'll need to have a motherboard that lets you set passwords on nvme drives. If you're on Linux or Windows

*I should add that any kind of software encryption will penalize SSD performance, even with AES-NI. Sequential speeds are usually unaffected but random writes can be lowered by up to 50% so bear that in mind. If you just want to protect your data from a nigger, class 0/TCG Opal is absolutely sufficient. Just make sure you use a modern Samsung drive because they have properly TCG Opal, at least as far as we know. If you're worries about law enforcement, use Software encryption, preferably dm-crypt as well. Bitlocker should be fine as long as you're not worried about the NSA.

>properly TCG Opal
*properly implemented

>verameme
you'd be better off mailing your files to your local police.