• 1 Post
  • 1K Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle








  • Honestly - lack of large trackpads aside (it does have a tiny one on the right side) - the Legion Go S looks like a good deal. Price should be equal to the OLED Deck for the 512 GB variant, for that you get a device with a more modern CPU architecture and 50% more GPU cores. The display is quite a bit larger (8.1" vs 7.4", which is a larger difference than it might seem), it’s higher resolution 120 Hz and - most importantly - it has VRR, which the Steam Deck OLED lacks. Sure, it’s not OLED and some people are seemingly allergic to higher resolution displays (“think about the battery life!!!” or “not powerful enough to play games at this res” (upscaling exists)), but 2D games like Hollow Knight or Cuphead should look amazing on this display and font rendering should be a lot better.

    Also, Lenovo might sell this in countries where the Steam Deck isn’t officially available.




  • It doesn’t already have to be running. BitLocker retrieves its keys from TPM by default, so just booting a device will place the keys in memory.

    To minimize downtime, abruptly restart the target system during the Windows boot process, specifically before the login screen appears, as this approach has proven effective in scenarios involving the retrieval of Full Volume Encryption Keys (FVEKs).

    By kernel-level debugging with WinDbg, the researcher observed BitLocker operations during the Windows boot process, which revealed that while Microsoft attempts to erase encryption keys using functions like SymCryptSessionDestroy, some keys persist on the heap, potentially due to incomplete key destruction mechanisms.


  • Is this really a BitLocker issue or more an issue inherent in the hardware design?

    EDIT: Okay, looks like Microsoft could do better:

    By kernel-level debugging with WinDbg, the researcher observed BitLocker operations during the Windows boot process, which revealed that while Microsoft attempts to erase encryption keys using functions like SymCryptSessionDestroy, some keys persist on the heap, potentially due to incomplete key destruction mechanisms.

    But maybe the hardware/UEFI should immediately wipe memory upon restarting anyway…?