How to: Set Up "No Authentication" Mode
This topic applies to:
Pro, Premium, and Ultimate
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.
No Authentication mode is not secure. If you enable No Authentication mode, debugging leaves your computer vulnerable to any user on the network. A hostile user can connect to your computer, launch applications on your computer, access data on your computer, and perform other mischievous or destructive actions by 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 you can. If you must use No Authentication mode, realize of the security risks and disable No Authentication mode as soon as you are finished debugging.
To set up No Authentication mode
In the Remote Debugging Monitor, choose Options on the Tools menu.
In the Options dialog box, select No Authentication (native only).
If you want to connect through a TCP/IP port number other than the default port, change the 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. If you enable Allow any user to debug you disable this user name check. This is not a security option.
Allow any user to debug leaves your computer vulnerable to any user on the network. Any user can exploit this privilege to connect to your computer, launch applications on your computer, access data on your computer, 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 time out period, change the value in Maximum idle time (seconds).
The longer the time out period, the greater the opportunity for a hostile user to connect to the Remote Debugging Monitor. To reduce exposure, do not use a time out period longer than the minimum time that you need for a debugging session.