Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's surprising that they deploy all of that debug stuff onto the console and then hide the switch behind a big lock to be picked. Why not just not deploy it?


Apparently the debug stuff are needed for servicing. Plus if someone manages to run custom code, having the debug options or not becomes irrelevant.


> Apparently the debug stuff are needed for servicing

Yeah, that makes sense. I'd have thought it would be better to have an ephemeral debug client that's deployed from remote if you have the key to the big lock, but perhaps that's for the PS6.

> Plus if someone manages to run custom code, having the debug options or not becomes irrelevant.

Agreed, but it might be harder as they have to write custom tooling to inspect the system.


I can't speak to PlayStation but on Xbox switching into (at least a limited) development mode just requires the right cert [0].

[0] - https://learn.microsoft.com/en-us/windows/uwp/xbox-apps/devk...


I'd guess a lot of it is in hardware and firmware which would be very costly to change that late into the development cycle


Not to mention it can break stuff. If QA tested everything with the debug stuff being on the console but temporarily hidden, that's how you want to deploy it as well, otherwise you're gonna have retest and surely fix a bunch of stuff before deploying.

Yes yes, systems should not act like that, probably means everything is too tied together. But real world systems do act like that, especially in things with not too high stakes and with high focus on shipping stuff quickly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: