|
|
Post by leet on Dec 26, 2019 15:01:51 GMT -8
Well, tried it and managed to create a Windows Logon Session (WLS) using RDP using a WinForms app. Everything seemingly worked but when I put the files in place RDP completely broke. I came to the realization that LogonUI actually is the thing that creates a new WLS. Since LogonUI.exe is just a black box, it's probably not possible to replace it.
|
|
|
|
Post by powerplayer on Dec 28, 2019 11:02:38 GMT -8
maybe u need to make a frontend for it and rename it to the dll that you remove , download processhacker to see the cmdbox instruction set
|
|
|
|
Post by ihatemetro on Sept 20, 2020 6:19:46 GMT -8
Well, tried it and managed to create a Windows Logon Session (WLS) using RDP using a WinForms app. Everything seemingly worked but when I put the files in place RDP completely broke. I came to the realization that LogonUI actually is the thing that creates a new WLS. Since LogonUI.exe is just a black box, it's probably not possible to replace it. Late but maybe go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ and change the UIHost key to your custom logonui, and maybe just call logonui only for the APIs required. Edit: Wait... It doesn't exist. Source for registry key here: www.askvg.com/how-to-install-and-apply-custom-3rd-party-login-screens-in-windows-without-replacing-default-logonui-exe-file/More information about login screen: Windows 2000 (msgina.dll) login screen is handled by winlogon.exe, not logonui.exe. Console Logon has ConsoleLogin.dll, see what's inside of it probably? |
|
|
|
Post by leet on Feb 22, 2021 17:32:05 GMT -8
A workaround just shot into my mind:
1. Create a user with no startup functions and the shell set to our custom program
2. Set that user to automatic login
3. Our custom program will display a custom themed logon screen to the user without anything else
4. Check if the entered password is correct
5. If it is, switch to that user using Windows API's
|
|
