As I said, you don’t have the mental capacity to process what’s wrong with your comment. Try to evolve a bit.

No, that’s people brainwashed by ideology “for ya”. You don’t seem to have the mental capacity to process that, so just try to talk to people you disagree with more, and widen your horizon.

As much as I despise Putin’s regime - this is not a practical solution. Also, there’s the issue with that Russian vassal state in NATO having the largest military in the world…

Do it, pussies!

“Country”

No shit Sherlock. “developers” who vibe code were never developers to begin with.

Codeberg would be sympathetic to the cause but does not have the €€ or legal power to deal with being bullied by microSLOP. :( Corporate law in Europe (and everywhere) is written to favour & protect big corps and corruption & bribery.

Same

Seems unlikely.

That’s what I’m saying. Not impossible though to hide key weakening info somewhere.

? They always were. Just less dumb morons.

That clarification of yours is massively important. Your initial comment sounds as if there is a PoC from Canada on how to circumvent the PIN for the Bitlocker keys.

Maybe that’s why you got downvoted?

I agree the “security researcher” sounds bitter, but also they found a proven critical backdoor, so it’d be negligent to just ignore their comment about circumventing the PIN. And the only way they could put microSLOP at fault for that would be if they could find that microSLOP was backing up encryption keys in the recovery environment / boot files somewhere.

I hope all people who have a problem with trans LGBTQ people die peacefully in their sleep. Tonight.

Thank you - it appears I stopped reading just one comment short of that, assuming that the “TPM+PIN is insecure” was a new comment, and not expecting it deeper down in the past.

Chaotic Eclipse posted the following with the disclosure of Yellowkey:

Second thing is, No, TPM+PIN does not help, the issue is still exploitable regardless, I asked myself this question, can it still work in a TPM+PIN environment ? Yes it does, I’m just not publishing the PoC, I think what’s out there is already bad enough.

Additional info:

The YellowKey is caused by the binary “autofstx.exe” which propagates all present volumes for transaction files, a researcher (unsure if they want to be named) told me that this binary is also present in windows update WinRE images and I think they will definitely have the same vulnerability as well. However, I’m unsure if it’s possible to trigger the controlled file deletion when windows is updating. If it’s true, then it means disabling WinRE is not a solution for the problem, which also means it’s a good thing that I kept the PIN+TPM PoC a secret.

Would you happen to have a source link for those claims? I’d like to forward them to a few organisations I work with, warning them that devices currently lost/stolen/left unsupervised despite having TPM+PIN configured will have to be considered compromised even if a future patch comes out.

Taste is almost identical, so I would assume “like KitKat” - however I have never spent a second thinking about chocolate quality in chocolate-biscuit-bars.

https://www.ulker.com.tr/en/brands/dido#product-popup-content-170

Get your fix there.

Fuck Nestle. Eat Dido from your local Turkish market if you are lucky enough to have one.

is this it? is the bubble finally about to burst? Don’t give me false hopes!

*millions

not the mosquito’s fault, is it?