On Fri, Oct 5, 2012 at 3:16 PM, Lucas Palma <[email protected]> wrote: > It's not the connection speed that I said, but the rate that the user sends > information. > And, as you said and I had already stated, it was an idea but not used, > because it can be forged. >
I don't see how, from an enforcability perspective these are any different (there's an iff), but okay.., > I was thinking if there's a server-side strategy, because almost everything > that come from the client-side can be forged, but if anybody knows something > that can't be forged and identifies the user as mobile device user, please > tell me. > What you want is some sort of certificate from sets of devices that can be signed by a device but not by a machine. However I'm unaware of any such capability (I highly doubt there is one, without assuming you have additional infrastructure in place, do you?). kris -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-security-discuss?hl=en.
