GNOME Bugzilla – Bug 156178
GTetrinet's non-compliant with tetrinet.org's new scoring
Last modified: 2006-10-31 15:52:25 UTC
Please describe the problem: Tetrinet.org's recently adopted the Blocktrix as its official client and adopted stricter requirements for scoring. GTetrinet does not qualify for this scoring, and is pretty much useless on that server. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 32943 [details] [review] Provides minimal tetrinet.org scoring compliancy (and some other stuff)
Created attachment 32950 [details] [review] Support for tetrinet.org's new scoring requirements (and other stuff)
It's OK to apply for me, but I currently don't have an Internet connection and I can't commit it myself. Geez, this sucks. You say that this patch adds minimal support, where can we find a specification of this Blocktrix protocol? We surely want to fully support it! :D
I asked the author of Blocktrix, "Strikelight", if he was willing to share the specification of the protocol to let me implement it in Jetrix. In essence he refused to give the specification to an open source project in order to preserve the security of the protocol. Also the protocol is unstable and expected to change in the near future.
Thanks for your interest ! First of all, security through obscurity is just Wrong, blah blah blah Anyway, the Tetrinet game itself is and will be insecure, as long as the game engine runs in the clients, not in the server (that is, the logic that choose what is the next piece, what attacks are available to the player, etc). If the BlockTrix protocol involves having the game engine in the server, then GTetrinet will need a major rewriting in order to support it. If not, then you'll never have a secure game. In the end, it's up to the BlockTrix's author. We can help him to secure his protocol, if he gives it away. Actually, I think that releasing it to the public is the best way to secure it. And I'll be glad to add support for it in GTetrinet.
This was fixed in 0.7.8.