>>1006458
8chan: where someone not stupid enough to run software from shady sources on his PC, who prefers emulation for the security of its isolated environment, prompts an ignorant but confident fool to disinform people for 7 hours and 1000s of words that any random deciding he had nothing better to do on the weekend can hack him through a ROM.
There are no known exploits in updated versions of common emulators to execute code outside the emulated environment, which makes them secure.
>A random guy stumbling on something and reporting to the github is not at all proof of the ryujinx dev looking out
You don't understand how these programming projects are organized. "The Ryujinx dev" is incoherent.
The Ryujinx GitHub has 212 development contributors on GitHub. Ryujinx imports dependencies, each with developers, like OpenAL, SDL2, or libsoundio for sound, OpenTK or Silk.NET for graphics, LibHac for the file system, ldb_mitm for multiplayer, and ShellLink for Windows shortcut generation. The code of these developers also develops Ryujinx.
One of these dependencies, SixLabors ImageSharp, had an info disclosure vulnerability.
It wasn't "stumbled on by a random guy" but James Jackson-South, the creator and top expert on ImageSharp. "Random guys" can't find such bugs, they're incapable. The reason the coder of ImageSharp found the bug in ImageSharp is because he coded ImageSharp and knows how parts of ImageSharp relate to exploit them. The reason top experts in emulation like byuu, mudlord, and aglab2 find emulation bugs is the same.
I said devs find bugs as a byproduct of development when coding or investigating issue reports. You challenged I prove it. I did: James found it coding and TSRBerry found it investigating issue reports. You then moved goalposts to not admit you were wrong.
The vulnerability has an EPSS score of 0.043% for the probability of exploitation in the next 30 days. Ryujinx fixed it in 3.
>zzazzdz found three separate exploits
What exploits for what claim? There are no known exploits in updated versions of common emulators to execute code outside the emulated environment, which makes them secure.
>Compiling with Visual Studio Code brought up the warning along with a link to the advisory
Because VS:Code reports CVEs as a security system. This got it to TSRBerry who fixed it. VS:Code didn't find the CVE, VS:Code reported it. James Jackson-South (the creator and top expert on ImageSharp) found it. Not a "random guy."
>That's not who found the vuln in ryujinx
It is, the 27929 vuln in Ryujinx was in the ImageSharp library, found by James Jackson-South, creator and top expert on ImageSharp. "Found" isn't "reported."
Did journalists reporting historical inventions discover them all? That's your "logic."
>And you can't even count on top of that.
I said it was found and fixed in 3 days, the 5th to the 8th. It was found by James on the 5th and TSRBerry's pull request was merged by gdkchan into Ryujinx:master on the 8th.
8-5=3. You actually can't count. I'm talking to someone who can't count. It explains a lot.
>That is wrong.
You are wrong saying aglab's N64 knowledge didn't help him exploit Project 64. I taught you aglab2 specializes in the MIPS R4300i microprocessor, and the function being exploited in RecompilerOps.cpp, which handles N64 recompilation, is Compile_R4300i_SB. His N64 specialization and his knowledge in host architecture both helped him exploit the PC program. Nothing's wrong there.
>besides you ruin your own claim by pretending it would affect millions
I said a malicious XCI or NSP for a new and popular Switch release that executes a Monero miner could. Point 62 in Nintendo's Yuzu lawsuit says "Between May 1 and May 10, Zelda: TotK was successfully downloaded over one million times." Before it came out. In a week and a half.
>Not necessarily
The creator of ImageSharp found the bug in ImageSharp because he coded ImageSharp and knows how parts of ImageSharp relate to exploit them. GitHub advertises 162 contributors to ImageSharp. The 161 devs with lesser knowledge didn't find the bug. The creator did.
>you're projecting your lack of knowledge
Funny from an ESL wrong on everything who argues only to argue. Most of my responses use knowledge you don't have to refute you.
You failed to even subtract 5 from 8.
>Look for any ad ridden emulator on the play store inb4 not malware somehow
You couldn't prove your claim and moved goalposts.
Monetized emulators aren't fake emulators and definitely aren't trojans.
>it means there's actually money to be made in doing so, so it's clearly more in the hundred of thousands range than hundreds.
You just made this up. Hundreds of thousands of what, Zimbabwean dollars?
You can make money from trojan emulators but you won't make that much. It takes minutes to trojan someone else's emulator so I challenge you, do it and make that. You won't.
>doesn't say how many of those were actually emu user, doesn't precise if it's many source or just one, this proves you're wrong instantly
Doesn't. Between May 1 and May 10, Zelda: TotK was successfully downloaded over one million times. Before it came out. In a week and a half. It's been out over a year. Doesn't matter how many are "emu user" or "many source," quoting your shitty ESL, when downloads to date are much higher. If easily infected it'd be infected and the Monero miner would make the infector a millionaire with really conservative infection numbers.