RustBuster Report Bug's

[salva]

That's funny. Is It because of the code link obfuscation? If you decompile the code, you will find nothing, so It's a false positive.

This post should belong to another thread
http://fougerite.com/threads/original-vs-deobfuscated-ulink-dll.1069

 

[Jakkee]

@DreTaX you could try and upload your work to Virus Labs and if its approved it'll be pushed to anti virus companies or something like that.

 

[xandeturf]

fast fast fast @DreTaX , my players sending screnshot of others servers. fix bugs 1 and 15 the list.
D;

 

[DreTaX]

Hold on for 1.4.0.

I want to quickly add client side plugin support.

 

[salva]

Hold on for 1.4.0.

I want to quickly add client side plugin support.

Hi dretax, can you check out the list 1-13 of suggestions posted here?http://fougerite.com/threads/rustbuster-report-bugs.1208/

 

[salva]

I've tried version 1.4.0 for almost 1h, apparently everything works perfectly, just a tint, (NotifyMSG2 = Nothing happens when I change this in the settings) .....

 

[DreTaX]

I've tried version 1.4.0 for almost 1h, apparently everything works perfectly, just a tint, (NotifyMSG2 = Nothing happens when I change this in the settings) .....

Yeah I forgot about that, sry. I may push out a 1.4.1 today.

 

[xandeturf]

I'm still testing, but I received a TimeOut for the first time. Serverbrowser does not work, kick player with RustBuster

 

[DreTaX]

I'm still testing, but I received a TimeOut for the first time. Serverbrowser does not work, kick player with RustBuster

About the serverbrowser I know, but you are not helping with screenshots with logs.

Besides, I'm totally fine with the connection.

 

[xandeturf]

About the serverbrowser I know, but you are not helping with screenshots with logs.Besides, I'm totally fine with the connection.

sorry, Eu acabei esquecendo dois logs, eu sou WilyWork no servidor de log.

 

[DreTaX]

wot

 

[DreTaX]

2/6/2017 7:46:15 PM [Console] [RustBuster Login] WilyWork - 76561197963289497 - 28945ac5b8293605a6c78e097eea154b8305ed2f
2/6/2017 7:46:15 PM [Console] [RustBuster Login] Done!
2/6/2017 7:46:16 PM [Console] [RustBuster Version Check] 76561197963289497 1.4.0
2/6/2017 7:46:17 PM [Console] [RustBuster ImageQuality Check] 76561197963289497 28945ac5b8293605a6c78e097eea154b8305ed2f
2/6/2017 7:46:18 PM [Console] [RustBuster CheckingIfAdmin] 76561197963289497 28945ac5b8293605a6c78e097eea154b8305ed2f NO
2/6/2017 7:46:24 PM [Console] WilyWork NOT USING RUSTBUSTER (tinyurl.com/rustbuster2)2!

2/6/2017 7:17:55 PM [RustBuster] Download finished, loading plugins...
2/6/2017 7:19:03 PM [RustBuster] [color red] Retrying connection... (1x)
2/6/2017 7:41:33 PM [RustBuster] [color red] Retrying connection... (1x)
2/6/2017 7:41:34 PM [RustBuster] [color red] Retrying connection... (2x)
2/6/2017 7:41:35 PM [RustBuster] [color red] Connection timed out!

Mhm.

 

[DreTaX]

I checked It.

rustforlife.ddns.net

When RustBuster requests the player count, rustforlife wants to send 1164339528 amount of byte data, which is 1GB. No idea why, but I'm adding a check to see if the data is bigger than 20mb, and checking the server part now.

 

[DreTaX]

Sorta done with the requests. More to come.

@Jakkee you may see what you could do with the client side plugin sort of thing now.

 

[tarynkelley]

Literally unplayable because of that spelling bug.

 

[tarynkelley]

No idea why this happens. The logs are all normal.

Also since I use RustBuster my CPU load increased massively. Before it was 25%, now the rust server is using all 2 cores with only 3 active players and 20k objects. It needs even more resources than my Rust Experimental Server. The server performance is therefore very bad and the server is laggy.

What is causing this?

At the moment RustBuster makes the server unusable.

@DreTaX Does the Obfuscator need Intel VT-d?

 

[xandeturf]

'-'

 

[tarynkelley]

Found the reason I guess, it affects all servers and can be easily exploited. @DreTaX contact me asap on Skype.

 

[DreTaX]

Alright.

 

[DreTaX]

Problem solved. Any details about this exploit will go in the logs.