[Windows 7 x64] Xenosuite not reading Client?

[chopperzondeck]

Bug ReportOperating System:
Windows 7 x64 Short Description:
Xenosuite not reading Client? Behaviors: Inability to attach to client

Indepth Description:
When the xenosuite is open and tibia client is then opened. It seems to attempt to read the client but fails. I recieve this message everytime. "Unsigned Xenobot module found!
Xenobot will now restart and attempt to re-download the proper file.
If you keep seeing this error, please contact an Xenobot staff member."

I have tried a re-download of Tibia and Xenobot several times and still nothing. This has been happening for about a week now. Every since this latest update.

[maroxy]

Try deleting first the XenoBot folder at the Program Files and next re-install.

[chopperzondeck]

Still getting the error after deleting the Xenobot file from program files and re-downloading.

[DarkstaR]

Don't delete the file, delete the entire folder before reinstall.

EDIT:

If this doesn't work, there's only one conclusion: the security of your machine may compromised.

What? XenoBot uses something called code-signing (http://en.wikipedia.org/wiki/Code_signing) to verify the validity of all of it's files. Code signing is widely used, and uses strong cryptography to ensure that software is published by verified publishers. XenoBot verifies the signature of all of its various components to make sure they haven't been tampered with (cracked, infected with malware/keyloggers, etc). If the signature is bad, it will not load the file. There's two causes for a bad signature:

1. The content of a file not being what it should be
2. Having a compromised CA repository.

#1 can happen if XenoSuite bombs during an update (this is rare, but it can happen, hence the delete and re-install approach). It can also happen if the file gets infected in transit (unlikely) or gets modified on disk by some form of malware (polymorphic malware is rare).

#2 can happen if something has modified your root CA store to not include certain Certificate Authorities (http://en.wikipedia.org/wiki/Certificate_authority). XenoBot is signed by me, and my cert is trusted by a common root CA called DigitCert. They will be a root CA on your machine by default. If your machine doesn't trust my certificate, it's because that CA has been removed for some reason.


The reason you haven't got help on this issue is because nobody can help you. If deleting the files and re-installing does not work, the bug is a symptom of your system (whether it be a security breach, missing cert, or whathaveyou), and you need to figure it out for yourself. I wish I could give you a "fix right now" answer, but I can't. Unlike other bot developers, I take security very seriously, and there's no easy ways to circumvent mine; that's why its fundamentally secure.

[chopperzondeck]

I did a System restore on my computer to attempt to remove any corruption, but i still receive the error. Any ideas where i could look next? Sorry but im not amazing with computers and not sure where else to look for help.

[DarkstaR]

Find the latest XenoBot library (C:\Program Files\XenoBot\Versions\ and sort by date), then righclick->properties->digital signatures, and give me a screenshot.

[chopperzondeck]

So i have done a complete restore to default factory settings on my computer to erase everything and still receive the error from xeno. Unfortunately my drivers disk was scratched so im without drivers at the moment. But the versions file within that link u sent me reads xb.0010.14.7.6.643.dll name of signer: Xenobot email: N/a timestamp: Monday July 7th 2014. They all read similar just different dates with the time stamp. It wont allow me to send images right now do to graphics driver not working.

[chopperzondeck]

i just found the problem i believe. the last file in that link gave me this error, Digital Signature Details: The integrity of this certificate that signed this file cannot be guaranteed. The cert may have been corrupted or altered. Name: Xenobot Email:N/a Signing time: Tuesday May 12th 2015

[DarkstaR]

i just found the problem i believe. the last file in that link gave me this error, Digital Signature Details: The integrity of this certificate that signed this file cannot be guaranteed. The cert may have been corrupted or altered. Name: Xenobot Email:N/a Signing time: Tuesday May 12th 2015

That looks like the problem. The signature IS LEGIT on my end (and on the end of most users), so something on your machine is either corrupting it or failing to recognize the root CA. Can you get that file's MD5 for me so I can verify if it is corrupted or not? Use this tool: http://www.winmd5.com/

[chopperzondeck]

i got it solved. Thanks for the help though man.

[krystianq17]

I got same problem, can u tell me what to do now?

[lucasizq]

i have the same problem please help me+