Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have a server application that we want to restrict non-users from triggerring it off from other machines or even by double-clicking from any share.
However, it should be easy for dev’s to run it on their boxes.
What are the various ways to enforce this policy?
One idea: One could use a registry key that needs to be present in order to run.
Another: One could require an X509 certificate be installed in the keystore to run
Another: Use System.Security.Permissions and restrict operation to a set of users or a group.
etc.