Homebrew Clarification Thread - What is going on?

  • Thread starter Thread starter JustPingo
  • Start date Start date
  • Views Views 647,692
  • Replies Replies 5,356
  • Likes Likes 103
Status
Not open for further replies.
They're getting pretty close. Looks like two new files have been added to the source today alone.
 
Seriously, why do people keep spamming refresh and commenting every time a commit is done in the github?

If/When it's done, the team behind it will make an announcement in it's own thread for everyone to see, there's no need to stalk the repo and constantly annoy whoever is working on it.

As someone who's done stuff before, nothing is more annoying than having people (figuratively) breathing down your neck asking when things will be ready.

But to stay on topic, it was mentioned that SNShax (which is no longer being worked on) would in theory have a workaround for O3DS, does anyone have any rough ideas of what this could have been?
 
Seriously, why do people keep spamming refresh and commenting every time a commit is done in the github?

If/When it's done, the team behind it will make an announcement in it's own thread for everyone to see, there's no need to stalk the repo and constantly annoy whoever is working on it.

As someone who's done stuff before, nothing is more annoying than having people (figuratively) breathing down your neck asking when things will be ready.

But to stay on topic, it was mentioned that SNShax (which is no longer being worked on) would in theory have a workaround for O3DS, does anyone have any rough ideas of what this could have been?

I mean it's annoying when a commit only includes cleanup or debug stuff, but it makes sense to post it here when a commit includes actual code additions.

And no, nobody knows about the workaround.
 
About the workaround, my first bet would be to abuse the fact that there is a service I can't recall the name that reboots NS when it is spawned. But don't call me on that as it's just a guess, I don't see how one could exploit that.

KTM isn't snshax, it's the app that would have used it.

Edit : omg that ninja
 
Last edited by JustPingo,
KernelTimeMachine is the name of the new program that they are using to downgrade via memchunkhax2. They ditched snshax and moved KTM to memchunkhax2
Really? So no more SNSHax??
And i thought i was lucky because i had my N3DS on 9.8 and was going to get the downgrade sooner than others...

I guess it won't hurt to update to 10.3 and get ironhax then.
 
About the workaround, my first bet would be to abuse the fact that there is a service I can't recall the name that reboots NS when it is spawned. But don't call me on that as it's just a guess, I don't see how one could exploit that.

KTM isn't snshax, it's the app that would have used it.

Edit : omg that ninja
somehow marking the area of memory as "used" or making sure the area isn't cleared out could work... It'd just be super hard to exploit if NS cleans up after itself (which it probably does...) unless you could mark the RAM page read only
 
  • Like
Reactions: JustPingo
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum