- 2 hours
Yeah, Copy Fail, Dirty Frag and Fragnesia are bad but holy fuck.
- 2 hours
more evidence that michaelslop binbows is trash
linux is better
luks wouldnt do this to u
Deebster@infosec.pubEnglish
5 hoursThis Chaotic Eclipse/Nightmare Eclipse is the same one whose opening post read:
I never wanted to reopen a blog and a new github account to drop code…
But someone violated our agreement and left me homeless with nothing. They knew this will happen and they still stabbed me in the back anyways, this is their decision not mine.
I’m guessing there’s plenty more to come.
Kinda funny that they’re targeting Microsoft and yet using GitHub to share the PoCs.
muusemuuse@sh.itjust.worksEnglish
3 hoursIt really isn’t. The encryption itself still hasn’t been defeated. The implementation is the problem. Microsoft just can’t get out of their own way. If they ignored all the business majors, nobody would be able to stop them.
- hperrin@lemmy.caEnglish8 hours
Of course they did. They have no interest in protecting your privacy and every interest in making you think they do. I would’ve been way more surprised to learn there wasn’t a backdoor.
- smeenz@lemmy.nzEnglish3 hours
I’m left puzzed as to how this works …like… the data on the disk should be encrypted sector by sector…it takes forever to encrypt or decrypt a disk which is consistent with that understanding.
When you boot into PE, I don’t understand how that OS can read anything off the disk, yellowkey or not, without knowing the encryption key…so how does it get that key. Is the vulnerability here that the key is stored in the TPM and win PE can be convinced to retrieve it without the proper credentials being provided ?
If that’s the case, and the TPM can just provide the key on request…then… where is the security here ?
- hperrin@lemmy.caEnglish2 hours
My guess is that the key to decrypt the disk is stored on the disk, encrypted by a Microsoft-known key. This seems to unlock that copy of the key rather than the copy encrypted by your own key.
Though he did say to put the disk back in the original system in part of the instructions, so it might be TPM based. The way to check would be to try this on a system with a disk from another system, or with a wiped TPM.
TPM is not security, it’s security theatre. If you don’t need to type a password in or insert a device with a key on it during boot, then it’s not secure, period.
- DeathsEmbrace@lemmy.worldEnglish11 hours
The entire Microsoft, Apple and Google ecosystem is USA backdoors. That’s why I call it American spyware.
- Dalraz@lemmy.caEnglish13 hours
Seems like every week there is another reason why I’m thankful I switched to Linux a few years ago.
tomiant@piefed.socialEnglish
11 hoursOnly thing I find annoying with full volume LUKS encryption is that it makes it difficult to resize partitions, it’s a whole thing, but it’s a minor hassle and not something I’d do every day anyway.
wonderingwanderer@sopuli.xyzEnglish
2 hoursWhy not just encrypt the whole drive and then use virtual partitions within the encryption?
- slowbyrne@lemmy.zipEnglish8 hours
I like to use btrfs subvolumes inside a luks lvm volume for this reason.
statelesz@slrpnk.netEnglish
7 hoursWhat? Btrfs subvolumes are basically the same as logical volumes. That’s somewhat redundant.
Miller@lemmy.worldEnglish
14 hoursYou mean that thing everyone knew about since the authorities derailed open-source TrueCrypt and forced them to message their users that they should migrate to BitLocker?
- 13 hours
There’s an open-source successor to TrueCrypt called VeraCrypt. For that matter, as far as I know, one can still download the last version of TrueCrypt. It hasn’t been disappeared.
It’s true that the TrueCrypt developers retired and said that commercial packages like BitLocker were finally good enough and available enough that they didn’t feel compelled to maintain TrueCrypt. I remember that. I think it’s plausible that Microsoft has (or has provided to someone) back-door access to BitLocker, but I don’t remember any hint that the TrueCrypt developers had been coerced; have you got something you can link to?
- Creat@discuss.tchncs.deEnglish8 hours
These days, if you’re not on Windows you can use luks or just zfs with encryption enabled. Code is open and can be audited by anyone. But yes, VeraCrypt to my knowledge is also still a viable option.
Miller@lemmy.worldEnglish
13 hoursCertainly at the time there was talk of coercion, there was talk the developers had been asked to put in a backdoor, had refused and then been encouraged to cease and desist their work on TrueCrypt and provide written recommendation of BitLocker, the wording of which did not seem to be their own. But people like conspiracies, maybe the authors did just move on, and if that was encouraged it probably was not as sinister as suggested. Security and privacy will always be duking it out.
tomiant@piefed.socialEnglish
11 hoursBut people like conspiracies,
In spite of the fact that they never happen and that government mass surveillance isn’t a thing and hasn’t been exposed repeatedly for decades and that we all know they have not been aiming to do this exact thing for the better part of a century and that they are genuinely evil and literally never prove themselves to be over and over and over.
- bitteroldcoot@piefed.socialEnglish13 hours
Good.
We always knew it was there. They sold their soul to the NSA decades ago.
tomiant@piefed.socialEnglish
12 hoursI remember the day I saw the “Intel! Inside” commercial and the logo, and I thought, I don’t fucking trust this company.
Yeah no shit Intel inside, you’ve got every fucking three letter agency inside.
I knew it was over the day they introduced UEFI and TPM.
wonderingwanderer@sopuli.xyzEnglish
2 hoursWait what’s wrong with UEFI? My computer uses it, although I have an AMD chipset if that makes a difference…
forestbeasts@pawb.socialEnglish
1 hourMostly the “secure boot” crap, which you can turn off (it’s more a “running your own software on the machine” risk than a privacy risk). UEFI in general isn’t too bad (way way WAY more complex than BIOS though) and managing EFI bootloaders is so much less hassle than with BIOS boot!
– Frost
wonderingwanderer@sopuli.xyzEnglish
10 minutesAll I know about secure boot is that if I make a custom ISO and try booting from it, I would need to create a signature first, register it in my UEFI, and use it to sign the ISO.
Seems like a pain in the ass, but then again if I want to play with a custom ISO I can do so in a VM, and that seems kind of worth it to prevent someone from booting whateverthefuck if they somehow gain physical access to my computer…
- Carmakazi@piefed.socialEnglish14 hours
Tech megacorps are the fifth estate of their home countries, trusting your data to Microsoft or Google is essentially the same as handing it directly to the FBI and CIA.
- 13 hours
LUKS, never had these problems…Too bad Win11 won’t boot from it.
- potustheplant@feddit.nlEnglish5 hours
No hay nada por lo que pedir perdon! Fue una correccion menor, se entiende lo que quisiste decir de todas formas :)
- hperrin@lemmy.caEnglish8 hours
For anything I want to actually keep private, I only trust the software that I wrote. But LUKS is good enough for most stuff.










