How to: Set Up "No Authentication" Mode
This topic applies to:
Visual Studio |
Visual Basic |
C# |
C++ |
J# |
Web Dev |
Express |
No |
No |
No |
No |
No |
Standard |
No |
No |
No |
No |
No |
Pro/Team |
No |
No |
Native only |
No |
No |
No Authentication mode is faster than the default Windows Authentication mode, so you might want to use No Authentication mode if network speed is an issue. Be aware that No Authentication mode is much less secure, however.
.gif) Caution |
|---|
No Authentication mode is not secure. Enabling No Authentication mode debugging leaves your machine vulnerable to any user on the network. A hostile user can connect to your machine, launch applications on your machine, access data on your machine, and perform other mischievous or destructive actions using a debugger. Use this mode with extreme caution. The default Windows Authentication mode is slower but much more secure. Use Windows Authentication mode if at all possible. If you must use No Authentication mode, be aware of the security risks and disable No Authentication mode as soon as you are done debugging. |
To Set Up No Authentication mode
In the Remote Debugging Monitor, choose Options from the Tools menu.
In the Options dialog box, select the radio button labeled No Authentication (native only).
If you want to connect through a TCP/IP port number other than the default port, edit TCP/IP port number.
In No Authentication mode, the Remote Debugging Monitor protects you from accidentally connecting to another user's instance of the Remote Debugging Monitor. Enabling Allow any user to debug disables this user name check. This is not a security option.
CautionAllow any user to debug leaves your machine vulnerable to any user on the network. Any user can exploit this privilege to connect to your machine, launch applications on your machine, access data on your machine, and perform other mischievous or destructive actions using a debugger. Use this setting with extreme caution.
In No Authentication mode, the Remote Debugging Monitor times out and exits if no debugger connects to it within a specified number of seconds. To change this timeout period, edit the value in Maximum idle time (seconds).
CautionThe longer the timeout period, the greater the opportunity for a hostile user to connect to the Remote Debugging Monitor. To reduce exposure, do not use a timeout period longer than the minimum time you need for a debugging session.
See Also
Tasks
How to: Set Up Windows Authentication Mode
How to: Run the Remote Debugging Monitor