<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Well, there is one thing with these encrypting stuff, EA still remains
a Game publishing company, not a data security company. So I doubt they
will make things impossible to break, they might make it hard, but not
impossible.<br>
<br>
<div class="moz-signature"><big><font face="Verdana" size="-2"><big><!-- SGT -->Mortis<br>
European Tactical Battlefield Forces<!--<a href="http://www.theartofwarfare.net">The Art Of Warfare</a> - BF<br>
The Gryphons--></big></font></big></div>
<br>
<br>
Mikael Bååth schreef:
<blockquote cite="midd9d8f32e050713090613115f4d@mail.gmail.com"
type="cite">
<pre wrap="">Well, if I put up a server inside a to me unknown network, and that
network gives me a dns which points me to what I beleive is the
account server. How do I know it's not? And if it isn't, how can I
break EULA if I dont know? Am I responsible for all network traffic
the server spits out? Impossible, it wouldn't hold in court. Not in my
country anyhow.
The only real problem would be, if EA found out, they would scramble
the protocol that communicates with the account server in the next
patch. It may already be tightly encrypted, what do I know? The way it
looks now, nothing is really working on that level in BF2, so my guess
is it's quite simple to break.
</pre>
</blockquote>
</body>
</html>