run as User without password
Closed this issue · 9 comments
Then checking checkbox to run service as specefic user, if selected user doesnt have password DaemonMaster doesnt proceed and insist user password to be inserter. This way program unable to create services for user accounts with blank passwords.
Due to security risks I doesn't implement such an feature for now.
Here is a link to such a topic:
https://stackoverflow.com/questions/1047854/cant-run-a-service-under-an-account-which-has-no-password
But I can allow to use empty passwords and than you must manually disable this security feature.
I read the article @the link. I am aware of this security policy and at work i am keeping my computers with group policy to allow use of blank password. Because i usually use RDP to connect to industrial PCs. But i think the issue does not apply here.
Correct me if im wrong . Regardless group polocy settings
1st.will Windows API permit service creation for specefic user with blank password? If yes then there must be no security hole issue as this is windows DNA.
2nd. If windows will refuse, then API function must return error and functionality will be reliant exclusivly on users decision to have GP Enabled or Not, its not DeamonMaster who overcomes security right?
Sorry for the late answer.
So what you want is, that I should not check that the password is empty so that windows can decide this?
Ok I will change it.
So I changed the code so that windows check the password/right to start without password.
(It will be in the next release version of DM. xD)
I checked the changes. while on local account it worked for me without password , with the accounts which do have password I have got an error message then I tried to run the service after creation.
so DaemonMaster on service creation page , create with account, of Course I typed in Username, and intentionally omitted the password. DeamonMaster created the service but It couldn't start it with message "service didn't start due to login failure".
so I fought of the scenario that a service can indeed be created without password if user doesn't have one, but password can be changed later, then the service will not be able to run . but lets face some facts, Windows services out there are running regardless of such password change events. so how shall it be?
one solution I do propose is to check the valid password then entering it and give a message that such password is wrong, or even for account without password gray-scale the password field and make it invalid.
So I don't understand all but you want that DM should check the password as before and gray-scale the password field when a user has selected an account that have no password. Right?
Edit: I don't have problems with users that have password. (same with users that have no password)