webMAN MOD

PS3 webMAN MOD - General Information Thread 1.47.48q

I have an idea for a webMAN MOD feature.
---Remote OSK .. Ability to type from device when the PS3 On Screen Keyboard opens. A great "2nd Screen" type feature.
 
I have an idea for a webMAN MOD feature.
---Remote OSK .. Ability to type from device when the PS3 On Screen Keyboard opens. A great "2nd Screen" type feature.

Yes it would be a neat feature, but I haven't found a way to send keyboard commands to the OSK.

BTW I uploaded a new test build of VSH Menu for webMAN 1.01
http://aldostools.org/temp/test/wm_vsh_menu.sprx

It has no new commands. I only changed the communication interface with webMAN MOD. Now it uses http requests like prepNTFS. So the response to the commands should be 1-2 seconds faster and some commands should be now compatible with deank's webMAN 'vanilla'.
 
When i've disabled syscalls and then i try to unmount game then the disc symbol stays in XMB but without showing game icon and i'm not able to start game... is this normal ?
 
When i've disabled syscalls and then i try to unmount game then the disc symbol stays in XMB but without showing game icon and i'm not able to start game... is this normal ?

No, it's not normal.. Does it happen only after disabling syscalls? I remember that I saw this issue happening with my PS2ISOs, but I haven't seen it again after some changes that I made to unmount isos.

Are you using PS3ISO or JB folders or is it happening with other type of games?

---

BTW I have uploaded a new test build of webMAN MOD 1.43.16 (WIP)
http://aldostools.org/temp/test/webftp_server.sprx

In this build it's possible to configure the video recording options using R2+SELECT+L3.

There are 5 preset configurations:
Code:
M4HD HD720 5000K AAC_64K
MPEG4 368p 2048K 30FPS AAC 64K
AVC MP 272p 768K PCM 768K
MPEG4 240p 512K AAC 64K
MJPEG HD720 11000K AAC 96K

Using L2+SELECT+L3 it's possible to customize the particular settings: video format, video size, video bitrate, audio format and audio bitrate.

Once you choose the setting that you want to change using L2+SELECT+L3, use R2+SELECT+L3 to change the value of the selected setting.

NOTE: Not all combinations are valid. So it's better to don't mess with L2+SELECT+L3 unless you want to try a different setting.
The valid settings can be found in the SDK:
.\cell\target\ppu\include\sysutil\sysutil_rec.h
 
No, it's not normal.. Does it happen only after disabling syscalls? I remember that I saw this issue happening with my PS2ISOs, but I haven't seen it again after some changes that I made to unmount isos.

Are you using PS3ISO or JB folders or is it happening with other type of games?
I have:
- Habib Cobra 4.76 V1.00, webMAN_mod 1.43.15 + VSH-menu, Latest PSNPatch plugin, Browser : Webkit
- Games are in PS3ISO folder on NAS
- issue happens with [online] tag but also when i disable syscalls via :R2: + :/\:

And another question just to be sure: When i've disabled syscalls i can't mount any game... when trying i get message that syscalls are already disabled... this is normal behaviour ??

Regards
Rudi
 
Last edited:
I have:
- Habib Cobra 4.76 V1.00, webMAN_mod 1.43.15 + VSH-menu, Latest PSNPatch plugin, Browser : Webkit
- Games are in PS3ISO folder on NAS
- issue happens with [online] tag but also when i disable syscalls via :R2: + :/\:

And another question just to be sure: When i've disabled syscalls i can't mount any game... when trying i get message that syscalls are already disabled... this is normal behaviour ??

Regards
Rudi
PSNpatch should disable all syscall (syscall 8 too) and so you can not mount any games
 
[MENTION=161]Matsumot0[/MENTION]
Build 1.43.16 is on my server with the following changes:

* VSH Menu now uses http network interface to execute webMAN commands (it must be faster & some commands must be now compatible with vanilla edition)

* Added option to browse URL on PS3 to the slider menu (mobile.html)

* webMAN.xml now open the web pages using webKit, except "CPU & RSX temperatures" that uses silk mode.
- Unmount & Insert Disc now auto-closes

* In Lite Edition: Added: remove syscalls. Removed: fix game & support for fake isos generated by IRISMAN: ntfs[FILE]. Binary is now smaller.

* Video Recording now can use custom settings for audio & video formats/size/bitrate.
- Use R2+SELECT+L3 to change the settings values
- Use L2+SELECT+L3 to choose the settings to be changed
- Current recording video & audio formats now are displayed in the popup
- The video & audio formats can be configured via /setup.ps3

* Removed video_rec.sprx from updater

* Added option to disable custom syscalls 200, 201, 203, 204 (ccapi) through syscall.ps3mapi.
* Syscall 1022 (prx loader) is now disabled by [online] tag and R2+/\ combo.

* SRC: Moved some files to cobra/unused
* SRC: Changed 8 to constant SC_COBRA_SYSCALL8 in Cobra modules. So it can be changed easily to another syscall number in the future.

* [BGM] toggler is now shown in /cpursx.ps3 if a game is running. (Only available in the test build. It may hang the console returning to XMB)
* Test build: Added /sysbgm.ps3 and swap kernel (not included in the updater)

* Syscalls 200, 201, 203, 204 (installed by CCAPI) are also disabled. There is a CCAPI check box in /setup.ps3, untick it to leave them enabled.

* Improved display of links/text in utf8 in File Manager

* /cpursx.ps3 now shows the last mounted game when /dev_bdvd is mounted.

* Added webftp_server_full.sprx to the updater. This build is compiled with almost all the compilation flags enabled (except a few).

* Fixed nonCobra editions... games were returning to XMB due a bad libfs.sprx in /dev_hdd0/tmp

* Added display of ICON0 in File Manager

* Added <Play> link to /dev_bdvd in File Manager


In a side note: I have been trying to add ntfs library to the project (to support FTP transfers to/from NTFS). But the project throws errors when I compile it. Maybe some dev could assist me in make it compile.
 
[MENTION=161]Matsumot0[/MENTION]
Build 1.43.16 is on my server with the following changes:

...

Now the question is: should I also add syscalls 200, 201, 203, 204 (ccapi) to the combo that disable the syscalls?

IMO they should be disabled too for safer access to PSN... but if I do it probably I'll have more haters than usual... especially the cheaters.
Who cares about haters...
Even though I don't use cheats so I suppose I could be biased. However I do go online though & safer is better.
What does KW think about this? [MENTION=118]kozarovv[/MENTION] ?
What about a partially/fully disabled option? Same idea as ps3mapi...

Sent with Tapatalk
 
Who cares about haters...
Even though I don't use cheats so I suppose I could be biased. However I do go online though & safer is better.
What does KW think about this? [MENTION=118]kozarovv[/MENTION] ?
What about a partially/fully disabled option? Same idea as ps3mapi...

Sent with Tapatalk

Aldo suggested the idea to prevent CCAPI allowing cheat online :) well that will result in loss of some webman users :)


Sent from my iPhone using Tapatalk
 
I understood & I realise that the end users' happiness are the only thing that matters in the end.
All I meant was safer is better so disabled CCAPI syscalls make sense. However, maybe the option to choose between all syscalls disabled vs partially disabled (all but CCAPI) could be a good idea. Cheaters would still have the option of they wanted...

Sent with Tapatalk
 
I understood & I realise that the end users' happiness are the only thing that matters in the end.
All I meant was safer is better so disabled CCAPI syscalls make sense. However, maybe the option to choose between all syscalls disabled vs partially disabled (all but CCAPI) ciuld be a good idea. Cheaters would still have the option of they wanted... [emoji6]

Sent with Tapatalk

We can also let SONY take care of it :)


Sent from my iPhone using Tapatalk
 
Aldo suggested the idea to prevent CCAPI allowing cheat online :) well that will result in loss of some webman users :)

Anyway I've added a happy medium :p Now the user can decide if CCAPI syscalls are disabled or not.
Unchecking "CCAPI" option next to "DEL CFW SYSCALLS" will keep CCAPI syscalls. By default they will be deleted.

Now they can be restored too through /syscalls.ps3mapi (this page has been merged with /syscall8.ps3mapi for a better overview of all the syscalls)

The command /play.ps3 now redirects the response to /cpursx.ps3 after launch the disc, instead of show a page with back button.
That way the user can see immediately the title/id of the game playing and monitor the temperature (specially useful when used from smartphones/tablets).
 
PSNpatch should disable all syscall (syscall 8 too) and so you can not mount any games
Thx 4 answer... but this leads me to another problem related to that:
1. Assume i've tagged a game with [online]-tag and enabled "Mount last played game at system start"
2. Restart System -> game mounts -> syscalls are disabled by PSNPatch -> i can play the mounted game... but i can not mount another game because of the disabled syscall 8

Workarounds i've found:
A) Unmount game -> Restart system -> no game is mounted on systemstart and therefore syscalls are not disabled -> mount another game
B) Disable "Mount last played game at system start"

Both of which is not ideal.
How's about not to process the [online]-tag for the auto-mount-game ?... or even better...
Is it somehow possible to process the [online]-tag only when the game is started by user ? (Then user would have the chance to change the auto-mounted-online-tagged game because syscalls are still intact)

Regards
Rudi
 
Last edited:
Thx 4 answer... but this leads me to another problem related to that:
1. Assume i've tagged a game with [online]-tag and enabled "Mount last played game at system start"
2. Restart System -> game mounts -> syscalls are disabled by PSNPatch -> i can play the mounted game... but i can not mount another game because of the disabled syscall 8

Workarounds i've found:
A) Unmount game -> Restart system -> no game is mounted on systemstart and therefore syscalls are not disabled -> mount another game
B) Disable "Mount last played game at system start"

Both of which is not ideal... how's about not to process the [online]-tag for games which mounts at system start ?... or is it somehow possible to process the [online]-tag only when the game starts ?

Regards
Rudi

Your issue is due PSNpatch that is disabling syscall8... IMO PSNpatch should include an option to not disable syscall8 and let to use PSN only if the syscall8 is faked.

Your other option is not use [online]-tag, and disable the syscall on demand using R2+/\ which is not so difficult.

If you only use webMAN MOD you shouldn't have that issue... but you won't have the extra safety that PSNpatch could provide...
 
Your issue is due PSNpatch that is disabling syscall8... IMO PSNpatch should include an option to not disable syscall8 and let to use PSN only if the syscall8 is faked.

Your other option is not use [online]-tag, and disable the syscall on demand using R2+/\ which is not so difficult.

If you only use webMAN MOD you shouldn't have that issue... but you won't have the extra safety that PSNpatch could provide...
Yes i know... but i'm pretty sure KW will deny to add such an option because it will decrease the savety level of PSNPatch. (May be [MENTION=124]kokotonix[/MENTION] read this and has another idea)
So i thought that ignoring the [online]-tag for the auto mounted game would be the easiest way around this little obstacle. (Although the best solution immo would be to process the [online]-tag only when a game is started)

I guess 4 now i will go with workaround B :(

Regards
Rudi
 
Last edited:
Yes i know... but i'm pretty sure KW will deny to add such an option because it will decrease the savety level of PSNPatch. (May be [MENTION=124]kokotonix[/MENTION] read this and has another idea)
So i thought that ignoring the [online]-tag for the auto mounted game would be the easiest way around this little obstacle. (Although the best solution immo would be to process the [online]-tag only when a game is started)

I guess 4 now i will go with workaround B :(

Regards
Rudi

I understand if KW decides to not add the option, although IMO the benefits would be greater than the potential risk.

Regarding ignoring the [online] tag would make webMAN's safety inconsistent (assuming that everyone also uses PSNpatch). If the user added the [online] tag is because he/she wants the syscalls auto-disabled when the game is mounted. If the game is mounted without disable the syscalls, the user could be accessing PSN with the syscalls enabled (if PSNpatch is not used).

As you said, the best option would be to disable the syscalls when the game is launched (it could also work for npDRM games)... but Cobra/Mamba payload needs to be modified to detect when an EBOOT.BIN is launched and check if it has the [online] tag. Also a few new opcodes would be needed to make this feature an option. I don't know if team Rebug is interested in adding this function.

EDIT:
webMAN also could disable the syscalls when a game is started, since it knows when a game is running (it polls the status every ~10 secs), but in that interval the game could have detected if the syscalls are enabled or not. Increasing the frequency of polling could affect the performance badly.
 
I understand if KW decides to not add the option, although IMO the benefits would be greater than the potential risk.

Regarding ignoring the [online] tag would make webMAN's safety inconsistent (assuming that everyone also uses PSNpatch). If the user added the [online] tag is because he/she wants the syscalls auto-disabled when the game is mounted. If the game is mounted without disable the syscalls, the user could be accessing PSN with the syscalls enabled (if PSNpatch is not used).

As you said, the best option would be to disable the syscalls when the game is launched (it could also work for npDRM games)... but Cobra/Mamba payload needs to be modified to detect when an EBOOT.BIN is launched and check if it has the [online] tag. Also a few new opcodes would be needed to make this feature an option. I don't know if team Rebug is interested in adding this function.

EDIT:
webMAN also could disable the syscalls when a game is started, since it knows when a game is running (it polls the status every ~10 secs), but in that interval the game could have detected if the syscalls are enabled or not. Increasing the frequency of polling could affect the performance badly.

The issue with recovering syscalls table started when it was discovered that the lv2 syscalls table was being sent to sony when connecting to the psn.

That is why one of the psnpatch functions is to clear the syscalls table entries for all the known cfw syscalls (6,7,8,9,10,11,35,36) replacing with the "not found" syscall entry (the one of syscall 0).
This way, when connecting to the psn, and sending it to sony, it will "appear" as an OFW syscalls table.
Futher more, if any game tries to "test" if running on CFW by the means of calling one of those syscalls, it will receive the "not found" error (as it should be on OFW – even if a "good behaved" game should not call any syscall: but we already suspect that there are some "bad behaved" games out there).

Cobra, mamba, ps3mapi and others are relying on syscall 8 to keep working (namely swapping games).
Some approaches rely on NOT "disabling" syscall 8 to keep full working functionality vs protection against psn.
I don't agree with that approach: my opinion is that the entire table should be cleaned.
Cobra will be "suspended" ? yes ! This means that no other game backup could be mounted until the system is rebooted (and cfw syscalls are re-instated) – for 99%+ of the users this is not a problem (myself included).

Not doing things this way (keeping syscall 8 table entry ) is dangerous.
Having an option to do it or not, is also dangerous – most users will not understand what they are doing and will leave the system in a more "unprotected" state.


Additionally let me explain that, as cobra protects the syscall table, some approaches don't change the syscalls table, but only the pointer to the functions – this may be a very big risk, as any lv2 process checking the syscall table, may easily detect it as "NOT original".

The approach psnpatch does is running from LV2 memory space and effectively "cleaning" the syscalls table (including syscall 8) ignoring any "Protection".
From tests make by KW with different PS3 and different accounts over the past 2 years – it is most than proved to been working.
How much time more ?
Well … only time will tell…
;)
 
Back
Top