Speaker 1: Welcome to your custom deep dive. Today. We're going to
Speaker 1: explore hacking in cybersecurity with this book, pifes or GTFO,
Speaker 1: real world exploits, coding tricks, you name it.
Speaker 2: Yeah, it's like a hacker's almanac. Really a collection of
Speaker 2: articles really gets you thinking differently about how technology works,
Speaker 2: where vulnerabilities lie.
Speaker 1: Yeah, and right away I was drawn to the section
Speaker 1: on anti forensics.
Speaker 2: That's a good starting point for sure. It highlights this
Speaker 2: back and forth between hackers covering their tracks and investigators
Speaker 2: trying to uncover everything. There's one technique involves a disc
Speaker 2: overwriting its own data while it's being imaged, so.
Speaker 1: They're basically erasing the evidence in real.
Speaker 2: Time, exactly like a puzzle. The pieces are vanishing right
Speaker 2: as the forensic team is trying to put it together.
Speaker 1: Clever but unsettling. Makes you think strong security from the
Speaker 1: start is just so crucial.
Speaker 2: Absolutely, prevention is key. But sc or GTFO doesn't shy
Speaker 2: away from offensive techniques either. It dives deep into how
Speaker 2: hackers exploit these systems. Take elf files for example.
Speaker 1: Elf files remind me those.
Speaker 2: Are executable and linkable format files, essentially instructions for your computer.
Speaker 2: But hackers can manipulate the metadata within these files, tiny
Speaker 2: details most people would overlook to hide malicious code.
Speaker 1: So it's like slipping a secret message in the margins
Speaker 1: of a document.
Speaker 2: Great analogy, and when that file is executed, the hidden
Speaker 2: code springs into action.
Speaker 1: Makes you wonder how many files out there that seem
Speaker 1: harmless could be harboring malicious code.
Speaker 2: It really shows the hackers creativity and deep understanding of
Speaker 2: these file formats. Another example is the ifunc mechanism in libic,
Speaker 2: which is this fundamental library that many systems use.
Speaker 1: I'm not familiar with lip could be honest, what is it?
Speaker 2: So libtct think of it like a toolbox full of
Speaker 2: essential functions that programs use for everyday tasks, you know,
Speaker 2: things like printing to the screen or reading files, and
Speaker 2: this ifunc mechanism it lets you swap out these functions
Speaker 2: while things are running, like switching tools mid task. But
Speaker 2: hackers can hijack this mechanism to execute their own instead
Speaker 2: of the intended functions.
Speaker 1: So it's like in the middle of building a bookshelf,
Speaker 1: you reach for a screwdriver, but get a hammer, throws everything.
Speaker 2: Off, exactly subverting the existing functionalities for malicious purposes. You know,
Speaker 2: one story that grabbed my attention was this gold ATM hack.
Speaker 2: Sounds like a heist movie.
Speaker 1: Okay, yeah, So.
Speaker 2: A group of hackers they're given permission to hack a
Speaker 2: gold plated ATM designed with top notch security, both in
Speaker 2: terms of software and the physical defenses.
Speaker 1: Sounds impenetrable.
Speaker 2: But here's where it gets interesting. They bypassed all the
Speaker 2: software completely. They focus on the physical. Found a weakness
Speaker 2: at the back, a jumble of cables, exploited that to
Speaker 2: gain access.
Speaker 1: So software vulnerability just bypassed everything fancy by going for
Speaker 1: the physical hardware.
Speaker 2: Sometimes the simplest approach is the most effective, and it
Speaker 2: makes you realize security has many facets. Can't just focus
Speaker 2: on software. You need to consider the physical stuff too.
Speaker 2: It ties into the next concept, the illusion of a
Speaker 2: single computer.
Speaker 1: What do they mean by that? Aren't computers single units?
Speaker 2: We tend to think of a computer as one thing,
Speaker 2: but it's more like an ecosystem of connected components cpu cores,
Speaker 2: memory buses. You've got expansion buses, storage, networking, interrupts. All
Speaker 2: interacting in Each component could have its own vulnerabilities.
Speaker 1: Like thinking of a city as one building when it's
Speaker 1: really a network of systems, each with its own weak points.
Speaker 2: That's a good way to picture it, and it raises
Speaker 2: a question, how do you secure something so complex? Post
Speaker 2: c or GTFO explores this with the idea of a
Speaker 2: b Butlerian typewriter.
Speaker 1: Okay, that sounds interesting. What's a Butlerian typewriter?
Speaker 2: Well, think of it as a thought experiment. Imagine a
Speaker 2: device that can't store data or connect to anything. A
Speaker 2: typewriter physically incapable of.
Speaker 1: Being hacked completely offline, no saving information makes sense for privacy,
Speaker 1: But wouldn't that limit what it can do exactly?
Speaker 2: It forces us to think about the trade offs security, functionality,
Speaker 2: our reliance on digital connection. Could we create something immune
Speaker 2: to data breaches? What would we have to give?
Speaker 1: Thought provoking for sure? Now for something a bit more,
Speaker 1: let's say alarming burning a phone with software? How is
Speaker 1: that possible? Software can't physically damage hardware? Can it?
Speaker 2: Unsettling?
Speaker 1: Isn't it?
Speaker 2: Software can manipulate a phone's power regulation battery charging. Push
Speaker 2: those systems too far and you can actually damage the circuitry,
Speaker 2: like overloading a circuit causing it to fry.
Speaker 1: So lines of code can fry of phones insights.
Speaker 2: It highlights that software can have physical consequences, or a
Speaker 2: reminder that we often take technology for granted without understanding
Speaker 2: the complexities.
Speaker 1: It's being a basics. The book had a section on basic.
Speaker 1: Isn't that outdated?
Speaker 2: It might seem like a relic, but basic is relevant
Speaker 2: to security and hacking. The simplicity forces you to grasp
Speaker 2: programming fundamentals, which is key for reverse engineering. Think of
Speaker 2: it as the alphabet of computers. Learn the alphabet you
Speaker 2: can read, understand more complex code, and that's how you
Speaker 2: spot vulnerabilities, how you figure out how systems work.
Speaker 1: So master the fundamentals before tackling the complex stuff. Learned
Speaker 1: to walk before you can run.
Speaker 2: Precisely, Sometimes the most effective solutions are rooted in simplicity.
Speaker 1: Okay, last, but not least, let's talk about polyglots, like
Speaker 1: something out of a spy.
Speaker 2: Novel, files that can be interpreted as different file types.
Speaker 2: A digital master of disguise might look like a harmless
Speaker 2: JPEG image, but it could also contain hidden code that
Speaker 2: executes when open with a different program.
Speaker 1: It's a chameleon blending in and then bam reveals its
Speaker 1: true nature.
Speaker 2: The book dives into specific examples like JPEG, PDFPNG polyglots.
Speaker 2: A single file masquerading as three different types.
Speaker 1: Hold on one file can trick three different programs.
Speaker 2: Yes, and that ability to deceive is what makes them dangerous.
Speaker 2: They slip past security filters, trick users into executing malicious
Speaker 2: code without realizing it.
Speaker 1: Ingenius and terrifying. Never take anything for granted in the
Speaker 1: digital world.
Speaker 2: A key takeaway from PAC or GTFO. The digital world
Speaker 2: is full of hidden complexities, and we need to be
Speaker 2: questioning how things work.
Speaker 1: Always Well my mind is I think I need a
Speaker 1: moment to process all this before we dive into the
Speaker 1: next batch of exploits.
Speaker 2: Take your time, we'll pick up where we left off
Speaker 2: next time, exploring even more fascinating and sometimes unsettling concepts
Speaker 2: from post C or GTFO. Welcome back. Ready to go
Speaker 2: deeper with post C or GTFO.
Speaker 1: Absolutely still thinking about those polyglots, digital chameleons blending right.
Speaker 2: In really highlight how deceptive these threats can be. Speaking
Speaker 2: of deception, let's talk about random number generators or RNGs.
Speaker 1: Rng's I know they generate random numbers, but how are
Speaker 1: they a security risk?
Speaker 2: Well, in the digital world, true randomness is hard to achieve.
Speaker 2: Most RNGs use algorithms to make numbers seem random, but
Speaker 2: if a hacker figures out.
Speaker 1: That algorithm, you can predict the.
Speaker 2: Numbers exactly, and that can be bad for security encryption keys.
Speaker 2: For example, if they're generated with a predictable RNG, a
Speaker 2: hacker could crack the encryption.
Speaker 1: That's scary, like playing cards when your opponent knows what's
Speaker 1: in your hand.
Speaker 2: The book actually talks about a vulnerability, and a simplified
Speaker 2: version of the Dacoran RNG shows how a small flaw
Speaker 2: can be exploited.
Speaker 1: Not just theoretical. Then this happens in the real world.
Speaker 2: Imagine an online gambling site using a predictable RNG. A
Speaker 2: hacker who cracks it could predict the outcome of poker
Speaker 2: roulette unfair advantage, so they could rig the system exactly.
Speaker 2: Shows how these abstract math concepts have real consequences in
Speaker 2: the digital world.
Speaker 1: So should we be skeptical of anything claiming to be random.
Speaker 2: A little skepticism is always good. True randomness is tricky,
Speaker 2: and computing any flaw in an RNG potential security nightmare.
Speaker 1: Okay, moving on from random numbers, the kosher phone concept
Speaker 1: that was interesting.
Speaker 2: It is an intriguing idea. Modify a phone's firmware, remove
Speaker 2: features some communities consider inappropriate, distracting, social media apps, games,
Speaker 2: certain types of Internet access.
Speaker 1: A curated digital environment tailor to specific values.
Speaker 2: Exactly using technology that aligns with your beliefs and priorities.
Speaker 1: But how do they modify the firmware sounds technically challenging.
Speaker 2: The book describes how someone figured out the encryption on
Speaker 2: a Nokia twenty seven to twenty phone, which allowed them
Speaker 2: to change the firmware bypass restrictions.
Speaker 1: Wait, they cracked the encryption. That's complex.
Speaker 2: It takes a deep understanding of the phones software and hardware,
Speaker 2: for sure, but it shows even secure firmware can be
Speaker 2: modified if you know what you're doing.
Speaker 1: So even with these kosher phones, there's still control, just
Speaker 1: by a different party. It reminds you that technology is
Speaker 1: rarely neutral. There are always choices about what's allowed and
Speaker 1: what's not.
Speaker 2: That's a really sharp observation. It raises questions about who
Speaker 2: gets to decide what we can do with our devices.
Speaker 1: Okay, ready for something fun. The Tetris game that's also
Speaker 1: a boot sector that was in the book.
Speaker 2: Oh yeah, classic example of creativity in the hacking community.
Speaker 2: They fit a whole Tetris game into the five hundred
Speaker 2: and twelve bytes of a boot sector.
Speaker 1: Wait, you can play Tetris while your computer boots up.
Speaker 2: Amazing more than a trick, though, It shows you can
Speaker 2: push the limits of code. Even the smallest environments can
Speaker 2: be used for something unexpected, delightful.
Speaker 1: Limitations sparking creativity.
Speaker 2: Exactly, and that spirit is all over pt or GTFO exploring, experimenting,
Speaker 2: challenging how we think.
Speaker 1: Okay, this one's a bit more head scratching, exploiting affuses
Speaker 1: with Unicode. Not even sure where to start with that.
Speaker 2: Let's break it down. Effuses they're like tiny fuses inside
Speaker 2: a device, permanently programmed with settings, often for security.
Speaker 1: So once they're set, there's no changing.
Speaker 2: Them, right, like tiny switches you can only flip once.
Speaker 2: But here's the thing. Some programs use a special comment
Speaker 2: in their code to declare the files encoding as UTF
Speaker 2: eight UTF.
Speaker 1: Eight that's for Unicode characters. But how does that relate
Speaker 1: to effuses.
Speaker 2: While the book says some programs misread these comments, it
Speaker 2: can cause them to read data from affuses. They shouldn't
Speaker 2: be able to.
Speaker 1: Access a hidden back door created by a misunderstanding.
Speaker 2: Of the code precisely shows the danger of assuming how
Speaker 2: software should act. Even something like a comment about character
Speaker 2: encoding can have unexpected security issues.
Speaker 1: Hackers find these vulnerabilities in the most unexpected places amazing.
Speaker 2: That's what makes PPC or GTFOL so valuable. Exposes these
Speaker 2: complexities makes us think critically about the systems we rely on,
Speaker 2: question our assumptions.
Speaker 1: This is changing how I think about cybersecurity. It's not
Speaker 1: just firewalls, antivirus, it's understanding how these systems work on
Speaker 1: a deeper level.
Speaker 2: Exactly. The more you understand, the better you can protect yourself.
Speaker 1: Speaking of protection and encryption, that sounded like something from
Speaker 1: a magic show.
Speaker 2: Pretty clever technique. A file that, when you encrypt it
Speaker 2: with one algorithm becomes a different file type.
Speaker 1: So encrypted jpeg, it becomes a PDF. Digital alchemy.
Speaker 2: Great way to put it. Manipulating fileheaders, data structures, exploiting
Speaker 2: how different file formats are parsed like a chameleon, changing
Speaker 2: colors to blend.
Speaker 1: In a file that adapts depending on how it's viewed.
Speaker 2: Exactly, not limited to two file types either. The authors
Speaker 2: make a file that can be a jpeg, a PDF,
Speaker 2: even a PE executable, a Windows program.
Speaker 1: File, one file, three different things. That's impressive, scary.
Speaker 2: It's a powerful technique that shows how deceptive cybersecurity threats
Speaker 2: can be, and it underlines the importance of understanding file
Speaker 2: formats how they can be manipulated.
Speaker 1: Okay, my mind is officially blown. Anything else that'll keep
Speaker 1: me up at night?
Speaker 2: How about netwatch, a proof of concept tool lets you
Speaker 2: debug a computer from outside its operating system.
Speaker 1: You mean, controlling a computer without being logged in?
Speaker 2: Basically, yeah, exploits a future called System management Mode or SMM.
Speaker 1: SMM not familiar.
Speaker 2: That it's a special mode in most modern computers, runs
Speaker 2: in the background, separate from the main OS handles things
Speaker 2: like power, system security, a.
Speaker 1: Hidden operating system alongside the main one good.
Speaker 2: Way to think about it. And because SMM is so
Speaker 2: low level, often undocumented, it's a target for hackers. Netwatch
Speaker 2: lets someone tap into this, observe, even manipulate the system.
Speaker 2: Really deep level stuff.
Speaker 1: A secret backdoor right into the computer's.
Speaker 2: Heart exactly, and it highlights the complexity in our systems,
Speaker 2: the potential for exploitation we might not even know about.
Speaker 1: It's a rabbit hole the more we dig, the more
Speaker 1: we find.
Speaker 2: That's the beauty and the challenge of cybersecurity. Always more
Speaker 2: to learn, threats, always evolving, but understanding the basics, staying curious,
Speaker 2: that's how we protect ourselves and the systems we rely on.
Speaker 1: Speaking of basics, what about a H two point one
Speaker 1: point five point four. I know that's wireless stuff like zigbe,
Speaker 1: but what are the security implications?
Speaker 2: POUSE or GTFO looks at a technique called packet and
Speaker 2: packet PIP. It can bypass security on these networks packet.
Speaker 1: And packet, hiding one message inside another.
Speaker 2: Great analogy. It's putting data within other data packets. Security
Speaker 2: filters often miss this, so it can be used to
Speaker 2: sneak bad code or data onto a network like a.
Speaker 1: Trojan horse, sneaking past defenses.
Speaker 2: The book even shows how to make PIP attacks even
Speaker 2: harder to detect, misaligning the symbols within the packets.
Speaker 1: Misaligning symbols sounds like next level hacking.
Speaker 2: It's understanding the details of the protocol exploit nuances most
Speaker 2: people wouldn't even think about.
Speaker 1: There's a pattern here. Hacking is as much about creativity,
Speaker 1: thinking outside the box as it is technical skills.
Speaker 2: Absolutely, it's about challenging assumptions, experimenting, pushing the limits.
Speaker 1: Well, this part of the deep dive has been a
Speaker 1: lot to take in. I need a minute to process
Speaker 1: at all before we get to the final exploits from
Speaker 1: payog or GTFO.
Speaker 2: Take your time. We'll be back soon to wrap up
Speaker 2: this journey into the world of hacking and cybersecurity.
Speaker 1: Welcome back, final part of our deep dive into payo
Speaker 1: or GTFO. This book has really really opened my eyes
Speaker 1: to like the hidden stuff, vulnerabilities in the technology we
Speaker 1: use every day.
Speaker 2: Yeah, it's been a wild ride for sure through this
Speaker 2: whole world of hacking and cybersecurity.
Speaker 1: So, last leg of the journey. What mind bending exploits
Speaker 1: do you have for me?
Speaker 2: Let's start with something called an aldy rand backdoor r
Speaker 2: D rand.
Speaker 1: That sounds familiar, something to do with random number generation
Speaker 1: on Intel CPUs good memory.
Speaker 2: It's an instruction on newer Intel processors suppose to give
Speaker 2: you these high quality random numbers, really important for encryption.
Speaker 1: Okay, so where's the backdoor part coming.
Speaker 2: Well, the book describes as technique manipulating the box.
Speaker 1: Emulator box emulator. I don't know that.
Speaker 2: One it's software lets you simulate computer hardware, like creating
Speaker 2: a virtual computer inside your computer. The author they were
Speaker 2: able to tweak box to make a back door that
Speaker 2: leaks data through rd.
Speaker 1: Rand, So it's not truly random. It's being manipulated to
Speaker 1: give out specific data.
Speaker 2: You got it, And because it's at the hardware level,
Speaker 2: it'd be super hard to detect, like whispering a secret
Speaker 2: message within random noise.
Speaker 1: That's both ingenious and terrifying, like a secret message hidden
Speaker 1: in plain sight, but on a tiny level.
Speaker 2: The author even goes further, suggests a generic by eighty
Speaker 2: six back door that could be almost impossible to.
Speaker 1: Detect, undetectable.
Speaker 2: How it's exploiting, like the deep complexities of BY eighty
Speaker 2: six architecture, those little things that allow for manipulation without
Speaker 2: setting off any alarms. It's like ah, a ghost in
Speaker 2: the machine, leaves no trace.
Speaker 1: Starting to feel like there's nowhere safe in the digital world.
Speaker 1: If even the hardware can be messed with, Where do
Speaker 1: we draw the line.
Speaker 2: It's not about despare it's about awareness. POC or GTFO
Speaker 2: wants to give us knowledge, not scare us. The more
Speaker 2: we understand these vulnerabilities, the better we can handle them.
Speaker 1: Knowledge is power, right, The more we know, the better
Speaker 1: we can protect.
Speaker 2: Ourselves exactly, and sometimes that knowledge is surprising. Like there's
Speaker 2: this article about a breakout board for many PCIe many.
Speaker 1: PCIe that's for connecting network cars, hard drives, that kind
Speaker 1: of stuff, right.
Speaker 2: Right, the author they show you how to make a
Speaker 2: breakout board that lets you connect a mini PCIe device
Speaker 2: to a USB port.
Speaker 1: Okay, but why is that a security thing?
Speaker 2: Think about it. You can now control PCIe devices, which
Speaker 2: are usually only accessible inside the computer from an external device.
Speaker 1: So you could get into a computer's hard drive network
Speaker 1: card from outside the system.
Speaker 2: That's the point. It creates all these new ways to
Speaker 2: exploit things. The author even shows how to use this
Speaker 2: to run Linux on an Intel Galilee board, which wasn't
Speaker 2: designed for that.
Speaker 1: So it's about like bending the rules of hardware, making
Speaker 1: it do things it wasn't.
Speaker 2: Meant to, exactly, pushing the boundaries of what technology can do.
Speaker 2: Sometimes that means blurring the lines between how it's supposed
Speaker 2: to be used and creative misuse.
Speaker 1: Speaking of blurring lines, booting pac or GTFO from a
Speaker 1: Cisco Blade server, that's a bold move.
Speaker 2: It shows how vulnerable. These remote management interfaces can be
Speaker 2: the author. They used a security flaw in Cisco system
Speaker 2: to boot the book from a Blade server, basically turn
Speaker 2: this high end server into a platform for hacking tools.
Speaker 1: Like hijacking a fortress and using its own weapons against it.
Speaker 2: Powerful analogy. It shows that even these big systems supposedly secure,
Speaker 2: have weaknesses. Can't get complacent with cybersecurity.
Speaker 1: No system is perfect, that's for sure.
Speaker 2: Now let's switch gears a bit Return oriented programming or
Speaker 2: ROP ROP.
Speaker 1: That sounds intense, What is it.
Speaker 2: Imagine you want to build a house, but you only
Speaker 2: have pre built rooms. ROP is like arranging those rooms
Speaker 2: in a clever way to create a new.
Speaker 1: Structure, repurposing existing stuff instead of building from scratch.
Speaker 2: Exactly, ROP makes malicious code by chaining together these little
Speaker 2: bits of existing code, code that's already in the system,
Speaker 2: harmless on their own, but arrange them carefully, you can
Speaker 2: execute any code you want.
Speaker 1: Putting together a puzzle where the pieces are good code
Speaker 1: but the final picture is bad.
Speaker 2: Great way to think about it. And because the pieces
Speaker 2: are legitimate, ROP attacks can sneak past security systems looking
Speaker 2: for normal code injections.
Speaker 1: Was a stealthy way to get in, hiding right there
Speaker 1: in plain sight.
Speaker 2: The book shows you how rop can exploit a vulnerability
Speaker 2: in a web browser, real world stuff.
Speaker 1: So that's how they get in. But how do they
Speaker 1: stay hidden once they're inside? Don't systems have ways to
Speaker 1: detect intruders?
Speaker 2: Right? They use things like canaries.
Speaker 1: Canaries like the birds they used in coal.
Speaker 2: Mines, exactly. In cybersecurity, canaries are special values. They're put
Speaker 2: on the stack to detect buffer overflows.
Speaker 1: Stack buffer overflows. Now I'm getting lost.
Speaker 2: Think of the stack like a pile of plates buffer
Speaker 2: overflows adding too many plates the pile falls over. Canaries
Speaker 2: are a warning telling the system if someone's messing at the.
Speaker 1: Stack, the trip wire setting off an alarm.
Speaker 2: Great analogy, but poh A Nisi or GTFO describes how
Speaker 2: attackers can actually disable these canaries. They use special instructions
Speaker 2: in their shell code, the malicious code.
Speaker 1: They inject, so they disarm the alarm before breaking in.
Speaker 2: Exactly, it's this constant back and forth, attackers and defenders,
Speaker 2: always trying to outsmart each other.
Speaker 1: Security is never finished, it's always changing, adapting.
Speaker 2: Now ready for a dive into the world of Jason P.
Speaker 1: And Rosetta Flash honestly never heard of them. Explain it like,
Speaker 1: I'm five.
Speaker 2: Okay, Jason p it stands for Jason with padding. It's
Speaker 2: a way to get data from a different domain, something
Speaker 2: usually blocked for security, like trying to borrow a book
Speaker 2: from a library that's not in your network. And Risetta
Speaker 2: Flash that's a tool lets you create flash files that
Speaker 2: work with old versions of Flash Player, like translating an
Speaker 2: a text into a language we use today.
Speaker 1: Okay, but how are those two things abused?
Speaker 2: Hackers can use them together to bypass restrictions steal data
Speaker 2: from websites, like using a secret backdoor to get into
Speaker 2: a restricted area.
Speaker 1: So it's a loophole combining two things that seem harmless on.
Speaker 2: Their own exactly, and it shows why updates are important.
Speaker 2: Old technology often has vulnerabilities.
Speaker 1: Even in the digital world, things can get old and
Speaker 1: need fixing up.
Speaker 2: Speaking of manipulation, heard of colliding jpeg files.
Speaker 1: Colliding JPEGs sounds messy. It's making two jpeg files that
Speaker 1: have the same hash value cash value.
Speaker 2: Remind me, it's like a digital fingerprint unique to each file,
Speaker 2: an ID. By making colliding JPEGs, hackers trick systems, they
Speaker 2: accept a bad file disguised as a good one.
Speaker 1: Fake ID that gets past security perfect analogy.
Speaker 2: The book explains how to do this using weaknesses in
Speaker 2: how JPEGs are compressed.
Speaker 1: So much going on beneath the surface of a simple jpeg.
Speaker 2: That's the whole point of post c or GTFO. It's
Speaker 2: about looking deeper into technology, nderstanding the little details that
Speaker 2: can be used for good or for bad.
Speaker 1: This deep dive has been eye opening and a little scary.
Speaker 1: Makes you realize how much we just trust the tech
Speaker 1: we use.
Speaker 2: But realizing that is the first step to being safer online. Remember,
Speaker 2: the more you understand, the better you can protect yourself.
Speaker 1: I definitely feel more informed, even if it means I'll
Speaker 1: be a little more cautious online.
Speaker 2: Now, being a little cautious online is always a good thing.
Speaker 2: Stay curious, stay vigilant, keep learning. That's what putc or
Speaker 2: GTFO is all about, and.
Speaker 1: That's what the deep dive is all about. Thanks for
Speaker 1: joining us on this exploration. Until next time, Stay safe
Speaker 1: out there.