Null terminatorXylight (Photon dev)@lemmy.xylight.dev to Programmer Humor@programming.dev – 1185 points – 12 months agoThis image is hosted on an Environmentally Friendly™ host.67Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentOr 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?
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?
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?
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?