Probably if you obscure the score internally as octal, you don't need
anything more (encryption, server-based score, etc.). If your game is
a gambling game and money is at stake, you would need to redesign it
with tighter security. If it's a "just for fun" game, simple
obsfucation of the score a
do i still need to use the method that you suggested
Integer.toOctalString() for setValue(), in the case, i already use
obscure for my score even though it is stored in int?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
Using HTTPS only helps to prevent the forged packet attack. It does
nothing to prevent a user from using firebug to change values on the
client.
With respect to Google and gmail or adsense, they are probably not in
the same position as you. You are relying entirely on the client to
report a val
1.u mentioned about https. even if using https, the javascript is
still visible to user. therefore using firebug..etc still possible to
change the value right?
2. what is the extra measurement taken by google for app like gmail
and adsense written in gwt?
--~--~-~--~~~
The answer is, of course. The code is on the client, and even though
obscured, is JavaScript. Using something like firebug or even editing
the JavaScript in the browser cache the logic of the client can be
altered. Like any effort/reward system, it's a question of how much
it is worth to the us
Just curious on this, since gwt is javascrpt and i wonder possible to
somehow when calling rpc method, inject invalid value into it? for
example, gwt game that have setScore(..) method. can elaborate on
this?
--~--~-~--~~~---~--~~
You received this message because
