macOS_Wine_builds VS fusee-launcher

Hi, I followed this guide of u/Gcenx https://github.com/Gcenx/WineskinServer/issues/420 and applied on wine 8.10 staging (this version https://github.com/Gcenx/macOS_Wine_builds/releases/tag/8.10) but it seems like it doesn't work I always get a stub error. My question is: I need to do something else or D3DMetal simply doesn't work on newer wine version

The new Winehq macOS packages can be found https://github.com/Gcenx/macOS_Wine_builds/releases these will work on macOS High Sierra (10.13) and later.

Not sure where you got your wine binaries from, but wine-staging from this brew tap has the fix.

Gcenx maintains macOS builds of Wine that are as close to WineHQ releases as possible alongside other versions. https://github.com/Gcenx/macOS_Wine_builds They do work on Ventura although I believe 32-bit apps are still not working at the moment.

Depending on if you have an Intel Mac or an M1 Mac, you have some different options! If you have an M1 Mac, you could try using Wine/Wineskin Winery. You could also try something like UTM, but it's probably going to be very slow. If you find some of these games as old Mac games instead of old Windows games, you might also be able to get them running through SheepShaver or BasiliskII. If you're on an Intel Mac, your two best bets are VirtualBox or maybe, like, Windows 10 on Boot Camp.

u/gcenx maintains newer builds from macOS on GitHub. 64-bit Wine 7.x is also available from nixpkgs (32-bit support won’t be available until it’s possible to build WoW64 on Darwin).

There are builds of wine 7 you can get through brew, but I think it's maybe an uphill battle: https://github.com/Gcenx/macOS_Wine_builds

Actually the current macOS packages are not being pushed to Winehq directly due to an unresolved bug, they can be found https://github.com/Gcenx/macOS_Wine_builds

If you want wine-7.0 I’ve provided a package that will function https://github.com/Gcenx/macOS_Wine_builds/releases/download/7.0/wine-stable-legacy-7.0-osx64.tar.xz.

Awesome! I'd love to see a detailed writeup on how the exploit works, if someone has the time and interest to put one together.

We were incredibly lucky to get one for the Switch BootROM exploit: https://github.com/Qyriad/fusee-launcher/blob/master/report/...

This writeup of the bug avoids getting super-duper technical, but it is by necessity somewhat technical. The absolute simplest explanation goes something like this:

Yeah, all the console manufacturers have some pretty crap design choices one way or another, especially about security... and not saying that switch is entirely nvdia fault but, that SoC version was plagued with some issues that affected every device that used it

I unfortunately don't have an OMG cable, but don't they run Linux? You could try making a script to run this https://github.com/Qyriad/fusee-launcher

The original Switch uses a Tegra chip code-named "Erista," and it has a serious flaw -- the flaw we use to seize control of the bootloader. You can read a semi-technical overview of it here.

Jailbreaking a Switch relies on a badly-coded recovery mechanism that failed to restrict the size of a USB control request, allowing a stack-smash to take place which then executes attacker-controlled code at the highest privilege level, before privileges are reduced and control is transferred to the Switch's operating system. A more complete, technical treatment of the exploit can be found here.

Dang I’f you have a android phone or tablet that can launch cfw that would be worth a try and also found this https://github.com/Qyriad/fusee-launcher that seems it works for Mac.

u/GeenMachine already has a pretty great answer on this, but if you want a more recent example of a well-secured device being hacked, read into the fusee-gelee exploit on the Nintendo Switch.. Not only is it a hack that exploits the kernel of the Switch, but it is a coldboot exploit meaning that it was impossible to patch until Nintendo released a dedicated hardware upgrade in the form of v2.0 switches.

To confirm I tried to inject hekate (after having formatted my SD following this guide: https://www.youtube.com/watch?v=U2DTVnupXjQ) using https://github.com/Qyriad/fusee-launcher/find/master - unfortunately the launcher didn't do anything after 'smashing the stack' and the switch screen didn't turn on - so pretty confident that it's a patched switch.

The name Fusée comes from the vulnerability found in 2018 that enables all of the homebrew possibilities (https://github.com/Qyriad/fusee-launcher/blob/master/report/fusee_gelee.md). And surely the Fusée payload utilizes that vulnerability.