, 2002-08-26
U.S. courts should join Russia in saying "nyet" to the FBI's lawless international hack attacks.
Expand all |
Post comment
When Feds are the Crackers
2002-08-26
Anonymous (17 replies)
Anonymous (17 replies)
When Feds are the Crackers
2002-08-26
Anonymous (2 replies)
Anonymous (2 replies)
When Feds are the Crackers
2002-08-27
Mark D. Rasch (1 replies)
Mark D. Rasch (1 replies)
When Feds are the Crackers
2002-08-27
Anonymous (2 replies)
Anonymous (2 replies)
When Feds are the Crackers
2002-08-27
Anonymous (1 replies)
Anonymous (1 replies)
yes mr. bush, we non americans are all wiked villans, kill us all!
2002-08-28
pedro barreto (3 replies)
pedro barreto (3 replies)
When Feds are the Crackers
2002-08-27
Anonymous (1 replies)
Anonymous (1 replies)
When Feds are the Crackers
2002-08-27
Yeah right (1 replies)
Yeah right (1 replies)

2. Everybody has the right to basic privacy (UN). Whether those rights apply to a particular activity depends upon the law in that country and the activity itself - see point 1. As for your employment rhetoric; remind me never to apply for a position in your company.
Back to the topic at hand; while I do not condone the activity of the Russian hackers, the FBI agents broke Russian law by hacking into the computers in Russia. The FBI agents even broke common US law by doing so, however under US law they are protected by their employment status (but this does not hold true in Russia). Therefore I believe that the Russian government would be quite within it's rights (possibly even it's duty) to attempt to extradite the FBI agents responsible and prosecute them under Russian law. You cannot have one side of a coin without the other.
This gets back to the basic arguments about where a cyber-crime is actually committed; in the country where the computer/data is located or in the country where the perpetrator is located? What happens if either or both are in international territory? What happens if the injured party is not happy with the law under which the "offence" is committed?
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/105/16260#16260