In reference to this thread, we can't allow links to webclients anymore.
The risks would be too large, as we can't really determine whether a Java applet is legit or not.
When you want to share a RSPS, you will have to add a regular as client as attachment.
As usual, you need to add two virusscans and if possible screenshots/videos.
Java DriveBy I'm guessing?
Originally Posted by Dejavu10
Java DriveBy I'm guessing?
Yes, if you would've clicked 'this' you wouldn't have asked that question
Not to scare anyone, but virus scanning jar or class files isn't going to yield any results. I could post a fake download link to fake RSPS that I make and have it download a rat and run it without a virus scanner ever picking it up.
Originally Posted by pjrat111
Not to scare anyone, but virus scanning jar or class files isn't going to yield any results. I could post a fake download link to fake RSPS that I make and have it download a rat and run it without a virus scanner ever picking it up.
There are some scanners intended specifically for Jar files. In fact, my anti-virus can even scan Jars
@whoszed Most can scan Jars. It's the ones that do it automatically and RELIABLY are the ones you need to have.
It's too bad that the RSPS community is a bunch of black hats, because those of us who prefer to play the unlegitimate servers legitimately always get a sore hand out of it all.
I like small communitys as it gives the players to bond more, however some larger communitys, (even the largest, soulsplit) have quite a large number of nice, bonded members.
I see the point of this thread and thank you @Ravallo .
Originally Posted by whoszed
There are some scanners intended specifically for Jar files. In fact, my anti-virus can even scan Jars
You say that, but there's no way of having it know what to look for if the file seems harmless. The scanner obviously can't read the code of the file, which means that it would have to closely watch the program to see if any unwanted things were done. It's easy to bypass this.
Originally Posted by pjrat111
You say that, but there's no way of having it know what to look for if the file seems harmless. The scanner obviously can't read the code of the file, which means that it would have to closely watch the program to see if any unwanted things were done. It's easy to bypass this.
Actually, the scanner can look at the code and search for malicious content, simple deobfuscation run on the jar (in case it's obfuscated ofc), and you can either use reflection or asm, even basic java api to get class names (See JarFile), reflection/asm to get content. :P