xiangxhuwang

Hi V3ct0r, I would like to suggest the creation of a subforum dedicated to Kop Security (hacking, cheating, exploiting). I come from the infosec community where we every day deal with CERTs, reports, advisories, write ups, etc, in this way we address security flaws (im sure you know about that). So I think if the Kop security is taken with this way, we could go a little further to servers with professional optics approach. Let me explain: The idea is very simple, create a restricted subforum as a pseudo CERT. I suggest several ways to get the privilege to join it: By be part of ''Community'' user group (conditions may apply). By be part of ''Server administrator'' user group (preferably if own a Stable server). By be an User but conditioned to send a Write up of new flaw, new approach to know flaws and/or PoCs. The ''Server administrator'' group members will be fundamental part of this subforum, they will be active participants in the search for solutions.The disclosure of the flaws to the public will be decided by consensus. The idea would be only disclose if there is an efficient Fix, then the flaw will be published with their respective patch. All the servers that really care about their security will have the opportunity to strengthen their security. Those who do not will be condemned to disappear. And btw this could contribute to fair competition. Regards.

Hi V3ct0r. If you run a diff between the files on ''娴风洍鐜婼server.rar'' and ''FILE.rar'' and the files on ''海盗汪.7z'' respectively, you will notice that they are the same files. Then I should think that source files of the 2.4 version was not public avaible on this forum?. Regards.

¿Where I can find that thread and how I can download these files? The thread can be found here. Although it is very easy to qualify for download, I leave attached the dot txt file published there. However, it should only be considered a mirror since the content of this Zip is the same as the files ''娴风洍鐜婼erver.rar'' and ''FILE.rar'' shared by @V3ct0r. And ofcourse, the Sha-2 sum: 5026c4da66e585c65ee19fbeb3db1721c979af88ac53df97ce9060a3075ee425;海盗汪.7z. Attachment: 海盗王.txt

Disclaimer I've made this post without any intention to discredit, discourage and / or detract from the great effort to obtain the Kop Source Code. The crowsourced way you financed the purchase and the great initiative to go public and really public without demanding anything in return (which show clearly the spirit of this community and its admins). Background A few days ago I heard that a member of this community had obtained the source code of Kop, I learned that the community made the effort to raise funds to honor the expenses of this user and he was encouraged to made it public, which was achieved successfully. However and despite the public availability of the code in this forum: I was nearly impossible to download it because of connectivity issues, achieving it only two days ago. After reviewing the container files, the first thing that caught my attention and caused me a bit of noise was that some files had recent modification date. As I like to work as clean as possible (anyone who has done some kind of forensics analysis ever could understand me) and of course as I am a friend of the checksums (I had downloaded it from the mirror in the OwnCloud of piratia.ru and did not know if contained any alteration regarding files published by @V3ct0r) so I decided to start searching for files without alterations looking for the source of this leak. What we know The existence of the source code of Kop became known thanks to the commercial promotion of such code by a user of Asian origin in a popular forum. This user, in their intention to build trust, performs demonstrations that suggest authentic possession of the source code. Using for this audiovisual on a trial basis. Leaks from the leaker Among the evidence provided by the seller, was a video in which a demonstration of compiling the source code is made: which means the strongest proof of possession of the source code, but at the same time the proof less relevant to my purpose, however, in the screenshot proof type you can see an archive manager showing enough information and this was all necessary info for my purpose: information that would be a checkmate to the intentions of doing business of the seller. A look at this matter If we try to dig a little in the screenshots of the archive manager and if we see in the left side panel we can find a little weird info at first, but very valuable if you see a little more on it. You can see a list disk units, the structure of the directory where the source code was decompressed and a number of directories which share the same root folder. Taking a deeper look Looking at the names of the directories, we can see that most contain Western names, and we can deduce that being a person who has a source code which tries to sell: possibly those directories containing source codes of games with such names. This indicates that it is not the primary source of the leak and possibly there is a common origin for all sources codes that possesses so many games with so many different styles. If we see a little more, we will detail that one of the directories have a domain name (www.eenot.com), after entering this website we find a community like a paradise where a lot of source codes are shared, as indicated by its page title: Aliens Source Forum: Open Source Forum, commercial source, game source code, website source code. Which confirm that the individual obtains the source codes of third parties, possibly similar to that online community. Now, with a little more light on the possible origin and their availability on the Internet, we need only extract some keywords of the screenshots by OCR and complement with keywords extracted from www.eenot.com page tittle. Let's start search on Baidu. Results We found an online community in which are published the source code, you can see that the thread was created on 04.12.2016: almost two months before the appearance of the seller at the popular forum, we can't rule out its previous existence in other source sharing communities.