

Because you did it the wrong way round! DISM first, to have a good image to compare against THEN run sfc to compare your system to that image
Former Reddfugee, found a new home on feddit.de. Server errors made me switch to discuss.tchncs.de. Now finally @ home on feddit.org.
Likes music, tech, programming, board games and video games. Oh… and coffee, lots of coffee!
I � Unicode!


Because you did it the wrong way round! DISM first, to have a good image to compare against THEN run sfc to compare your system to that image
It’s a self cleaning dryer - the means everyone cleans it by themselves… wait…
That’s not the Chinese models we were talking about…
Hey, handsome! Wanna go for a few beers?


Yeah, but either Linux could do the same (maybe not as a default and with a scary warning in the config file if you turn it on) or it’s against the rules and MS should also play by the very same rules.
If someone has physical access to your devices you reach a game over state quite fast usually - so much more options to tamper things than with traditional malware. You can make things harder for them, sure. It’s always a trade off between comfort and security. A PC at home has another thread model than a notebook you carry around all the time and which might get lost/stolen/… easily (NOT saying encrypting your disks is useless!)
Are you sure that you cannot tamper with anything with a password in the UEFI bios? Does the UEFI encrypt and sign everything correctly or could you just exchange/ probe a flash chip on the mainboard and still get access? Or - in case of boot priority: How does your UEFI react if I disconnect all internal drives and only plug a bootable USB drive in? will it happily boot from the only possible (and new) option? Might it save that option for the next time? How does your password work, when I reset the UEFI with the little jumper/button? Etc.


As long it’s an intermediate platform that can milk the sellers and buyers with endless junk fees, count me in!


So as always - MS imposes the rules like Secure Boot and then gets to break them for convenience.
They already require a TPM. They already use it to manage keys. Why not set up a key for bitlocker for that one specific file?! Or at least sign the file header containing the checksum with a key from the TPM?


I do use secure boot, I do dual boot (rarely, but Windows is not yet deleted). My windows partition is not encrypted. Still Windows does allow hibernation. And reports a clean secure boot state afterwards.


Then there’s Secure Boot. With Secure Boot enabled, the Linux kernel runs in lockdown mode, and lockdown blocks hibernation because the saved image on disk isn’t signed and could be tampered with.
I wonder… how does Windows solve that problem?


✨oh yes, you’re absolutely right to point that out. It is a bad thing that we went bankrupt. I completely made up all business numbers and just guessed it from my dataset since you never gave me access to the real numbers. I should have pointed that missing access out earlier. If you want, we can setup a new company and I will amend the checklist to make sure I have access to its real financial situation.
1? No
2? No
3? No
95% of hackers quit before they crack a secret key!

I wonder how noticeable it would be to have two cheat modes


Not fair - I count 7 possible colours and 5 places to put them. That’s 16.807 combinations. That’s roughly 14 bits of information. That’s too hard! eMudhra only had 8 bits max!!!
makes you spit another tooth


Gnihihi - here they are in full glory:
The private key sizes of the compromised keys ranged from 3 to 8 bits. Astonishingly, the private keys were 4, 56, 66, 115, 155, 156, 230, 237.
I’m running Wayland on Fedora without problems. IIRC steam is still X and runs flawless since Fedora 43 (that’s when I switched to Fedora)