Blacksheep wrote: "Life is short. How about a truce?"
Peace. Thanks for all your helpful posts here.
Blacksheep wrote: "Life is short. How about a truce?"
Peace. Thanks for all your helpful posts here.
There have been many helpful posts on this forum, including yours. I know I have learned much by participating and am sure others have also.Originally posted by johnny
Blacksheep wrote: "Life is short. How about a truce?"
Peace. Thanks for all your helpful posts here.
The reason I think using a .edu, .gov or .mil proxy sometimes might be a good idea is this:
Prerequisite: One is not engaged in nefarious Internet activities.
Given: Proxy sysadmin can read cleartext traffic, i.e. yours.
Example: If a US netizen was surfing in Iran, Iraq, or other countries hostile to US through a US .mil proxy and query was made to .mil sysadmin for your IP, log files, etc., that could be identified as coming from hostile country, I doubt any info on you would be divulged.
Sysadmin competency: I think a competent sysadmin would be less likely to be "social engineered" (conned) into giving info to "unknown" sources.
.edu sysadmins?: MIT and others of similar caliber can handle their networks.
.gov?: I dunno about that one, maybe I'll avoid it.
Blacksheep