Open arykov opened 3 years ago
It indeed is inability to pull credentials problem. Configuring service to "run as a user"...the right user solves the problem. Can be done manually as a workaround. Obviously password will have to change in the service every time it is changed for the user. Might be worth while to change install function to be updated accordingly
Here's a PowerShell script that will install gontlm
as a Windows service, running as the current user:
New-Service -Name "Go NTLM Proxy" -BinaryPathName 'C:\Program Files\gontlm-proxy.exe' -StartupType Automatic -Credential $(Get-Credential)
You'll then need to start the service:
Start-Service "Go NTLM Proxy"
The next time your start your computer, the gontlm service should automatically start 🙂
gontlm-proxy appears to have an ability to run as a service. Did give it a shot and don't seem to be able to use it this way(while starting it in a user's "session" works well). Didn't dig but is it related to the service unable to pull credentials when running as a service? And if it is the case does it even make sense to offer such an option?