Xylight (Photon dev)cake to Programmer Humor@programming.devEnglish • 11 months agoNull terminatorbackend.xylight.devimagemessage-square67fedilinkarrow-up11.17Karrow-down116file-textcross-posted to: xkcd@lemmy.world
arrow-up11.15Karrow-down1imageNull terminatorbackend.xylight.devXylight (Photon dev)cake to Programmer Humor@programming.devEnglish • 11 months agomessage-square67fedilinkfile-textcross-posted to: xkcd@lemmy.world
minus-square@tool@lemmy.worldlinkfedilinkEnglish12•11 months agoOr just cleared the SAM password altogether. Windows is trivially easy to break into if you have physical access and the volume isn’t encrypted.
minus-square@Mikina@programming.devlinkfedilink6•edit-211 months agoMy go-to solution is to simply replace some kind of accessibility feature executable, such as onscreen keyboard, with cmd.exe. It runs under SYSTEM.
minus-square@100794@lemmy.dbzer0.comlinkfedilink1•11 months agoDoes SYSTEM have enough permission to write to the SAM file?
Or just cleared the SAM password altogether. Windows is trivially easy to break into if you have physical access and the volume isn’t encrypted.
My go-to solution is to simply replace some kind of accessibility feature executable, such as onscreen keyboard, with cmd.exe. It runs under SYSTEM.
Does SYSTEM have enough permission to write to the SAM file?