Tremulous Forum
General => Troubleshooting => Topic started by: Janook on July 15, 2007, 07:54:06 am
-
Hi,
I recently reformatted my computer. I remembered to save my autogen and autoexec files, but I didn't remember to save my qkey file! And so, my GUID is gone.
This is a big nuisance for any servers I admin on, so I was wondering if someone could write a step-by-step tutorial on how to create/compile your own qkey file and how to set your GUID.
I'm on Windows XP.
-
nope
-
...excuse me?
-
"No"
Unless you know your exact GUID, you won't be able to.
-
Iam not quite sure how the file is created but the hostmaster of a server you were admin (Or anybody else who got access to admin.dat) can get your complete GUID. I got no idea howto use it but perhaps somebody else knows..
-
GUID is calculated from qkey file in your Tremulous user base directory. The only other way is to hack TJW's client executable to always send your old GUID.
-
GUID is calculated from qkey file in your Tremulous user base directory. The only other way is to hack TJW's client executable to always send your old GUID.
And from where is the qkey calculated? :-?
-
GUID is calculated from qkey file in your Tremulous user base directory. The only other way is to hack TJW's client executable to always send your old GUID.
And from where is the qkey calculated? :-?
if(cl_serverguiduniq) md5sum( <server ip>:<server port><contents of qkey> );
else
md5sum( <contents of qkey> )
recent versions of the client will refuse to use a qkey that isn't exactly 2kbytes in length.
-
GUID is calculated from qkey file in your Tremulous user base directory. The only other way is to hack TJW's client executable to always send your old GUID.
And from where is the qkey calculated? :-?
if(cl_serverguiduniq) md5sum( <server ip>:<server port><contents of qkey> );
else
md5sum( <contents of qkey> )
recent versions of the client will refuse to use a qkey that isn't exactly 2kbytes in length.
omg stop posting hax
-
GUID is calculated from qkey file in your Tremulous user base directory. The only other way is to hack TJW's client executable to always send your old GUID.
And from where is the qkey calculated? :-?
if(cl_serverguiduniq) md5sum( <server ip>:<server port><contents of qkey> );
else
md5sum( <contents of qkey> )
recent versions of the client will refuse to use a qkey that isn't exactly 2kbytes in length.
okay.. but.. i don't know how to do that.
Isn't there a way to compile your own qkey file?
-
okay.. but.. i don't know how to do that.
Isn't there a way to compile your own qkey file?
short answer: no
long answer: if you didn't have cl_serverguiduniq enabled it's possible but not practical to brute force a qkey with the same md5sum if you can find out what it was.
-
short answer: no
long answer: if you didn't have cl_serverguiduniq enabled it's possible but not practical to brute force a qkey with the same md5sum if you can find out what it was.
It would be possible to hack the client to always send the same guid, right?
-
short answer: no
long answer: if you didn't have cl_serverguiduniq enabled it's possible but not practical to brute force a qkey with the same md5sum if you can find out what it was.
It would be possible to hack the client to always send the same guid, right?
iirc starting with +set cl_guid blah works you just need to find blah
you also need to delete your qkey maybe
-
short answer: no
long answer: if you didn't have cl_serverguiduniq enabled it's possible but not practical to brute force a qkey with the same md5sum if you can find out what it was.
It would be possible to hack the client to always send the same guid, right?
iirc starting with +set cl_guid blah works you just need to find blah
you also need to delete your qkey maybe
deleting it just makes the client generate a new one, newer clients will ignore +set cl_guid ... on the comand line.