![]() ![]() This would mean that the more commonplace builds for Linux/Windows/Android would be immediately available, but all the specialized systems like consoles, old MSVC builds and whatnot would have to wait for later until we have adapted this properly to the new system. It might indeed be the case this is the catalyst for just starting all from scratch with a new server instead of trying to migrate the old one over. We had some long-term migration plans for a move to a new server, but this was always pushed back because we felt that we weren’t ready migration-wise. We’re still assessing the situation but moving forward, we think that it’s probably best not to go forward with the buildbot server that was compromised earlier today. The IP he was using while doing this was ‘54.167.104.253’, which seems to lead back to AWS. The same goes for ‘Update Assets’, ‘Update Overlays’, ‘Update Shaders’. For the current time being, the Core Installer is non-functional until further notice.Nothing has happened here and there is no need for any concern. The attacker simply wiped our buildbot server clean, there is nothing being distributed that could be considered malicious to your system. No cores or RetroArch installations should be considered compromised.We wanted to clear up some confusion that may have arisen in the wake of this news breaking: We hope they will be able to help us restore some of these vandalised Github repos to their proper state, and also to help us narrow down the attacker’s identity. We are still awaiting any sort of response or support from Github. RetroArch and everything preceding it on page 3 has been left intact before his access got curtailed. He managed to do damage to 3 out of 9 pages of repositories. He gained access to our Libretro organization on Github impersonating a very trusted member of the team and force-pushed a blank initial commit to a fair percentage of our repositories, effectively wiping them.The websites for these have also been rendered inaccessible for the moment He accessed our buildbot server and crippled the nightly/stable buildbot services, and the netplay lobby service.Here are the official press releases from the Libretro/RetroArch team:Īpproximately 5 hours ago, we were the target of a premeditated cybercrime attack on our key infrastructure. See the UPDATE 1 tab below for complete details. UPDATE 1 - The Libretro/RetroArch team have restored their buildbot server and github repositories. As of writing, the monthly goal has been well passed, and donations are currently at almost $2,000 a month. ![]() They have also asked for those wishing to help, to join their Patreon which was aiming to raise $1,300 a month to help with server and backup costs. While the Libretro/RetroArch determines their next steps, including possibly switching to a new server (which would slow down the process in releasing console specific builds), they may soon be asking for users to supply git repositories with the full history intact. The netplay lobby service is also currently not working. The nightly and stable buildbot services have also been crippled, and end-users are not longer able to update or downloads cores, assets, overlays and shaders. A sizeable amount of Libretro/RetroArch repositories have been wiped clean, and the development team is working hard to see if Github will be able to help them restore the lost data. While it seems the end-users are safe from the damage (no cores or installations should be considered dangerous), the same cannot be currently said about the work of the development team behind the great all-on-one emulator we have come to know and love. In sad news for the hombrew and emulators communities across multiple scenes and platforms, I regret to inform our readers that several days ago Libretro/ RetroArch was the victim of a targeted hacker attack. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |