Accessing \\.\PhysicalDrive0\ seems to require elevation still
-
-
No elevation required - can reproduce on Win10 Workstation Pro 2004 as a normal user, with AV protection and other mitigations in place. This is a permissions change that was introduced at some point by an update.
1 reply 0 retweets 0 likes -
Background: unelevated. Foregound: elevated. 20H2 572pic.twitter.com/Gr3FQMfoe6
1 reply 0 retweets 0 likes -
-
Well... for starters your anime/manga/hentai wallpaper. In addition it sure looks like a bitlocker icon on your drive.....
1 reply 0 retweets 0 likes -
Wallpaper was to grab attention!
And yes indeed, I use a TPM-backed BitLocker1 reply 0 retweets 0 likes -
yarh- bit locker stop em bits. i named the cve Bits please- not Bits get here or ill crack open the lock with brute force.
1 reply 0 retweets 1 like -
BitLocker ensures the „safe” permissions on the device objects or it is a side effect?
1 reply 0 retweets 0 likes -
side effect- you can still read the encrypted bits. hmm I just had an idea.... permissions reflects to the shadow drive.... try this: mklink /J shadow \\.\globalroot\device\HarddiskVolumeShadowCopy1
1 reply 0 retweets 1 like -
mklink operates on local volumes only :) Global namespace is not supported, so it refuses to cooperate
2 replies 0 retweets 0 likes
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.