Warning: Declaration of MyAuthPlugin::initUser(&$user) should be compatible with AuthPlugin::initUser(&$user, $autocreate = false) in /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php on line 37

Warning: session_name(): Cannot change session name when session is active in /home/tig/www/aalf/www/wiki/includes/Setup.php on line 222

Warning: session_set_cookie_params(): Cannot change session cookie parameters when session is active in /home/tig/www/aalf/www/wiki/includes/GlobalFunctions.php on line 2446

Warning: session_cache_limiter(): Cannot change cache limiter when session is active in /home/tig/www/aalf/www/wiki/includes/GlobalFunctions.php on line 2451

Warning: Parameter 1 to MediaWiki_TIGAutoAuthenticate() expected to be a reference, value given in /home/tig/www/aalf/www/wiki/includes/Hooks.php on line 117

Warning: Cannot modify header information - headers already sent by (output started at /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php:4) in /home/tig/www/aalf/www/wiki/includes/Feed.php on line 125

Warning: Cannot modify header information - headers already sent by (output started at /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php:4) in /home/tig/www/aalf/www/wiki/includes/WebResponse.php on line 10

Warning: Cannot modify header information - headers already sent by (output started at /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php:4) in /home/tig/www/aalf/www/wiki/includes/WebResponse.php on line 10

Warning: Cannot modify header information - headers already sent by (output started at /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php:4) in /home/tig/www/aalf/www/wiki/includes/WebResponse.php on line 10

Warning: Cannot modify header information - headers already sent by (output started at /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php:4) in /home/tig/www/aalf/www/wiki/includes/WebResponse.php on line 10

Warning: Cannot modify header information - headers already sent by (output started at /home/tig/www/aalf/www/wiki/extensions/DDNAuthPlugin.php:4) in /home/tig/www/aalf/www/wiki/includes/WebResponse.php on line 10
http://beta.aalf.org/wiki/index.php?title=CottenShubert459&action=history Revision history for this page on the wiki en MediaWiki 1.13.3 Sun, 01 Nov 2026 18:15:57 GMT http://beta.aalf.org/wiki/index.php?title=CottenShubert459&diff=59775&oldid=prev <p>New page: The most common method to hide your IP address is to use a proxy server in one form or another. A proxy server is a computer that offers a computer network service to allow clients to make...</p> <p><b>New page</b></p><div>The most common method to hide your IP address is to use a proxy server in one form or another. A proxy server is a computer that offers a computer network service to allow clients to make indirect network connections to other network services. A client connects to the proxy server and then requests a connection, file, or other resource available on a different server. The proxy provides the resource either by connecting to the specified server or by serving it from a cache. In some cases, the proxy may alter the client's request or the server's response for various purposes.<br /> <br /> There are several implementations of proxy servers that you can use to hide your IP address (in an attempt to remain anonymous on the internet).<br /> <br /> A Website based proxy server is a website that provides a form for you to enter the URL of a website that you wish to anonymously visit. When you submit the form the website proxy server makes a request for the page that you want to visit. The machine usually does not identify itself as a proxy server and does not pass along your IP address in the request for the page. The features of these sites vary (ad blocking, javascript blocking, etc) as does their price. Some are free and some charge.<br /> <br /> In using a proxy server (for example, anonymizing HTTP proxy), all data sent to the service being used (for example, HTTP server in a website) must pass through the proxy server before being sent to the service, mostly in unencrypted form. It is therefore possible, and has been demonstrated, for a malicious proxy server to record everything sent to the proxy: including unencrypted logins and passwords.<br /> <br /> By chaining proxies which do not reveal data about the original requester, it is possible to obfuscate activities from the eyes of the user's destination. However, more traces will be left on the intermediate hops, which could be used or offered up to trace the user's activities. If the policies and administrators of these other proxies are unknown, the user may fall victim to a false sense of security just because those details are out of sight and mind.<br /> <br /> If you're surfing very popular sites, like for example Yahoo!, then you must use a [http://www.proxysecurity.com/yahoo-proxies.php yahoo proxy] to not let any data slip from your computer to their server.<br /> <br /> The bottom line of this is to be wary when using proxy servers, and only use proxy servers of known integrity (e.g., the owner is known and trusted, has a clear privacy policy, etc.), and never use proxy servers of unknown integrity. If there is no choice but to use unknown proxy servers, do not pass any private information (unless it is properly encrypted) through the proxy.</div> Thu, 19 Apr 2012 18:39:01 GMT CottenShubert459 http://beta.aalf.org/wiki/index.php?title=Talk:CottenShubert459