Thyth · Apotheosis Incarnate
- person Thyth
- perm_contact_calendar Member since
- today Last active (8 visits)
Comments
-
Yes, exactly.
-
Here's a more updated graph. I posted a description of the units on another site, and without them the X axis doesn't make much sense. X axis is milliseconds since the start of 1970 (the Unix Epoch). The major subdivisions on the X axis correspond to 13 hour, 53 minute, 20 second time intervals. I'll provide updated graphs…
-
Only one account can be generated per IP, per week. Sorry.
-
The system was developed on a system with a 2 Ghz Intel Core 2 Duo processor, and the estimated key times are based on systems with similar specifications. On this system I manage a 512-bit key generation in under 90 seconds. That 1 Ghz Athlon is pretty old school though. 11 minutes is pretty impressive.
-
The installer for the game that we link to was released by Sierra in 2004. For legal reasons, we haven't touched or made any modifications to that installer, so you get a virgin copy if you install from that. I don't know of any specific issues with that installer, but, I also don't have any Vista hardware.
-
Just so you guys know... the GameSpy Installer (the one we provide on the download page) installs a copy of the manual in PDF form in "Dynamix/Tribes2/Manual/Tribes 2 Manual.pdf".
-
Is this the GameSpy Installer?
-
You'll probably want setPerfCounterEnable(0); not setPerfCounterEnable(1);
-
That error message means an account was successfully generated from that address in the last 7 days. Sometimes the account download that occurs immediately after generation fails. If this happens, do an account retrieval.
-
This is slated for the delegated community management server, which will provide services such as Browser and T-Mail. That server will provide 24 hour time limited signed certificates that indicate current name, associated GUID, a list of clans, and active clan. There will be graceful fallback to bare account certificates…
-
That's a bug that we fixed on the 4th. Unfortunately, not all servers have applied it.
-
If you bring up the task manager, go to the process, right click on the Tribes2.exe process, and select "Set Affinity", you will have the option to constrain the process to one core/CPU. This should address those issues.
-
There is a lot of communication over anonymous pipes between the Tribes 2 process and the Ruby interpreter on startup. That's when the cryptography module is loaded. On most systems, this process takes under half a second, and doesn't contribute much to the load time.
-
I plan to post a full technical overview of the system soon, but to shortly answer your question: there is no real method of retrieving the password that you used to encrypt the private portion of the account, short of brute force. The contents of the store file are very high entropy, but are not entirely random. The…
-
There are occasional glitches in the RSA key generation. If that fails, then those fields are set to blank in the request to the auth server. Try closing your game, reopening, and recreating the account.
-
Can you tell us which operating system you are using? Additionally, do you happen to have any version of Microsoft Visual Studio installed? It sounds like you might have a crazy version of the Microsoft Visual C Runtime.
-
That's the same version we link to from the downloads page.
-
Select your account from the drop down menu. If the drop down menu says "Retrieve Account", then you are attempting to download your login credentials, rather than logging in.
-
As in a clean install of the game.. like from the tribes2_gsi.exe installer that we link to on the download page.
-
Ok... haven't seen any issues like that before. How long does key generation take for you (and the CPU in your computer would be useful to know as well). We've noticed some issues with the patcher failing to patch the actual game executable -- thus not actually initializing the Ruby interpreter. If key generation takes…
-
All of my testing accounts are working properly now. They exhibited the entire range of issues that were reported to me. I've sent patched files to Krash, and as of 1:15 PM Pacific Standard Time, these fixes are available in the version on the download page. Both servers AND clients must run this latest version, as I had…
-
I know what he meant, and I say again: DO NOT perform that operation.
-
Sierra/VU wouldn't release that account information, so we start from scratch.
-
Um... excuse me? Remove TCMS.vl2, but DO NOT, I repeat: DO NOT, unpatch your game.
-
Make sure you delete the Tribes2 directory between after uninstallations. Chances are the modified executable wasn't recognized by the Tribes 2 uninstaller. So... uninstall it... delete the directory... reinstall using the GSI version. Then apply the patch.
-
The public.store file contains every digitally signed account certificate that you have. One per line. When you "log into" an account, the account certificate from that file is what is sent to servers. The private.store file contains encrypted private exponents. When you "log into" an account, the private exponent that…
-
I wouldn't say that for certain. LouCypher suggested an approach which may be suitable. I don't know if Defense Turret does analysis of the in-memory image of the game, but if it only analyzes the on-disk copy, then LouCypher's idea would work. Defense Turret emulation on the client side, in the form of a script is a…
-
I think I've managed to trace the last remaining issue when performing authentication with servers. It seems to be caused by a limit in the game's networking protocol for transferring blocks of data over 255 characters in size. Certain keys generate (or are prone to generating) challenge exchanges that are larger than this…
-
I've been informed privately of one other issue that we're tracing now.
-
What are your system specifications (specifically CPU model and frequency)? What kind of key were you trying to generate? 512-bit? 768-bit? 1024-bit? RSA key generation takes a while.