Xylight (Photon dev)@lemmy.xylight.dev to Programmer Humor@programming.devEnglish · 1 year agoNull terminatorbackend.xylight.devimagemessage-square76fedilinkarrow-up11.2Karrow-down114file-textcross-posted to: [email protected]
arrow-up11.19Karrow-down1imageNull terminatorbackend.xylight.devXylight (Photon dev)@lemmy.xylight.dev to Programmer Humor@programming.devEnglish · 1 year agomessage-square76fedilinkfile-textcross-posted to: [email protected]
minus-squaretool@lemmy.worldlinkfedilinkEnglisharrow-up12·1 year 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-squareMikina@programming.devlinkfedilinkarrow-up6·edit-21 year 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-square100794@lemmy.dbzer0.comlinkfedilinkarrow-up1·1 year 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?