[lotuseclat79]

Details on presidential motorcades, safe house for First Family, leak via P2P (2 web pages).

Lawmakers eye bill to ban P2P use on government, contractor networks

The problem is well understood, but it remains difficult to stop. The leaks typically occur when a user installs a P2P client such as Kazaa, LimeWire, BearShare, Morpheus or FastTrack on a computer for the purposes of sharing music and other files with others on the network. In many cases, users inadvertently expose not just the files they want to share, but also every other file on their computers.

If the POTUS/Secret Service can be compromised as indicated in this article - how safe does that make you feel using P2P - just say no regarding your home computer(s).

Note: A legitimate use of P2P is when a company with 1,000s of internall computers need a patch distributed - i.e. it takes less time. But, that is a well-contained use of the P2P technology within a legal framework.

The lesson to be learned here is - don't expose you and your information on your home computer by using P2P networks for any reason you might think it is justified - it simply is not worth the risk! It may also open you up to legal exposure if you engage in pirating, etc.

-- Tom

[RootbeaR]

"In order for a LimeWire user to change their default settings to enable document sharing, they have to click nine times and disregard three warnings," Gorton said
http://tech.yahoo.com/news/nm/200907..._filesharing_4

[perfume]

Dear Tom,
This is peach of a post! Human tendency is to latch on to anything that comes free( which otherwise is a purse burner). Risk-taking ,seems to be the second common tendency! I know of students, who use Xerox machines to copy (very expensive)entire text books in the library, by tipping the technician operating the machine. In my view that too is piracy! Ultimately, it is "why buy"?

regards,
perfume

[RootbeaR]

"This started a few years ago, when suddenly grandstanding Congress-folk started blaming Limewire for "leaking" a confidential terrorist threat assessment. Of course, that was misguided. The problem wasn't Limewire (or any file sharing software), but idiotic gov't employees who (a) put file sharing software on gov't computers (b) didn't properly wall off the software and (c) put confidential info where it could be shared. Earlier this year, suddenly, the issue came up again (again targeting Limewire). It was instigated by some aggressive entertainment industry lobbyists, who have concocted this huge story about how Limewire is to blame."
http://techdirt.com/articles/20090729/1959315704.shtml