freak527

It is not the compiled version from the commercial source code that is already public. It is a edited loginapp from a indie version of the server and it does not reply in expected way so far?! The test with the compiled version throw out an encryption error it can't decode the attempt of the client. If i say i am working on it.

For now I never get a token. As I say many things to do.

It is running under CentOS 5.11 or so as described in the public available documents. But it is difficult to understand the way wargaming went with the Bigworld sources. And i am not sure if this helps for the progress, but you can maybe use it?

I will try to analyze with Wireshark. But I'm a real noob in this. I think there is too much work to do for me alone... So far it's only running in a kind of emulation. The client is awnser with please update your client.

Normally, I can't run the server with modified wot res folder?! Not so far. But is this the wrong method it must be token2 not basic i think.

This is an other test.

I will try to post more progress. At the moment it is difficult. Writing with my cell phone. Want to stay in touch. It's only for science issues no publishering planned. Thanks for your time. @Dragon armor This is a shot of the loginapp log with a previous test It's interrupting.

This is the hard way. Because the biggest problem at the moment is the nearly empty database. The missing scripts maybe recoverable.

Scripts config edited and my own generated rsa pair.

I don't know how I can capture it?! Sorry posts are automatically merged.

So far thanks for your help.

The loginapp is requiring a specific protocol version when i want to login with the wot client. For example the 0.9.22 will need protocol version 17... In my case Yes, but it is very interesting topic. And I will try it out again. Maybe there is a way. Sincerely freak

I have run tests with edited loginapp with public source code changed for working but it was not working correctly. Interrupt in blowfish. But now only dbmgr and loginapp don't work. Baseapp is needed. Yes attempt is working. Maybe it's too difficult that way?

Only the patch to override the server protocol version check.

For this version there is no source code available I think. I have patched the loginapp with IDA to work. The server is not shown in client because at this time the baseapp does not start because the missing scripts i talk about.

It is a working version of the Indie Suite. My patched loginapp is working with 0.8.9 and 0.9.22 so far. It is a big surprise for me. I stuck on database and python issues i described. Version number is 2.1 it was nearly working out of the box with client version 0.8.9. I want to share the experience with the community for help. You are so close. That inspired me. I try it about a half year. But here no successful login so far.

My last step was to patch the loginapp to work with my client version. But when I want to start the process there are some scripts needed. And I have big problems to understand the python scripts. No experience in python language programming. A second big question are the persistent data. At the moment there is a big database. But no idea to fill for testing. Sincerely freak

Yes it is a simplified version but, the procedure is still the same, i understand so far. Your project is awesome. Thank you for your fast reply. My problem is to add missing scripts to finalize the server start? I will send some screenshots to visualize the problem. Sincerely freak

Как продвигается проект? Сожалею. Google перевел Я тестирую решение с Bigworld Indie Server, но оно застряло в деталях при запуске клиента версии 0.8.9. У кого-нибудь есть опыт, которым можно поделиться?