makes the exploit runs 100x100 of times and also ON BOOT!

[canariaslink]

Maybe need to adjust the time if you have ssd or something wich cause your system power up too soon , else with hdd it's ,tried on pro 11.00 .no fail , no crash

proof here:

https://www.mediafire.com/file/jo21oogi8gtfuoe/5902031530020049787.mp4/file

[canariaslink]

Maybe need to adjust the time if you have ssd or something wich cause your system power up too soon , else with hdd it's ,tried on pro 11.00 .no fail , no crash

proof here:

https://www.mediafire.com/file/jo21oogi8gtfuoe/5902031530020049787.mp4/file

btw i'm MiralaTijera a old ps3 scener :-D

[khalid7863]

Dear MiralaTijera
i am new to github and don't know how to perform the operation you just did on that video uploaded the link here, Can you please help where is that boot.bat file and how can i do this on my ps4 pro ? waiting for your great response.

[canariaslink]

hi there! here you have a pack ready to use:

https://www.mediafire.com/file/n4513v2k99bok9p/MLT_PAYLOADER_ON_BOOT_WORKING_with_npcap.rar/file

it's included:

python latest version
scapy
PPPwn sistr0 with my mods
first install npcap exe i included in the root of the rar
so when you decompress it you will see the same boot.bat , just edit that file and on cmdline of windows "ipconfig /all" find your rj45 interface name and copy as is and replace the one i put by default on --interface="the name of your rj45 interface" and save it , run it and power on the console , and if you have the console preconfigured on PPPoE just wait ,you will see te PPPwn msg on press ps button step on powering on the console , remember you need your rj45 interface connected to your computer and ps4 directly without hubs or routers... enjoy ;-)

btw: @SiSTR0 at least u can say a explanation why you refuse the commit? , no one know's the console can be pwned at boot?

[didix16]

Hello @SiSTR0. Is It possible to execute the exploit on PS4 boot time? I mean, FreeBSD should has systemd right? Maybe you can modify the stage2 in such way that create a service that executes the goldhen.bin on boot and thus we don't have to execute the Network exploit anymore once the payload is stored in the HDD.

What do you think?

[DzikiSzogun]

I have on (maybe stupid) question/confusion.

Tell me one little thing.. Why in the commit You call 2 times "payload.bin" into "PAYLOAD_EXT_PATH"

Let me explain. You commited this:
#define PAYLOAD_NAME "payload.bin" #define PAYLOAD_EXT_PATH "/mnt/usb0/payload.bin" PAYLOAD_NAME #define PAYLOAD_INT_PATH "/data/payloads/" PAYLOAD_NAME

So.... We're define "payload.bin" at the first into "PAYLOAD_NAME" ant this is acceptable.
But payload name has been implemented second time into "PAYLOAD_EXT_PATH"
Finally we get something like this "/mnt/usb0/payload.binpayload.bin"...

Maybe I'm not understanding something. But these are basics, not quantum physics
Can you explain this simple relationship to me, why you want to double-load "payload.bin"?

I assume it's a simple oversight. Unless it's supposed to be that way for some reason?

btw. This is not sarcasm but curiosity

[SiSTR0]

this is a fork of exploit and I haven't any exploitable console for this exploit.
I am not exploit dev, so better PR the main repo so TheFlow can review better than me.
Thanks anyway

[canariaslink]

Because depends of the conditions , the name u say it's no Way , because one definition is for externas usb payload ( usb ) and another for internal one so , at final of the code Will check both locations, never this two definitions Will be mixed, that's a n00b question, need to Know the language and programming to understand the code bro... El sáb, 18 may 2024 2:37, DzikiSzogun ***@***.***> escribió:

…

I have on (maybe stupid) question/confusion. Tell me one little thing.. Why in the commit You call 2 times " *payload.bin*" into "*PAYLOAD_EXT_PATH*" Let me explain. You commited this: #define PAYLOAD_NAME "payload.bin" #define PAYLOAD_EXT_PATH "/mnt/usb0/payload.bin" PAYLOAD_NAME #define PAYLOAD_INT_PATH "/data/payloads/" PAYLOAD_NAME So.... We're define "*payload.bin*" at the first into "*PAYLOAD_NAME*" ant this is acceptable. But payload name has been implemented second time into "*PAYLOAD_EXT_PATH* " Finally we get something like this "*/mnt/usb0/payload.binpayload.bin*"... Maybe I'm not understanding something. But these are basics, not quantum physics Can you explain this simple relationship to me, why you want to double-load "payload.bin"? What a coincidence that @SiSTR0 <https://github.com/SiSTR0> can refuse your commit btw. This is not sarcasm but curiosity — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATRDCL2737PJXUZZ6Q57YCDZC2WFPAVCNFSM6AAAAABHQLCPMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGU2TGMRVGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Doyle4]

I have updated Stoogegs Pi PPPwn and see it now has config for delay, Im using an SSD in a Phat PS4 and PPPwn it takes around 4mins as it constantly fails.

Anyone have any recommended time delay settings at all? I see there is also a Buffer setting, sadly no clear instructions.

Thanks