PS3 PSNpatch - Releases / Usage Information (Official Support Thread)

[gDrive]

Cool, perhaps the problem was using the program to disable CFW when I needed to use the plugin itself to disable CFW, I would think either should work but that would actually make sense if that's the case.

I would personally advise AGAINST using multiMAN to mount games as it has a homebrew-specific game ID (BLES80608) and it cannot be spoofed as a legitimate retail game (if you try to do that, it would overwrite the PARAM.SFO file and the XMB Images so that it would STILL COME UP AS MULTIMAN WITH THE GAME ID BLES80608), so therefore I would only advise you to use the STEALTH version of multiMAN if it is up-to-date but DeanK HAS NOT YET released a STEALTH multiMAN 04.75.00, and I personally feel like asking him regarding this though I am not sure as to how he would react to this LOL.

That said, Iris Manager, which CAN be spoofed as a legitimate retail game (I suggest spoofing it as such before installing it) would be the safest route for mounting games, and as for PS3 firmware updates, you CAN do that if you want to (the more close your PS3 setup is to a 1:1 OFW setup, the better), but I have mine deleted to prevent accidental updates.

 

[pinky]

well, as I've said before, I think what sony may be looking at is the xregistry. the xregistry has an allow/deny function for install pkg files. it merely makes the install pkg function appear. it won't allow pkg files to be installed without altering the sprx, but simply allowing that function to appear, one can reasonably assume the person is on cfw. that's where I personally think a ban flag is placed. spoofing another game probably wouldn't matter. that's what flash carts do on the 3ds, but that's not what Nintendo looks for. they look for a flash clip to allow save functions, then try to create a file that's larger than the flash clip. can't say for nds games, but 3ds flash clips allow a 512Kb file. anyway, that'd be an easy way to know.

 

[PatrickBatman]

I would personally advise AGAINST using multiMAN to mount games as it has a homebrew-specific game ID (BLES80608) and it cannot be spoofed as a legitimate retail game (if you try to do that, it would overwrite the PARAM.SFO file and the XMB Images so that it would STILL COME UP AS MULTIMAN WITH THE GAME ID BLES80608), so therefore I would only advise you to use the STEALTH version of multiMAN if it is up-to-date but DeanK HAS NOT YET released a STEALTH multiMAN 04.75.00, and I personally feel like asking him regarding this though I am not sure as to how he would react to this LOL.

That said, Iris Manager, which CAN be spoofed as a legitimate retail game (I suggest spoofing it as such before installing it) would be the safest route for mounting games, and as for PS3 firmware updates, you CAN do that if you want to (the more close your PS3 setup is to a 1:1 OFW setup, the better), but I have mine deleted to prevent accidental updates.

So now I feel like I should be using kokotonix's KW lite webman instead of multiman being it runs into the background but im new to ps3 online stuff. And if they see im using ZUMA all the time that'll prolly look suspicious as its a dumb psn game. Anyway so much differing info on this, I wish there was just a straight answer currently the thing that sounds most reasonably safest i cant even do because as you said stealth mM 4.75 isn't even out. oh jeez.

 

[gDrive]

So now I feel like I should be using kokotonix's KW lite webman instead of multiman being it runs into the background but im new to ps3 online stuff. And if they see im using ZUMA all the time that'll prolly look suspicious as its a dumb psn game. Anyway so much differing info on this, I wish there was just a straight answer currently the thing that sounds most reasonably safest i cant even do because as you said stealth mM 4.75 isn't even out. oh jeez.

LMAO any legit software or game is fine and Sony will not get suspicious if it is legit software, or spoofed as legit software and as for Iris Manager, you can spoof it as any game or software - heck, you can spoof it as Vidzone or Netflix or even Metal Gear Solid: Ground Zeroes if you wanted to.

As for game-mounting homebrew, webMAN lite or Iris Manager spoofed as a legit game is your best bet in the meantime.

 

[PatrickBatman]

I noticed after using PSN Patch that app_home and install package files are still on the XMB. I'm wondering kokotonix if you can hide these when the CFW syscalls are disabled? Just temporarily until reboot. I know webman hides app_home but then webmans icons are on the XMB instead. I've never used SEN enabler but gDrive said it is able to hide install package files and app_home to be more like OFW.So I figured you could do it as well, unless that is you think it's a bad idea in terms of ban safety.

(I think i could figure out how to do it myself in code pretty easily but I'd have to add and remove code every time which is a lot more time consuming than just having a program to do it automatically. I've never written homebrew myself, just fixed eboots for everyone back in 3.56 days so it's been a long while since coding ps3 anything for me since compiling C+ and perl scripts :old

 

[kozarovv]

[MENTION=13550]PatrickBatman[/MENTION] Believe me PSNPatch is safe in form that is now. No need to any change. [MENTION=230]gDrive[/MENTION] it doesn't matter which app mount your backup psnpatch delete history before run game. Also if sony really want to catch you they check lv2_kernel.self or any needed to mod cfw file. For now there is no need to any step to hide cfw more than is hided now. If sony change licence agrements then any app can't help us.

Also PatrickBatman and gDrive please keep this threat about PSNPATCH - USAGE INFO. / RELEASES INFO. if you want talk about ban risk or how to minimalize this risk use this threat: http://www.psx-place.com/forum/gene...d-accounts-2441.html?highlight=banned+account or any other releated.

Thank you.

 

[PatrickBatman]

It was just a suggestion. I was waiting for you to say something about that (although every post I made mentioned PSN patch in it somewhere, just checked ) as I've been a mod/admin at basically every ps3 scene site except here and hax. I'm just going to assume XMB plugins are safe as well being PSN patch plugin is being used that means webman can be used as it's also a plugin. PSN PATCH!! thanks koktonix, kozarovv and gDrive. I think I'll shutup for awhile :zipped:sorry for my annoyance.

 

[kokotonix]

I noticed after using PSN Patch that app_home and install package files are still on the XMB. I'm wondering kokotonix if you can hide these when the CFW syscalls are disabled? Just temporarily until reboot....

It is a good suggestion but it is not needed

 

[kokotonix]

Does psnpatch stealth extension (is plugin? right? ) is compatibile with Cobra 7.02 firmwares? In my case i mean Darknet 4.70 (cobra 7.02) http://www.psx-place.com/forum/ps3-...70-cobra-builds-v7-02-7-03-released-1491.html

Darknet changelog clearly states that is incompatible, but PSN patch is firmware independent. How about plugin? All i want to know, can i safely use PSN patch plugin with Darknet 7.02 or i should install 7.03 version (ps. i know is better 4.75)

Let me use your question to comment some subjects from the last days:

1
PSNPATCH should be compatible with all CFW version. the new stealth v3 auto install and removes itself from memory and COMPLETELY disables CFW syscalls.
Some CFW functions will be disabled as for instance the ability of mount new games until the next reboot - that's why games should be mounted before disabling CFW.
That's also why some apps complain about unknown firmware version, and some games get black screens.

2
a black screen game can be fixed by mounting it as ISO.

3
The new stealth extensions included in the last psnpatch versions (being 2015.7A the latest ATM) are the safest stealth approach to go online with A PS3 running CFW !

4
Install the plugin and use it to disable CFW and regain PSN access (L2 R2 R3 in the XMB).

5
Psnpatch plugin can also be configured to auto spoof IDPS and PSID at boot time - and so mimicking another console at all time.

6
Never go online with version spoofed CFW.


That's all I remember right now.
I will post more when I fit appropriate.

 

[gDrive]

It is a good suggestion but it is not needed

Then explain this:

[PS3] CFW Ban Counter Measures - Call of Duty: Black Ops 2 Mods, Cheats and Guides - Page 2 - NextGenUpdate

This does NOT stop you from being BANNED for MODDING!!!!
Treyarch scans your PS3 Folders, Do not have these folders on your PS3 when you run Black Ops 2 from CFW.
And for you DEX users look at the last one...

/dev_hdd0/game/BLES80608
/dev_hdd0/game/TOGGLEQAF
/dev_hdd0/GAMES
/dev_blind
/dev_hdd0/game/SDISABLER
/dev_hdd0/game/BLND00001
/dev_hdd0/game/VEBUSPOOF
/dev_hdd0/game/HTSS00003
/app_home/PS3_GAME

nice, where did you find this? in the eboot?

na not in eboot, in bo2 mem dump
and i want to say it comes down with the playlist update, but not sure

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F


018BA300              2F 64 65 76 5F 68 64 64 30 2F 67 61      /dev_hdd0/ga
018BA310  6D 65 2F 42 4C 45 53 38 30 36 30 38 00 00 00 00  me/BLES80608....
018BA320  2F 64 65 76 5F 68 64 64 30 2F 67 61 6D 65 2F 54  /dev_hdd0/game/T
018BA330  4F 47 47 4C 45 51 41 46 00 00 00 00 2F 64 65 76  OGGLEQAF..../dev
018BA340  5F 68 64 64 30 2F 47 41 4D 45 53 00 2F 64 65 76  _hdd0/GAMES./dev
018BA350  5F 62 6C 69 6E 64 00 00 2F 64 65 76 5F 68 64 64  _blind../dev_hdd
018BA360  30 2F 67 61 6D 65 2F 53 44 49 53 41 42 4C 45 52  0/game/SDISABLER
018BA370  00 00 00 00 2F 64 65 76 5F 68 64 64 30 2F 67 61  ..../dev_hdd0/ga
018BA380  6D 65 2F 42 4C 4E 44 30 30 30 30 31 00 00 00 00  me/BLND00001....
018BA390  2F 64 65 76 5F 68 64 64 30 2F 67 61 6D 65 2F 56  /dev_hdd0/game/V
018BA3A0  45 42 55 53 50 4F 4F 46 00 00 00 00 2F 64 65 76  EBUSPOOF..../dev
018BA3B0  5F 68 64 64 30 2F 67 61 6D 65 2F 48 54 53 53 30  _hdd0/game/HTSS0
018BA3C0  30 30 30 33 00 00 00 00 2F 61 70 70 5F 68 6F 6D  0003..../app_hom
018BA3D0  65 2F 50 53 33 5F 47 41 4D 45                    e/PS3_GAME

I'm just curious as to how you came to the conclusion as o why hiding app_home/Package installer XMB entries isn't necessary?

 

[kokotonix]

Then explain this:

[PS3] CFW Ban Counter Measures - Call of Duty: Black Ops 2 Mods, Cheats and Guides - Page 2 - NextGenUpdate

I'm just curious as to how you came to the conclusion as o why hiding app_home/Package installer XMB entries isn't necessary?

Thank you for your questions.
I will try to answer them without creating a very long answer and looking at the fact that I'm not a native English speaker (that may led in some misspelling and understanding issues).
I will try to simplify things and will also avoid much of the tech mambo jambo in order to produce a more readable text.


1. HDD ACCESS

PSNPatch was prepared by looking, not only at the ps3 behaviour, and transmitted packages over the net, but also over KW knowledge of the PS3 architecture and the information detailed by SONÿ in the leaked PS3 SDK.
Without being a PS3 specialist, we know that games running in the PS3, do it in a isolated and separated memory space.
PS3 Games also have dedicated and exclusively reserved hdd space under its "USRDIR" folder substructure.
For instance, an app with CID BLES0000 will have access exclusively to /dev_hdd0/game/BLES0000/USRDIR.
That is why it is so easy for developers to test if a game is running moded, because there must be changes in this folder structure.

Games have also access to save and load game progress but not through a direct dev_hdd0 access but using specific sony sdk methods and procedures.

This kind of isolation has many advantages in a modern OS as the PS3 and it is currently used by most top OS available – of course this is out of the scope of this message and it should be discussed in another topic.

Back to our scope:

With this implementation an official ps3 game can detect if it is running modded but should not be able to detect if there are illegal files in the hdd (as multiman installed and so on).
But even if there are "illegal" files, or a game has access to other areas (which I doubt for the reasons stated before - read the PS3 SDK docs ) that proves nothing: one may even be running CFW and decides to go into OFW.
I believe we all agree that his system will then be legit, and even if he does not format its PS3 hdd, all the CFW apps will remain in the disk (not working anymore, but still there).
With this I pretend to transmit the idea that the hdd contents should not pose an issue for running games detecting a running CFW.


2. MEMORY SPACE

Additionally, games are running in a limited privilege implementation, which denies them access to memory spaces outside its own, namely, LV1 and LV2, which access (trough syscalls) is needed to validate a running CFW.

PSNPatch accesses the space outside its own reserved memory space because it is unofficially (not approved or endorsed by SONÿ) compiled for a CFW environment with higher privileges linkage.
PSNPatch plugin runs with even higher privileges.
The new stealth 3 extensions runs in LV2 memory space as top ("kernel") privilege – this is the way to fully and correctly disable the syscalls, and it is only possible for the reasons stated before.

An official game running for OFW is not able to do so.


3. XMB CONTENTS

XMB contents (as app_home or install packages) are registered and configured in dev_flash and dev_flash2 (xregistry).
These are virtual file system spaces and once again for the reasons stated in 1, games should not access them.
Additionally, even in a CFW environment, higher privileges are needed to access flash, which is not available to official games.



PS:
About the tests you refer in the beginning of your message, I do not know them, and I do not know enough of the testing environment specifically used in order to even speculate about its contents, source or propose.

PPS:
OFW running environment comments are somehow speculative as KW doesn't have an official (hardware based) development kit, as I bet 99,999% of the scene developers.

PPPS:
I know some of the ideas I've written are subject of further, and more detailed discussion, and we may not all agree on them, but I believe they are consensual enough to a vast majority – PSNPatch implementation with around 2 years of success, should be the living proof of it.


Thank you for reading and I hope it is roughly understandable

 

[kokotonix]

Following my last post, I would like to add some additional comments:

All this said, PSNPatch is the "safer" approach to use when connecting to the PSN with a modded PS3.
But it doesn't mean that it is "safe".
The only real "safe" thing to do is to format the PS3 hdd and install an official firmware version.


Furthermore, some guys asked me if SONÿ cannot detect CFW.
Yes. If they want-it, they can.
They can easily change the PS3 firmware to test if running from an altered version or if using a changed IDPS.
It is damn easy to do it from startup and even to avoid booting, and repeat the test several times during runtime.
Or even testing it randomly while gaming, thus creating seriously difficulties to patch while creating the CFW.
In fact, it is really easy: but they would have to do some changes in the firmware.
At the moment they are not doing it. Looking at the way they've implemented the firmware, and the methodology they usually use for the upgrades, it doesn't seem to be something to be done in a minor version.
If the PS3 was still SONY's flagship console, they would probably put-it in firmware 5.XX.
But the PS3 is slowly dying.
PS4 is now the focus of their development.
If you ask me, I would say that most probably those issues will never be corrected.
But who knows ?

It is just so easy to do, that I must ask:
Why haven't they done it before ?
Is there a willing motive to allow some PS3 to be jailbroken ?
Why is that ?

 

[PatrickBatman]

I agree they shouldn't be allowed out of the USRDIR directory mainly due to personal privacy breeches of their customers, but that doesnt mean they are ACTUALLY doing that, because as most of us know Edward Snowden revealed that the NSA and the UK were using private information in a manner not consistent with what they were saying publicly (Xkeyscore and Tempora). But again I agree with you because I think they can do it just wont cause they simply dont care anymore due to (like you stated) the ps4 being the flagship console now.

EDIT:
forgot

And whos to say just because someone goes back to OFW that sony can't and doesn't ban people who have CFW files? Sony could think well this system was jailbreaked before so they have already breeched our terms of service contract so it doesn't matter they've decided to go back to OFW now. It's like the police not arresting a serial killer for his past crimes because he's stopped killing (extreme example).

 

[kokotonix]

...

And whos to say just because someone goes back to OFW that sony can't and doesn't ban people who have CFW files? Sony could think well this system was jailbreaked before so they have already breeched our terms of service contract so it doesn't matter they've decided to go back to OFW now. It's like the police not arresting a serial killer for his past crimes because he's stopped killing (extreme example).

Well ... I'm no layer.
But for what I understand from their usage policy, it seems that if are not using CFW you are not violating.
But again ... I'm no lawyer.
But that's a good question to place to them.


Anyway, it's kinda easy to implement a file system handler that locks access to certain folders. Well ... It is easy in concept but very dull to implant. May be someone else cares to do it...

 

[boxbundy]

Thank you for your questions.
I will try to answer them without creating a very long answer and looking at the fact that I'm not a native English speaker (that may led in some misspelling and understanding issues).
I will try to simplify things and will also avoid much of the tech mambo jambo in order to produce a more readable text.


1. HDD ACCESS

PSNPatch was prepared by looking, not only at the ps3 behaviour, and transmitted packages over the net, but also over KW knowledge of the PS3 architecture and the information detailed by SONÿ in the leaked PS3 SDK.
Without being a PS3 specialist, we know that games running in the PS3, do it in a isolated and separated memory space.
PS3 Games also have dedicated and exclusively reserved hdd space under its "USRDIR" folder substructure.
For instance, an app with CID BLES0000 will have access exclusively to /dev_hdd0/game/BLES0000/USRDIR.
That is why it is so easy for developers to test if a game is running moded, because there must be changes in this folder structure.

Games have also access to save and load game progress but not through a direct dev_hdd0 access but using specific sony sdk methods and procedures.

This kind of isolation has many advantages in a modern OS as the PS3 and it is currently used by most top OS available – of course this is out of the scope of this message and it should be discussed in another topic.

Back to our scope:

With this implementation an official ps3 game can detect if it is running modded but should not be able to detect if there are illegal files in the hdd (as multiman installed and so on).
But even if there are "illegal" files, or a game has access to other areas (which I doubt for the reasons stated before - read the PS3 SDK docs ) that proves nothing: one may even be running CFW and decides to go into OFW.
I believe we all agree that his system will then be legit, and even if he does not format its PS3 hdd, all the CFW apps will remain in the disk (not working anymore, but still there).
With this I pretend to transmit the idea that the hdd contents should not pose an issue for running games detecting a running CFW.


2. MEMORY SPACE

Additionally, games are running in a limited privilege implementation, which denies them access to memory spaces outside its own, namely, LV1 and LV2, which access (trough syscalls) is needed to validate a running CFW.

PSNPatch accesses the space outside its own reserved memory space because it is unofficially (not approved or endorsed by SONÿ) compiled for a CFW environment with higher privileges linkage.
PSNPatch plugin runs with even higher privileges.
The new stealth 3 extensions runs in LV2 memory space as top ("kernel") privilege – this is the way to fully and correctly disable the syscalls, and it is only possible for the reasons stated before.

An official game running for OFW is not able to do so.


3. XMB CONTENTS

XMB contents (as app_home or install packages) are registered and configured in dev_flash and dev_flash2 (xregistry).
These are virtual file system spaces and once again for the reasons stated in 1, games should not access them.
Additionally, even in a CFW environment, higher privileges are needed to access flash, which is not available to official games.



PS:
About the tests you refer in the beginning of your message, I do not know them, and I do not know enough of the testing environment specifically used in order to even speculate about its contents, source or propose.

PPS:
OFW running environment comments are somehow speculative as KW doesn't have an official (hardware based) development kit, as I bet 99,999% of the scene developers.

PPPS:
I know some of the ideas I've written are subject of further, and more detailed discussion, and we may not all agree on them, but I believe they are consensual enough to a vast majority – PSNPatch implementation with around 2 years of success, should be the living proof of it.


Thank you for reading and I hope it is roughly understandable

I have read that some games have been found to have hdd0 searches for backup managers when they've been examined. It's been recommended to format the hard drive when going back to ofw for this reason. I can't remember who said this but they were reputable.

 

[kokotonix]

I have read that some games have been found to have hdd0 searches for backup managers when they've been examined. It's been recommended to format the hard drive when going back to ofw for this reason. I can't remember who said this but they were reputable.

Thank you for your comment but it would be very helpful if you could identify the source and the game / games, as until today I haven't found any.


Sent from a mobile device using Tapatalk

 

[Joonie]

Thank you for your comment but it would be very helpful if you could identify the source and the game / games, as until today I haven't found any.


Sent from a mobile device using Tapatalk

I recall that game was COD BO2 which has the most online cheaters. It's funny how those game modders go online with spoofer without any protection but not worrying about ban issues..

Hey guys...came across this earlier....any truth to this? Is it really that simple?


*the only way to play black ops 2 online without banned

hey guys we always loves call of duty but not the old one we love the fresh one it's black ops 2
we don't always to play it on solo we love to play it online
sadly is treyarch black ops 2's servers on scaning every ps3 console
ofw and cfw
if they locate an homebrew on the console they will send you a band this is what treyarch studios are scaning for

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

018BA300 2F 64 65 76 5F 68 64 64 30 2F 67 61 /dev_hdd0/ga
018BA310 6D 65 2F 42 4C 45 53 38 30 36 30 38 00 00 00 00 me/BLES80608....
018BA320 2F 64 65 76 5F 68 64 64 30 2F 67 61 6D 65 2F 54 /dev_hdd0/game/T
018BA330 4F 47 47 4C 45 51 41 46 00 00 00 00 2F 64 65 76 OGGLEQAF..../dev
018BA340 5F 68 64 64 30 2F 47 41 4D 45 53 00 2F 64 65 76 _hdd0/GAMES./dev
018BA350 5F 62 6C 69 6E 64 00 00 2F 64 65 76 5F 68 64 64 _blind../dev_hdd
018BA360 30 2F 67 61 6D 65 2F 53 44 49 53 41 42 4C 45 52 0/game/SDISABLER
018BA370 00 00 00 00 2F 64 65 76 5F 68 64 64 30 2F 67 61 ..../dev_hdd0/ga
018BA380 6D 65 2F 42 4C 4E 44 30 30 30 30 31 00 00 00 00 me/BLND00001....
018BA390 2F 64 65 76 5F 68 64 64 30 2F 67 61 6D 65 2F 56 /dev_hdd0/game/V
018BA3A0 45 42 55 53 50 4F 4F 46 00 00 00 00 2F 64 65 76 EBUSPOOF..../dev
018BA3B0 5F 68 64 64 30 2F 67 61 6D 65 2F 48 54 53 53 30 _hdd0/game/HTSS0
018BA3C0 30 30 30 33 00 00 00 00 2F 61 70 70 5F 68 6F 6D 0003..../app_hom
018BA3D0 65 2F 50 53 33 5F 47 41 4D 45 e/PS3_GAME

ok these are without keys


/dev_hdd0/game/BLES80608
/dev_hdd0/game/TOGGLEQAF
/dev_hdd0/GAMES
/dev_blind
/dev_hdd0/game/SDISABLER
/dev_hdd0/game/BLND00001
/dev_hdd0/game/VEBUSPOOF
/dev_hdd0/game/HTSS00003
/app_home/PS3_GAME

see those things if the severs have located them the servers automatically reports to sony
ok guys what if we deleted all those things

You can delete BLES80608 = Multiman we can stealth it as a psn game just we need to change the id

TOGGLEQF that u don't need it

GAMES Folder the scan on the HDD it self and not the external so u can delete this folder and your games must be on external

BLND00001 can be deleted
VEBUSPOOF can be deleted
HTSS00003 can be deleted

the last one app_home

this is the proplem
i try to deleted but no luck if there is anything to delete it just put it here

Dev_Blind can't be seen becuase multiman can disable it

so this thing is usefull we need only to delete app_home the we are cleare or devolopers can creat a fast custom firmwire only to play black ops 2 online but this custom firmwire must not have app_home we can load the game from external hardrive by multiman and then deleting muliman

and load the game from the disc but all the things that i posted it up must be deleted or u will get banned

Source

Only way to play Black Ops 2 without Ban Info - Any truth to this??? - Call of Duty: Black Ops 2 Mods, Cheats and Guides - NextGenUpdate

 

[kokotonix]

I recall that game was COD BO2 which has the most online cheaters. It's funny how those game modders go online with spoofer without any protection but not worrying about ban issues..



Source

Only way to play Black Ops 2 without Ban Info - Any truth to this??? - Call of Duty: Black Ops 2 Mods, Cheats and Guides - NextGenUpdate

[MENTION=29]Joonie[/MENTION],
Thank you for your previous comment.
Being the second one reported about BO2, I will investigate it further.
(where did that test came from ? where was it found ? which file have does locations configured ? etc …)
I have no doubt that BO2 do test if running modded (by simply looking into their own USRDIR files)
But In case it proves to be true that they access other filesystem areas, I will have some difficulty in understanding how can they do it from the official ps3 sdk, and the legitimacy of reporting it to sony.
Anyway, and again if proved its reality, we must urgently implement new syscall handlers for the file access in order to block access to a "black list" of dev_hdd0 locations.

I will report back.


Thanks



[edit]
btw, That info at nextgen is from March 2014 and I'm sure I've played several times on-line with BO2 since then, from both my original bluray and from the ISO i've made without a ban...
(But note I've never played modded).

 

[PatrickBatman]

and again if proved its reality, we must urgently implement new syscall handlers for the file access in order to block access to a "black list" of dev_hdd0 locations.

Why not just do this anyway? Is it too time consuming? Will it cause other problems? If it won't do any harm and offers potential extra protection I just don't see why you just don't implement it anyway. (As far as locations to block, any location that wouldn't plausibly be on OFW)

EDIT:
Perhaps this answers my question

Anyway, it's kinda easy to implement a file system handler that locks access to certain folders. Well ... It is easy in concept but very dull to implant. May be someone else cares to do it...

Is PSN patch open code so someone else could implement this? I would but I've never written homebrew, only did some C, C+,C++,perl, pascal,cobol compiles (well cobol and old perl are interpreted languages and not compiled but you get my drift) and eboot fixing in 3.56 days (before just anyone could do it) shows how old i am and how long its been. Perhaps if you convert PSN Patch over to fortran I could then do it, JK hahahaha

 

[kokotonix]

Why not just do this anyway? Is it too time consuming?

Implementing the syscall handler itself and intercepting fsopen calls is rater easy.
The most time consuming is the black list handling and testing.

This is something independent from psnpatch or any other tool - it could even be a separate plugin - even if it makes more sense doing it inside psnpatch itself.
Unfortunately, time is not much to invest in psnpatch, and I do believe it would be very difficult to ever be implemented in it.