You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running an exe the script compares the password wrongly.
I've tried writing my outlook password and PC numerical pin not non of these worked. Right after looking into %LOCALAPPDATA%\Microsoft\ there was no file like user.db. Is it a script bug or system stores the password not correctly?
The text was updated successfully, but these errors were encountered:
In case a PIN is configured you should have a password configured first. That is the password that is being requested at the fake logonscreen. Depending on whether the FakeLogonScreen.exe or FakeLogonScreenToFile.exe binary is used, the password is respectively printed to the console or written to a file. I haven't checked the source, but wrong attempts might also be written to that file.
I haven't tested what happens if a Microsoft account is used as opposed to a local or domain user account. I can imagine a Microsoft account underlying works with AzureAD and should then use the same Windows APIs to validate the password, but I haven't looked at that yet.
After running an exe the script compares the password wrongly.
I've tried writing my outlook password and PC numerical pin not non of these worked. Right after looking into
%LOCALAPPDATA%\Microsoft\
there was no file likeuser.db
. Is it a script bug or system stores the password not correctly?The text was updated successfully, but these errors were encountered: