drwho

for compliance we’d have to get everything re-vetted yearly

Huge pain in the ass to set up, but from the user's end of things it was pretty easy to do.

Some years ago, I had a client with a really fucked up set of requirements:

• Must run Gentoo Linux. (No, I don't know why. But it was written into the project specs and everybody who had to sign off did.)
• Must use LUKS for FDE.
• Login (loosely interpreted as "booting up") must have MFA.

This was during the days when booting into a LUKS encrypted Gentoo install involved copy-and-pasting a shell script out of the Gentoo wiki and adding it to the initrd. I want to say late 2006 or early 2007.

I remember creating a /boot partition, a tiny little LUKS partition (512 megs, at most) after it, and the rest of the drive was the LUKS encrypted root partition. The encrypted root partition had a randomly generated keyfile as its unlocker; it was symmetrically encrypted using gnupg and a passphrase before being stored in the tiny partition. The tiny partition had a passphrase to unlock it. gnupg was in the initrd. I think the workflow went something like this:

• System boots up.
• Script in the initrd prompted the user for the passphrase for the tiny LUKS partition. (first authentication step)
• User entered passphrase.
• Script in the initrd unlocked the tiny partition and prompted the user for the passphrase to decrypt the root partition's keyfile stored therein.
• User entered the symmetric passphrase for keyfile. (second authentication step_
• Script used the passphrase to decrypt the keyfile to stdout, piped into an evocation of cryptsetup to unlock the root partition.
• /dev/mapper/root mounted, /boot mounted, boot process continued.
• User logged into the box.

I don't miss those days.

Just like archeologists having to call dildos they find "religious objects," it all depends on how much you want to risk your reputation and research funding.

Syncthing could do it.

So, it'll cost them an hour's worth of revenue in fines.

It would probably be more reliable to partition and format the new drive manually and use rsync to copy everything over. Updating /etc/fstab with the new UUIDs isn't a big deal (though you can also manually specify the partition UUIDs at time of format - mkfs.btrfs --uuid ...) (you didn't say what file system your /boot partition was using, so I don't want to guess).

If you really want folks to have a go at it, add the phrase "military grade encryption" to the readme. That'll trigger a lot of folks' Google Alerts and you'll get the eyes on your code you're looking for.

It really depends on the company. When I was working for that company a few jobs back, we crunched the numbers and the cost of C&C and IV&V (Certification and Accreditation; Independent Verification and Validation) for an in-house TOTP had one more zero to the left of the decimal point than the Twilio bill (added up for the year). Plus, for compliance we'd have to get everything re-vetted yearly.

That's kinda of the definition of government contracting. :) I think the only US government org that has actual govvies doing anything other than management is NASA.

No, that makes perfect sense. Thank you for explaining.

I like hearing about other people's environments, because it gives perspective.

I was starting college (comp.sci, natch) and a hard req for the program was "Your own personal computer, with an Ethernet card and an OS that had a TCP/IP stack for remotely accessing classwork." I didn't have a great deal of money (most of it was tied up in tuition and housing) and ethernet cards were expensive (I think I paid $140us for it at the time). I couldn't afford Windows and didn't have a warez hookup for '95. A BBS I used to call had Slackware disk images for download.

The rest, as they say, is history.

Just out of curiosity, how often do you have to run pip install?