On Tue, Feb 03, 2009 at 03:51:14PM -0200, Mark Boon wrote: > On Feb 3, 2009, at 2:34 PM, Heikki Levanto wrote: > > >All in all, I think this is a messy and unreliable solution to a > >problem I > >have not seen happening. > > > >For what it is worth I vote against client-side time controls.
> Maybe you haven't seen it. That doesn't mean it doesn't exist. True enough. > I always thought that security-certificates, signed applications and > public-key encryption were well equipped to tackle a problem like > this. But I'm certainly no security expert. No amount on crypto-mumbo-jumbo will solve the problem that the server will have to trust the program, and its author. Signing can provide some little assurance that the program running today is the same as was running yesterday, but that's about all. As long as we can write our own programs, there is no way to stop us from cheating in them, intentionally or by accident. I still think the that such time controls would take too much work to implement, make it easier to cheat, and offer no reasonable solution to a problem that may not warrant it. But that is, of course, my opinion. -H -- Heikki Levanto "In Murphy We Turst" heikki (at) lsd (dot) dk _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
