the new PS4 jailbreak is sort of hilarious

The PS4 has been hacked by a 20 year old bug! (yes 2006 was almost 20 years ago)
Exploit: github.com/TheOfficialFloW/PPPwn
Writeup: hackerone.com/reports/2177925
🏫 COURSES 🏫 Learn to code in C at lowlevel.academy
👕 MERCH 👕 Like the shirt? lowlevel.store
📰 NEWSLETTER 📰 Sign up for our newsletter at mailchi.mp/lowlevel/the-low-down
🛒 GREAT BOOKS FOR THE LOWEST LEVEL🛒
Blue Fox: Arm Assembly Internals and Reverse Engineering: amzn.to/4394t87
Practical Reverse Engineering: x86, x64, ARM, Windows Kernel, Reversing Tools, and Obfuscation : amzn.to/3C1z4sk
Practical Malware Analysis: The Hands-On Guide to Dissecting Malicious Software : amzn.to/3C1daFy
The Ghidra Book: The Definitive Guide: amzn.to/3WC2Vkg
🔥🔥🔥 SOCIALS 🔥🔥🔥
Low Level Merch!: lowlevel.store/
Follow me on Twitter: / lowleveltweets
Follow me on Twitch: / lowlevellearning
Join me on Discord!: / discord

[@LowLevelLearning]

wanna get good at programming? check out lowlevel.academy and use code THREADS20 for 20% off lifetime access. or dont. im not a cop

[@susstevedev]

I love my programing looking like it was written in 2005 and horid function names.

[@Kane0123]

Did you say your name is Ed instead of Low Level Learning for the first time? Classic Ed move to sneak that in

[@R00kTruth]

I believe any system can be jail broken, via the ethernet port....and of course some smart developers,

[@brianmo2611]

going off on a limb here but i would say they wrote the code in that manner to make it harder for people to read on purpose.

[@mu11668B]

That "im not a cop" at the end makes everything 10 times more sketchy 🙂

[@RadikAlice]

This is more normal than what it took to hack the Wii. Which was a figurative and literal, pair of tweezers

[@Notevenmad955]

Probably equally as insane as the tweezer hack on the wii, was doing a man-in-the-middle attack on the pcie bus of the ps4. The same team that did the tweezer hack on the wii used an fpga board(connected to the ps4 apu) and another PC(where the ps4 “chipset” was connected) and connected those 2 using 115200baud serial(kinda downgrading PCIe to 0.00002x)

[@crism8868]

Man. When I hacked my PSP, I did by loading images of eggs to it that make it crash lol Those were the day am I right

[@RadikAlice]

@@Notevenmad955 As painful as it sounds, makes perfect sense

[@SystemError-wb2vi]

@@Notevenmad955 nerd

[@BrostroTheWizard]

Holy f*ck I forgot doing that. good times indeed.

[@theondono]

“You can tell this is from ‘07 because of the variable names” The Go team in complete shambles 😂

[@mignon9230]

Bro, that was cold, but so true... hahaha

[@PaulFisher]

don’t talk about when the design of Go as a language looks like it came from

[@brentonbills5946]

I came to write this 😂

[@MSThalamus-gj9oi]

People who wrote code like that in 2006 had likely been coding since the 80s, or were heavily influenced by those who had been. I've also been writing code since the 80s, though, so I can tell you that by 2006, single letter variable names were frowned upon, but abbreviations like "buff" were still common place.

[@VonCarlsson]

"buf" is still common and that's a good thing

[@Vaalin]

But think of all the bytes you could save by shortening your variable names!

[@jbinmd]

Even in the 80s we were trained to use descriptive variable names. Did we do it? Arguably. I mean, buf isn't that bad.

[@Tomyb15]

The code shown for the exploit used the exact same naming conventions.... It's not that bad

[@MantasXVIII]

​@@VonCarlssonDepends on the context. If there's more than one, such as I see daily in rendering code, ibuf vbuf isbuf is very fun to read and decipher....

[@kiri101]

Dang, now people who bought devices can run their own code on them

[@llvn11]

The horror

[@MelroyvandenBerg]

so dangerous, right? As if you bought a product.

[@TUDORMARCU16]

@@MelroyvandenBerg It's worse than that. It's as if you're owning the product.

[@AG-ur1lj]

meaningless comment about how we all got the joke he made

[@igordasunddas3377]

@@TUDORMARCU16 yeah, the elites won't like that!

[@lemagreengreen]

You talk about 2006 like it was a long time ago! Oh no...

[@NXE212]

The kids born during then can be certified for forklift driving by around this year

[@kaasbaas9532]

i was 6/7 years old :(

[@donaldtrump2]

I was one years old 😂

[@ryan.c.s]

I wasn't even alive.

[@shabadrandhawa3829]

my age was in the negatives.

[@AhnkInside]

Please don't give Me a heart attack and call 2006 "20 years ago." It was only 18 years ago.

[@btarg1]

I'm a little disappointed we didn't get to watch you jailbreak your own ps4/5 with this

[@mbcrump]

kzbin.info/www/bejne/j3OldqyPqM-becksi=mzGD29gZIcZNNZhZ&t=419

[@Lamoboos223]

Yeah, I wanted to see a demo too :(

[@psychosomatiqueofficial]

Sony dev in disguise

[@xChrisyFTWx]

Search up Modded Warfare

[@Tuckdragon]

lookup modded warfare, he got tons of videos on it

[@freedustin]

"P comes out of H+1" Man...that is not what 4chan told me.

[@DanteS-119]

Thanks for NOT dumbing this down.

[@polite3606]

The author of the exploit seems to be TheFlow which has been in the console hacking scene forever (PSP, PSVITA). Thanks for the code breakdown!

[@FAKEAXIS]

Can't believe the Xbox one ended up being the most impenetrable home console ever created.

[@soggytoast111]

The achilles heel of the PS4 has really been relying so much on open source modules, especially FreeBSD for the kernel. Every time there is a critical CVE, it's open season for another jailbreak. Microsoft has the privilege of being able to build around in entirely closed source environment. It makes reverse engineering a much more daunting task.

[@ralphard]

It also gives you dev mode for $20

[@tbuk8350]

The polar opposite is the Wii U, which can be hacked with an SD card and the web browser.

[@slamslam-qw8qi]

​@@tbuk8350 Wii is easier to hack and way easier to set up storage

[@meeponinthbit3466]

Probably because it's a POS no one is really interested in. Being able to softmod a PS4 opens easy piracy to a LOT of less technical gamers.

[@crushermach3263]

bug reported: 2006 PS4 release: 2013 PS4 FW 11 release: 2023 FW 11.02 (Dec 2023) _may_ have fixed it? Unsure. This bug was known about 7 years before the PS4 existed and it's still been in there for nearly its entire lifespan. Crazy.

[@istvandjumber6474]

"...and the PS4 is now effectively yours..." sad words, sad world...

[@KevinTurner-aka-keturn]

That's some nice work, but I spent most of the time here being flabbergasted that a PS4 has a PPPoE client at all.

[@ryanilari3537]

That’s most likely because the PS4 kernel is a modified OpenBSD kernel. They likely just didn’t disable it

[@TetrisMaster512]

​@@ryanilari3537 It's based on FreeBSD, but yes, this was just inherited functionality. Weirdly, the PS4's OS is supposedly based on FreeBSD 9, which is from 6 years after this was patched, so I'm guessing they didn't fully rebase on FreeBSD 9 but kept code around from the PS3's OS (also partially based on FreeBSD), which is basically contemporary with the vulnerability.

[@forbiddenera]

Exactly what I was thinking like pppeewhat

[@kinnikuzero]

<a href="#" class="seekto" data-time="142">2:22</a> no, P is stored in the balls

[@ezioauditoredafirenze8352]

So is sperm stored in the bladder then?

[@gFamWeb]

Honestly the most surprising thing to me about this is that they have a low level device object for the notification UI. I would think that would be handled by some higher-level API, but I guess not.

[@gertjan1710]

Maybe they do and that API makes use of the device as a persistent location.

[@Axman6]

When you build an OS on FreeBSD, you might as well do things the Unix way.

[@unstopabalz]

Wow this entire exploit is like an overview of my reverse engineering course I just took. Everything from creating shellcode, identifying and exploring buffer overflows, creating ropchains, defeating protections like ASLR, and heap exploitation. The only thing that is missing that would make this exploit and entire course overview is fuzzing and creating scripts in binja/ghidra

[@hriad]

waw, a course covering all those aspects of reverse engineering sounds interesting. Where can i find this course??

[@kcnl2522]

Im also interested on that course xD

[@nicolasfuchs3072]

@@hriad I would also be interested in that

[@SFTaYZa]

@@nicolasfuchs3072 yeah cough it up buddy

[@jjackson4727]

OP, please bless us w/ the course

[@isomeme]

A few of us cared about good naming conventions 20 years ago. A very few of us cared 40 years ago. It's good to have more allies today. My favorite software joke: The two hardest problems in software engineering are naming, concurrency, and off-by-one errors. 🙂

[@nutbastard]

It sounds like there are 11 kinds of people 😉

[@angel_luis]

As note, it was released on 2013, so probably it was coded between 2010-2012, so its not far away from 2006. So it has been jailbroked after 11 years. PS3 was jailbroked after 3-4 years only.

[@klairm9097]

there has been a lot of other exploits before this one, iirc 4-5 years after release

[@Trustmage]

@@klairm9097 flatz jailbroke 1.76

[@soggytoast111]

PS4 has been jailbroken many times before on earlier firmwares. This one is just the latest one that works until 11.00. Also Sony is constantly patching the software with updates, this bug could have been patched at any point between 2013 and now, but it wasn't because no one knew it was in there until now.

[@elvendragonhammer5433]

True, but what he was referring to is that this exploit was already in the wild in 2006, which is why it the claimed date is roughly correct. There are plenty of other exploits using the same vulnerability, just with different hardware, or ordered increments. Honestly can't wait till PS4 stops getting updates, so we don't ever need 2 worry about patches screwing with custom ecosystems anymore.

[@zandr0]

@@elvendragonhammer5433 Might be a long ways off. Even the PS3 had a recent-ish update. But definitely share the sentiment!

[@luketurner314]

<a href="#" class="seekto" data-time="76">1:16</a> once jailbroken, "the PS4 is now effectively yours". So before jailbreaking, you can't put your own software on it. If you can't do whatever you want with it, do you really own it?! Even if you bought it, purchased it, paid for it, if you don't have full and total control over the device, do you actually OWN it?! What does ownership even mean these days?!

[@powerLien]

legally, the console hardware is yours, but the software on it is licensed to you by sony, and sony can revoke that license at any time (though I am not aware of any instances where they have done this to anyone). given that the software is installed in such a way that sony hopes you will never be able to modify it without their consent, the hardware is also effectively controlled by them in practice unless you find a way to get past their protections, hence what is said in the video that is to say, ownership means what it always has, in a sense, but software companies keep trying to find ways for that to be less useful to you. another good example is with modern games; technically you don't own those either, they're also just licensed to you, and that license can be revoked at any time. I believe it's technically been that way from day 1, but it's only within the last 10-20 years that publishers have gained the ability to actually enforce that through modern DRM but also remember: if buying isn't owning, then piracy isn't stealing :)

[@Brahvim]

@@powerLien Wait, even the OS IS GIVEN under a license?! Wow, I want to read the T&Cs on this one!...

[@powerLien]

@@Brahvim windows is like this too. if you change the hardware in your computer too much without reinstalling windows, it will revoke itself, because microsoft bases the validity of a windows license on the particular hardware configuration windows sees when it's first installed technically, you don't really own any software that you don't make yourself, even if it's free. what matters is the terms under which it's licensed to you. ex: linux is licensed to you under the GPL, which in practice means it's free forever

[@moister3727]

Eh, Linux is free and fully yours

[@Zcalyps0]

@@powerLien amen to that

[@-EndlessHorizon]

The algorithm deemed this foreign video as permissable to watch. Even though i dont understand your language you sound very confident so i agree whole heartedly.

[@garrettrinquest1605]

Someday I hope console makers will realize their stuff is gonna get hacked and just lean into the user freedom angle. Kinda like the stream deck is doing now

[@DigitalDiabloUK]

They do; they just hope the defenses last long enough so they can get to their next iteration without someone breaking it and defeating DRM etc. It's why I suspect Microsoft allowed developer mode on the Xbones, those who want to write games and apps can do so, without having to exploit the whole system, leaving that area only for the pirates to investigate.

[@vlc-cosplayer]

The PS3 let you officially install Linux. I think they removed that because they were worried someone would use the Linux environment for jailbreaks... But ironically, taking away Linux created a much bigger incentive to jailbreak the console, that is, bringing Linux back 😆

[@ca_kay]

@@DigitalDiabloUK Wasn't the Switch broken, like, Day 1? You can't defend anything with an OS

[@mofik26]

Yeah, steam is this whole "piracy is a utility issue" thing, provide a good service and it goes away mostly.

[@t0m_mcc]

Eventually though steam servers will one day shutdown, and then do we really own anything?

[@danielsan901998]

This is why memory safe languages like rust are bad for user freedom.

[@talonhackbarth7652]

LOL

[@mskiptr]

*that's why BSD should have been under the GPL

[@matthewrease2376]

​@@mskiptrwhere's the lie? This message brought to you by GPL superiority gang

[@thesenamesaretaken]

Yeah I've been unironically wondering about this. It's nice that software is less likely to be taken advantage of by malicious third parties, but what do you do when it's the vendor themselves who is the malicious actor?

[@antonf.9278]

@@thesenamesaretaken Get out the soldering iron. No software can totally protect it self from the layers of abstractions below it.

[@itwaslikethiswhenifoundit5941]

Thanks for doing this rundown! Heap exploits always seem to have to be wildly complex -- building primitives, finding targets, getting rw/exec'ble memory, getting to stack, cleaning up... always nice to get the nickel tour

[@CortexExists]

You can't just to round 17 years to 20, Aubrey

[@Whomst12321]

Aubrey 💀💀💀💀💀

[@h-aandle]

nope he can

[@yuyuyuyuyuy484]

LMAO

[@pranavbadrinathan6693]

18*

[@Lelende]

You ought to have a series sort of documenting how various consoles and machines were jailbroken sort of like MVG but maybe more code oriented/step by step

[@itemushmush]

MVG is a king. He gets down and dirty with the code, but this channel is even lower-level than that!

[@clebbington]

agreed!! would be awesome to see a low level oriented console hacking series

[@fdwr]

<a href="#" class="seekto" data-time="179">2:59</a> "You can tell this code was written in '06 ... naming variables like buf and r and p and h" - Even back in 2006, those were terrible variable names, and coding naming guidelines said to favor readable pronounceable whole words over obtuse fragments (at least I recall the Windows API design guidelines stating that, attempting to correct past blunders :b).

[@squirlmy]

although, Windows apps are meant to run, and be updated for years. Game consoles, not so much.The only coders looking at this code are trying to hack the console! It's not nearly so desirable to have readable code in the console world (unless you're porting a particular game to other platforms)

[@UnCoolDad]

Can work both ways. Sometimes you include code that is so old,it doesn't have any if the newer vulnerabilities in more modern versions of that code 😂

[@Shonicheck]

Ah the good'ol "too broken to be lockpicked" strategy

[@v01d_r34l1ty]

This comment deserves more likes 😂

[@bpw]

You should look at the earlier jailbreaks, it's crazy what has happened over the years to the PS4 with some "fixes" not actually addressing the issue

[@TallinuTV]

Wow, that was wild. Thanks for going through it like that! ❤

[@tredband92]

Thanks for the video. My constructive feedback is to zoom in a big more on the code so it’s easier to see in the video. Watching on my phone the code is too small to see. Love the content!

[@nomore6167]

"...you have jailbroken your PS4; you can put your own apps on there, you can load your own software, and the PS4 is now effectively yours to do whatever you want with" - Which is exactly the way it should be for hardware which you purchased with your own money.

[@BrandyBalloon]

Nice to meet you Ed 😊

[@0dayCTF]

This is wild! Awesome content as always. So crazy that was around 20 years.

[@LowLevelLearning]

YOOOO my guy! Thank you! 🫡

[@fransmanlaparis4830]

Very good video, easy too follow even though some parts get a little too advanced for myself. 18 year old code weakness is insane :D

[@supremebeme]

this stuff is over my head but i still enjoy your content

[@casev799]

So I have already have a broken PS4... Time to have fun with it I gues

[@FelipeV3444]

I'm curious as to how much we'd be able to achieve with this. Cause I'd love to install Linux and Steam on my PS4 and use its GPU for essentially PC gaming lol.

[@btwiusearch2]

@@FelipeV3444 sadly the gpu driver for the ps4 is not shared by sony so on linux you will be using the integrated graphics of the cpu which is horrible for gaming

[@SanekGamer007]

​@@btwiusearch2linux has been ported to ps4 (currently only for older jailbreaks like 9.00) and it has gpu drivers. also ps4 doesnt even have dedicated graphics iirc

[@btwiusearch2]

@@SanekGamer007 sorry i meant gpu acceleration it doesnt have that

[@btwiusearch2]

@@SanekGamer007 i also had linux on a jailbroken ps3 and that too had gpu driver but no graphics acceleration but some one somehow programmed a graphics acceleration driver for the ps3

[@RoraighPrice]

I like this guy's approach to talking, he knows he's talking about something complicated but manages to not be condescending and spells things out for us un knowledgeable in his special field

[@go0oh]

I love the CLRS in the background :)

[@PaulFisher]

<a href="#" class="seekto" data-time="182">3:02</a>: “naming variables things like buf and r and p and h are just, like, terrible naming conventions” don’t let Rob Pike catch you saying that; they’re still acting like you get charged by the byte when you write golang source code

[@hobbified]

You get charged by the character when you read it. The longer the name, the more it distracts you from seeing the shape of the code and understanding what it actually does.

[@Nekroido]

@@hobbified only if the code itself is short, neatly written, and contains no bugs. I've spent way too much time deciphering unreadable mumbo jumbo in my career just because some bright minds wanted to use up the entire alphabet for variables instead of treating a programming language as, well, an actual language 😅

[@repairtech9717]

Short variable names should only be used within very short functions. People are making out like you write all go code like this. Calling an integer you are manipulating, i, in a 3 line function for instance. If you are using short variable names in any other way, you are doing it wrong.

[@PaulFisher]

@@repairtech9717 ideally yes. however, in my dealings with the arbiters of Go style from my time at Google, and from reading the stdlib, there was a strong cultural norm towards shortness for its own sake, even at the expense of what I would judge as readability.

[@PaulFisher]

@@repairtech9717 when writing Go code at Google, in my experience the style reviewers for the language strongly pushed authors to shorten variable names in most situations, even beyond the “just a few lines” case (which, in that particular context, I would not find objectionable)

[@bsvenss2]

Love your T-shirt! 🙂

[@dasdos002]

Love it too! Came to the comments to say the same thing lol

[@eyezikandexploits]

As someone in the "hacking" seine i really like how you explained the exploit, its pretty wild how it got exploited

[@pato6350]

I love your channel so much! ❤

[@priyanshuupadhyay4854]

One last video before i go to bed , This video

[@nickst2797]

Did you go to bed yet?

[@priyanshuupadhyay4854]

@@nickst2797 ya dude , good night its 2:20 am here in india

[@anonp2958]

@@nickst2797 I wonder if we can get people to leave nice comments for him to wake up to?

[@darksequenceyt2446]

Have cholay and anda in ur breakfast lol!

[@scattagain]

Im also gonna sleep after this, 4:30am for me >:D

[@ClayTheFoxx]

<a href="#" class="seekto" data-time="146">2:26</a> missed opportunity to confirm that pee is stored in the balls

[@oafkad]

That laugh hurt.

[@chrisholder3428]

Thanks this is a very good dive.

[@leovin00]

Me completely fascinated by even the basic socket receive and notification send code 😂

[@invalidation]

Thinking readable code wasn’t a standard in 2006… 🤣 It was a practice that was ignored just as it often is now, and as it was when I got started in the 90’s

[@DavidCowie2022]

"If it was hard to write, it should be hard to read."

[@Ty4ons]

You can search for Critical Program Reading (1975) to see just how old it is. People have been struggling with unreadable source code since the dawn of programming and have tried to figure out solutions. Part of it is the background too. If you're used to math then single character variables often feels like the cleanest solution, but in Java it should be a sentence.

[@lvlinty]

In 2006 Perl still saw regular ( yet dwindling use). Php owned the web and jQuery wasnt really on the scene yet. I think a lot of people are confusing 2006 and 2014...

[@invalidation]

@@DavidCowie2022 some developers seem to think that “security through obscurity” is a coding style and applies to job security.

[@4rumani]

it wasn't ignored "as often as it is today" at all, they obviously cared about it less. are you stupid?

[@fardinhaque70]

Wish you gave TheFlow0 a shout out because that guy is a legend when it comes to sony console exploits.

[@thedeadblitz]

damn thats crazy complex props to the one who put all that together, so many moving parts

[@s81n]

It's funny you mentioned you can tell the code looks written long ago, I thought the same thing. (I've been programming since the 90s and was happy seeing people starting to name variables nicely as the years went by.)

[@roisoleilxiv14]

Would be interesting to test if this works on the PS3 OS aswell. As far as i know, it is also based on BSD, but i dont know whether the PS4 also has the lv1 lv2 hypervisor structure

[@wingedzero]

Memory exploits often cause the ps3 to crash. The risk for bricking is too high so they are not ideal.

[@81milliontotallylegitimate10]

Not accurate at all ​@@wingedzero

[@sirtra]

Entirely different processor, definitely won't work. Ps3 was a weird console that developers hated because it was so weird.. same reason it's so hard to emulate even to this day.

[@mobslicer1529]

real name reveal is crazy

[@Brahvim]

I've always wanted it, and he finally did it! Hey, Ed! Thanks for all the videos!

[@Sarfarazzamani]

Why should he care when he has already revealed his REAL face? 😀

[@echeese63]

"P comes out of H+1" after being stored in the balls, obviously

[@stoneworld7556]

Short code variable names were common in older code in part due to carryover from small memory days. They offen abbreviated file names for the same reason.

[@1____-____1]

Wanna feel old? 2004 was 20 years ago. I was a lost kid at uni drinking cheap beer...

[@UnknownUnrecognized]

uni 1968...

[@v01d_r34l1ty]

Born in '03, drinking cheap beer myself now. :)

[@sunsetman22]

I wish I could say this to myself 20 years from now

[@1____-____1]

@@sunsetman22just dont win a Darwin Award and you'll be good.

[@1____-____1]

@@sunsetman22Not with that attitude... You'd be amazed how fast a couple of decades can wiz by.

[@id104335409]

Actually an open code game console WOULD BE WILDLY SUCCESSFUL!!!! Everyone will want one and all the indie developers will want to create games for it and port their old games for it. The potential is MASSIVE! All you need is a safe store that is protected so that devs get their money. Imagine everyone who does game related stuff - games, mods, items - everyone can put their own prise. Sure, you could pirate, but I imagine not many pirates would want to pirate stuff available on the console for like 1$ that goes to the developer and not Ubisoft. Plus open source means holes will be plugged pretty fast.

[@nagaserpentico]

That was the whole pitch of the Ouya way back in the day. Wound up not being very successful, but I always admired the ideal behind it. It's just very difficult to be successful in the modern console space. there's a lot of open portable devices though, so there's something at least

[@jordanb722]

We have that - it's a regular computer XD

[@zynaps666]

Superb video. I wondered why it was so complicated. Luckily I'm on 9.00 so I'll be sticking with my ESP32 s2 mini for now but it seems it's time to start trawling the spares or repairs on fleabay again.

[@yourdemiseishere]

Meanwhile everyone with a PS4 that has standards against piracy now rushing to crack their stuff.

[@Rollthered]

hehe he said pp

[@Trumben]

Not only that, he also said pp pee

[@Winnetou17]

Who's this Ed and what have you done with Low Level Learning ?

[@kiseitai2]

The irony is that it is Sony products that made me interested in code security concepts because I had a PSP and exploits like this one or exploits using images (forgot which image format) would happen often enough you always had a chance to switch to custom firmware. I think that has made me a better developer, albeit one disappointed by a lot of current enterprise code or disappointed when my patches to up the number of characters in a password field was rejected… because it was certain to cause issues for customers. Haha. Console exploits to enable CFWs is an insane world!

[@demolazer]

Wow. Some of the stuff that's been achieve in the console world is on another level. I remember watching something where some people reverse engineered the NES hardware with no documentation.

[@Nono-hk3is]

Using buf and ptr and h as variable names had been going on since 1970 and continues to occur today. There's nothing 2006 about it .

[@poisonouspotato1]

I like your funny words, magic man

[@JohnThePon]

The next time I complain about a black duck scan at work, I'll come back and watch this... 😅

[@almirchowdhury9557]

love your videos been always been interested in how exploits work. Pleaseeee do an ios jailbreak overview :)

[@horrorislander]

Wears shirt saying "everything is open source if you can read assembly" while complaining about abbreviated variable names! :-)

[@shizeeque]

<a href="#" class="seekto" data-time="92">1:32</a> a small clarification. PPP and PPPoE are not the same. PPP as you mentioned stands for Point-To-Point Protocol it's a dial-up connection daemon. PPPoE stands for PPP over Ethernet. It's a Ethernet connection daemon using PAP/CHAP for authentication. The difference between PPP (pppd) and PPPoE (rp-pppoe) is one used to connect over a landline telephone wire and another (your case) is used to connect over Ethernet.

[@JacobLock]

Very easy to parse explanation, thank you!

[@Hiiiro]

It was a wild reminder of my age to me when you said "'06" and "20 years ago" back to back.

[@cardboardbox_tech]

P comes out of...

[@saifhussain3303]

Description doesn't seem accurate 👀

[@Cmanorange]

the apple playstation

[@happycolours8551]

Hmmm 🤔

[@LowLevelLearning]

thank you youtube is trying to end my career ong

[@Shildr5]

Thank you for this. Interesting, informative, understandable. Very enjoyable.

[@mrmanny1418]

Thanks for your video, i have no idea how to read code, but your explanation is very interesting, even though i have no idea what you’re saying!

[@replikvltyoutube3727]

It was also noted there that it works on PS5. Is this really the time we are going to see more PS4 and PS5 as Linux desktops?! Would be fire actually

[@rj7250a]

I mean, they have x86_64 CPUs, you just would need drivers for GPUs (same arch as AMD desktop GPUs) and the wifi chip, and some more firmware.

[@The2011andrey]

from what i know, you can run linux on the ps4, if you have the firmware 9.00 and below jailbreak, i don't know how it is for the 11.00 one.

[@MattDog_222]

His name is what? LLL?

[@jrn_v1]

Very well explained, great video

[@bigutubefan2738]

Awesome video! Cheers dude.

[@Jshicwhartz]

2024-2006 is not 20 years my guy.... regardless, thats a cool find! Now for someone to run it via GPT and have it clean up the code and find some fun things to do with it.

[@init_yeah]

Not, if you round up

[@DanteS-119]

Why the hell would you run it with gpt, just run the file directly

[@Jshicwhartz]

@@DanteS-119 Did you just see GPT and not read the rest of what I put?

[@Jshicwhartz]

@@init_yeah untrue, rounding up means you are looking at it from a floating point value. In this case, it's 2024-2006 is 18. You can't round 18 to 20 lol. Simple maths.

[@Alberto-ww7vb]

Bloodborne for Pc is coming rahhhhhhhhhhhhhhhhhhh

[@newsofthenerd]

Ed kidnapped Low Level Learning. Never forget, never surrender, stay strong LLL 💪

[@LowLevelLearning]

Who told you

[@fgfsgdomagerd]

lmao I thought this was Modern Vintage Gaming because of the title and colour scheme of the thumbnail

[@jogurcik13]

Just a reminder: fuck sony

[@ProtossOP]

Based and true

[@warezit]

-20 years ago, developers used names like "p" and "h" because of hardware restrictions (specifically harddrive space), it wasn't because they liked doing it that way. 😉 You need to write code a bit differently when you only have 120 MB of space for the operating system and all your programs and files, compared to today where everyone has GBs of free space at all times.- ... Love that shirt btw!! 😀 Thank you everyone for all the feedback! I ended up researching this topic a bit more, and learned a lot! 😎

[@Niosus]

Your variable names don't exist after compilation, so no need to be terse for that. If you're talking about memory limitations of the developer's computer... In 2004, it wasn't unusual to have a GB of RAM. The contents of a text file really didn't bother computers by then. Maybe this was an issue in the 80's, but not in the 00's. Half Life 2 came out in 2004. Crysis would release just 3 years later. It really wasn't the dark ages anymore. Computers were fast and had plenty of RAM for software development. I've worked with a guy who still named variables like that in 2016 or so. He was getting close to retirement and just stuck in bad habits. People just didn't think as much about code maintainability.

[@warezit]

@@Niosus Those are definitely good points! I keep forgetting how 20 years ago means 2004 😭 I'm getting too old! 🤣

[@welcometovalhalla2884]

@@Niosus I was basically gonna write the same comment, I was a kid back then but I think our home PC had a 128gb hard drive and 512mb of ram around that time. I think the variable names do exist somewhere in interpreted languages so maybe it was a concern for late 90s Java/JS/PHP programmers? More likely to be habits taught by people who programmed even earlier tho

[@talonhackbarth7652]

Yeah, it's not so much hardware limitations, since the names don't stick around after compilation, but more because C programmers for a while had a habit of writing this way and that got passed down to many developers. A lot of older c programmers came from assembly which is where some of it stems from. Sort of the opposite of Java devs 800 character names, LOL

[@thesenamesaretaken]

Wew mate my childhood 386 machine back in the early 90s had more than 100MB of hard drive space. I'd very surprised if even back then people worried about how much space their variable names would take up

[@lorddorker3703]

Showing my age but that naming convention buf,p,etc.. would have not passed code reviews from 30 years ago maybe in the 70's when memory was limited.

[@TechXTech91]

i would assume the code you're looking at is decompiled code in some form, which might be why the variables are p/h/r/buf etc. It just places generalized variables. I see this a lot in my reverse engineering of old stuff

[@ding.1367]

rawr

[@LowLevelLearning]

xd

[@katana2k]

I imagine that “naming things properly” has been a thing since the first time somebody was expected to work on code they didn’t write

[@unusvita9346]

Your introduction got me to subscribe thats a nice intro

[@MikeHarris1984]

20 years ago people wrote tons of spaghetti code. You had two backwards engineer tons of code to figure out what it did if you need to make a change. And that was the way I was taught and early on I started making notes in my code and making my strings and variables names that anybody could see what it is and take it apart easily and work with it.

[@johnsmithking6646]

I feel soo dumb right now

[@onedeadsaint]

your break down of the code reminds me of playing a OTK deck in yugioh; everything is chained together in this ridiculous combo

[@juchemz]

great walkthrough!

[@deltacx1059]

<a href="#" class="seekto" data-time="74">1:14</a> rather you now actually own the thing, what a concept.

[@Kuromusha]

I had no clue what this man said & still left entertained & informed.

[@adversHandle]

Subscribed that was very interesting 🤔

[@virtualizeeverything]

i love how you go though all the steps

[@Daniel-it1dp]

I have current coworkers who use that “2006” variable naming methodology.