文字稿 🔗
WEBVTT
00:00:00.239 --> 00:00:01.280
Yo, yo, yo.
00:00:01.679 --> 00:00:02.640
How are you?
00:00:03.120 --> 00:00:03.520
Good.
00:00:03.680 --> 00:00:04.160
How are you?
00:00:04.400 --> 00:00:04.799
I'm good.
00:00:04.879 --> 00:00:05.599
It's great to meet you.
00:00:05.679 --> 00:00:06.959
I appreciate you joining.
00:00:07.280 --> 00:00:09.439
Yes, I'm super happy to be here.
00:00:09.519 --> 00:00:11.839
Although it is like 7 a.m.
00:00:12.240 --> 00:00:14.240
for me, which is, you know, kind of.
00:00:14.720 --> 00:00:15.119
You're the goat.
00:00:15.359 --> 00:00:16.000
Thank you for joining.
00:00:16.719 --> 00:00:17.359
Yeah, you're the goat.
00:00:17.519 --> 00:00:18.000
Thanks for doing it.
00:00:18.160 --> 00:00:19.440
It's kind of a crazy day today.
00:00:19.519 --> 00:00:19.760
Okay.
00:00:19.920 --> 00:00:20.800
I appreciate you being here.
00:00:20.879 --> 00:00:22.480
I wasn't sure who you're gonna have on.
00:00:22.719 --> 00:00:30.239
And usually I could do pretty well with topics that are out of my scope, but this one is like particular cyber as a whole, it's just particularly out of my scope.
00:00:30.399 --> 00:00:32.560
And so you have a lot of people that love you, by the way.
00:00:32.719 --> 00:00:35.920
Like crazy, uh, please get her on, please get her on, please get her on.
00:00:36.079 --> 00:00:37.759
And I've heard you on some podcasts before.
00:00:37.920 --> 00:00:53.679
So um, I guess can you help us and set the stage on how severe are the events of the last I don't know, 48 hours, PHP, but more importantly, like how was this able to happen?
00:00:53.840 --> 00:00:54.560
Why now?
00:00:54.719 --> 00:00:55.439
How severe?
00:00:55.600 --> 00:00:56.479
Are you terrified?
00:00:56.640 --> 00:00:58.399
Like, get yeah, I don't know.
00:00:58.640 --> 00:01:00.399
Whisper some some sweet nothings to us.
00:01:00.479 --> 00:01:02.000
How how how do you feel?
00:01:02.320 --> 00:01:07.599
Okay, so it's been it's been wild, it's been actually insane.
00:01:07.760 --> 00:01:20.640
So if people are out there and like reading Twitter and are scared, it's that's I think a legitimate feeling right now because there's like it just feels like a deluge of things blowing up in our faces.
00:01:20.959 --> 00:01:24.000
Um I think we can kind of temper that.
00:01:24.159 --> 00:01:29.599
If you're like a normal person, you're probably gonna be okay.
00:01:29.840 --> 00:01:40.319
If you're running servers doing DevOps, you probably want to pay more attention just because this stuff is affecting you more and more.
00:01:40.640 --> 00:01:53.599
Um, but most of the panic and running around that's happening right now is the it's like the fruits of people coordinating so that end users don't have to do anything, right?
00:01:54.159 --> 00:02:11.919
And that's it's it's panicky and it's loud and it's sometimes quite obnoxious and it's always terrifying, but it's because that's what it takes to get um, I don't know, millions, billions of people protected essentially overnight when like a new zero day drops or whatever.
00:02:12.400 --> 00:02:15.280
So hopefully that helps a little bit.
00:02:15.520 --> 00:02:17.759
What is how tech go ahead, sorry.
00:02:17.919 --> 00:02:21.199
No, go no, I mean, I was just gonna say how technical is your audience?
00:02:21.280 --> 00:02:22.560
How how deep do we want to go on this?
00:02:22.719 --> 00:02:27.840
We're high level, but I uh, you know, we we we we frequently bring on some very sharp people.
00:02:27.919 --> 00:02:33.520
So I asked the dumb questions, they say the smart stuff, and we land somewhere in the middle, is is how I think this usually goes.
00:02:33.680 --> 00:02:43.599
Can you explain like what PHP was and what exactly was exploited over the last couple days here?
00:02:44.400 --> 00:02:44.879
Yeah, yeah.
00:02:44.960 --> 00:02:50.400
So PHP is a programming language, so um, like Solidity is a programming language as well.
00:02:50.479 --> 00:02:52.479
It's like the language that you write the stuff in.
00:02:52.719 --> 00:02:57.199
It's PHP is a very old programming language and it allows you to do things.
00:02:57.520 --> 00:03:04.000
So um it's not just like CSS or JavaScript where it sort of like lives in a certain place.
00:03:04.159 --> 00:03:06.800
PHP tends to live literally everywhere.
00:03:07.360 --> 00:03:09.840
Um, and it's so old.
00:03:10.000 --> 00:03:19.919
So PHP was when I started when I built my first website, which is like two decades ago, PHP was already old then, to give you like an idea.
00:03:20.159 --> 00:03:24.719
Um, it was most popular like early 2000s, late 2000s, 2010s.
00:03:25.199 --> 00:03:37.520
Um, every WordPress site is PHP, like e-commerce sites, blogger sites, like everything that's not basically built in the last few years is probably PHP.
00:03:37.680 --> 00:03:46.240
Um, I think estimates still are at like 70% of websites and and backends are like built on PHP.
00:03:46.479 --> 00:03:50.319
So it's just like a massive scope, right?
00:03:50.400 --> 00:03:55.360
Like the the the amount of things that are written in PHP is insane.
00:03:55.520 --> 00:04:14.960
And so what happened was that some researchers uh got together, really smart, insanely smart people got together um with the new AI models and basically went to town and they had history and knew a lot about PHP, they knew the right questions to ask, they knew how to prompt.
00:04:15.599 --> 00:04:26.079
Um, and they were able to find not one but two RCEs, which is remote code execution, it means that anyone means that anyone can hack you remotely.
00:04:26.160 --> 00:04:28.480
It's like the worst type of hacking, right?
00:04:29.279 --> 00:04:34.959
So what that means is like if you have um like a WordPress site, right?
00:04:35.040 --> 00:04:47.839
Or maybe your mom has a WordPress site there somewhere, like a travel blog or a Pilates blog or whatever it is, what it means is that like a hacker could just like come along, see
Load full transcript
that, um, and then just hack it remotely.
00:04:48.399 --> 00:04:51.279
And you couldn't do anything about it.
00:04:51.439 --> 00:05:10.639
And so that's why the patch is so critically important, is so that uh, you know, we can't have we can't have people just running around hacking all of our infrastructure, all of our websites, whether that's a travel blog or like unfortunately, a lot of government websites, a lot of banking websites, fintech stuff also runs on PHP.
00:05:10.959 --> 00:05:18.399
Can you sort of explain, like of the sort of outbreak and fear we saw yesterday?
00:05:18.639 --> 00:05:26.480
How much of it is for exploits that were already found, and then how much of it is extrapolating forward?
00:05:26.639 --> 00:05:35.600
Oh shit, if they were able to do this, the implications are so much worse of what could happen like how much of it is future looking versus what's currently the case today.
00:05:36.079 --> 00:05:42.480
I think every time we have one of these, and especially with like the PHP one, this bug existed in the PHP.
00:05:42.639 --> 00:05:46.720
This vulnerability exists in the PHP since I think say 2004.
00:05:47.199 --> 00:05:47.439
Whoa.
00:05:47.680 --> 00:05:56.639
So this bug this vulnerability is probably older than some of your viewers, which is I mean, I was two, so yeah, exactly.
00:06:00.079 --> 00:06:20.399
Uh so I think it's just like it's very, it's very eye-opening and it's very scary to realize that um the AI, and especially like properly harnessed AI, can find things that like we're getting to the point where the AI is is almost smarter than the humans.
00:06:20.639 --> 00:06:26.639
And I think the fear, part of the fear is realizing that it is going to be smarter than the humans.
00:06:26.879 --> 00:06:28.879
We're not that far away from it.
00:06:29.199 --> 00:06:41.759
Um, and if our whole world is built on like these sort of janky tech stacks of PHP and you know, um the realization is that like, yeah, like that's that could be really, really bad.
00:06:42.000 --> 00:06:45.040
Um we're not really secure at all.
00:06:45.360 --> 00:06:52.160
I mean, how much of important stuff on the internet is built with these, like, like you said, janky sort of tech stacks?
00:06:52.240 --> 00:06:54.240
Like, is that just like the internet is sort of like this?
00:06:54.399 --> 00:06:54.720
Yeah.
00:06:54.959 --> 00:06:57.439
Turns out, guys, the internet is super janky and old.
00:06:57.759 --> 00:06:59.680
Basically everything, yeah.
00:06:59.839 --> 00:07:08.000
So the other thing that your viewers were probably aware of is this e-mudra certificate thing.
00:07:08.240 --> 00:07:08.800
No, I don't think.
00:07:08.959 --> 00:07:09.439
Did you hear about this?
00:07:09.600 --> 00:07:10.240
No, no, no, what is this?
00:07:10.480 --> 00:07:14.480
Okay, so this is the other thing that a lot of people were panicking about this week.
00:07:14.720 --> 00:07:19.600
It's basically the certificates that can that like make sure everything is secure and private on the internet.
00:07:20.480 --> 00:07:25.680
Um, these were issued by an Indian company, Indian company that like works with the Indian government.
00:07:26.000 --> 00:07:30.720
Certificates are um, it's actually it's very similar to crypto, right?
00:07:30.800 --> 00:07:49.199
You have a private key, you have a public key, you have these signing things that happen in a test, and it allows you to like put your credit card into a forum on a website, and it's encrypted and it goes up into the cloud and it goes to the other servers, but anyone that's in the middle or seeing your stuff, they can't actually see that that data, right?
00:07:49.439 --> 00:07:52.399
It's HTTPS, it's it's all that, right?
00:07:53.519 --> 00:08:05.360
Um, it turns out that turns out that the private key that this company was using, which everyone uses, um, was just the number four.
00:08:05.519 --> 00:08:10.480
So if you guys saw like the four memes, if you saw a bunch of security nerds making four memes, that's what it was.
00:08:10.959 --> 00:08:26.399
Again, this is like the underpinnings of the internet, it's like how the communication layer works, and I think again, this realization that our tech stacks are really quite janky, it's just oh my god, it's super eye-opening.
00:08:26.639 --> 00:08:33.440
Wait, that's I thought it was like um it was uh forgive me, I thought it was a CZ reference.
00:08:34.240 --> 00:08:39.919
I mean, it is because it's the number four, but it's also like, yeah, it's terrifying.
00:08:40.159 --> 00:08:46.799
It's literally, it's like if you created like an Ethereum or Bitcoin or a Solana private key, that's just the number four.
00:08:46.879 --> 00:08:48.000
Like that was your password.
00:08:48.159 --> 00:08:54.240
That's essentially what these guys did, but that's like for it's for the certificates for you know the whole internet.
00:08:54.720 --> 00:08:55.679
For the whole internet.
00:08:56.080 --> 00:09:01.840
That is well, so yeah, a lot of people, a lot of different people issue certificates, but they're one of the ones that's trusted.
00:09:02.080 --> 00:09:02.960
Holy shit.
00:09:03.200 --> 00:09:20.399
Okay, what's sort of surprising to me about this is like we've spent the last, I don't know, six months having siloed panic about exploits to crypto, and everyone is like crypto is uniquely the worst positioned.
00:09:20.559 --> 00:09:32.639
Everything in crypto is gonna get hacked, DeFi is gonna get destroyed, crypto is gonna lose, and we're sort of pretending like it's just silo to crypto, and then it feels like you're closer to it than I am over the last couple days.
00:09:32.720 --> 00:09:34.240
Now it's like okay, fuck crypto.
00:09:34.399 --> 00:09:35.840
We already got the big stuff in crypto.
00:09:36.000 --> 00:09:38.399
Crypto's actually fine or relatively fine.
00:09:38.639 --> 00:09:40.159
Now it's like the whole internet.
00:09:41.440 --> 00:09:48.799
Like, how is crypto in
like crypto-specific cryptography positioned relative to like everybody else on the internet?
00:09:49.519 --> 00:10:00.799
So I think one example of like just how much I guess better positioned crypto is is like with this four, this private key that was just the number four thing.
00:10:01.279 --> 00:10:08.960
Imagine if you use the private key with the number four or a password with the number four in crypto, it would be like instantly drained.
00:10:09.120 --> 00:10:12.799
Like you would be wrecked in in like not even a second, right?
00:10:13.039 --> 00:10:19.039
And there'd be like, honestly, there would be like 20 dudes running to get you, like within a second, right?
00:10:19.279 --> 00:10:24.559
Meanwhile, the certificate went completely unnoticed for like 16 months.
00:10:24.799 --> 00:10:28.320
It was just like nobody, like nobody noticed for the whole time.
00:10:28.639 --> 00:10:32.080
Um, and so I think that there's something to be said about crypto.
00:10:32.159 --> 00:10:37.919
Like, we've actually hardened um the infrastructure, the the things that we do.
00:10:38.080 --> 00:10:51.200
Like, we are naturally in a much more hardened position than perhaps some of these sort of like core internet things that nobody realizes exists um and might be super, super weak.
00:10:51.440 --> 00:10:58.559
Um, I also think we're just operationally um we're super used to being wrecked all the time.
00:10:58.720 --> 00:10:58.879
Yeah.
00:10:59.039 --> 00:11:00.240
Which I think this is a good take.
00:11:00.320 --> 00:11:03.600
It's just like perpetual attacking on all systems, right?
00:11:03.759 --> 00:11:04.159
Forever.
00:11:04.399 --> 00:11:04.639
Yeah.
00:11:04.799 --> 00:11:16.000
So one of the things I noticed with the PHP situation was like, you know, a lot of these guys are like really experienced, skilled, like DevOps guys who've been doing this for like a decade.
00:11:16.240 --> 00:11:22.639
They definitely probably know more than crypto people, but they're not nearly as agile.
00:11:22.799 --> 00:11:23.039
Whoa.
00:11:23.200 --> 00:11:27.840
Like this, like an explosion happens, and like the first thing they do is they like freak out.
00:11:28.000 --> 00:11:30.559
They're like, oh no, my sleep.
00:11:30.639 --> 00:11:31.919
What am I gonna do?
00:11:32.080 --> 00:11:35.759
Like, we need to schedule the patch release.
00:11:36.000 --> 00:11:45.919
Meanwhile, in crypto, it's like something blows up and like everyone kind of stares at it and is like, okay, let's, you know, what like run, go get our funds, turn off the system.
00:11:46.159 --> 00:11:46.720
You know what I mean?
00:11:47.039 --> 00:11:50.000
There's like a protocol for how we deal with this stuff, yeah.
00:11:50.159 --> 00:11:54.639
And it's not fun, but it's definitely it's not like the world is actually ending at this point, you know?
00:11:54.720 --> 00:11:57.759
It's like, oh, go revoke your approvals, go whatever it is.
00:11:57.919 --> 00:12:00.399
Yeah, there's like
standard, like we know how this works.
00:12:01.600 --> 00:12:04.159
So I think there's something to be said about that.
00:12:04.639 --> 00:12:07.840
Um, that's I like that take a lot.
00:12:08.080 --> 00:12:11.919
What about the fact that it's GPT 5.6 soul, like now?
00:12:12.000 --> 00:12:14.399
Or I guess it happened in August and it got leaked or whatever.
00:12:14.480 --> 00:12:19.440
It isn't like it's this crazy insider, like super mythos.
00:12:19.919 --> 00:12:25.039
Like it's sort of, I don't know, 5.6 soul was launched, it's good, but it didn't change the world.
00:12:25.200 --> 00:12:27.919
It's not like the craziest super intelligence that's ever been created.
00:12:28.000 --> 00:12:33.200
Like, what are your thoughts on the capabilities required to do what just happened?
00:12:33.519 --> 00:12:38.080
I think, I think that's probably the scariest thing is that because I didn't think soul was that good.
00:12:38.399 --> 00:12:39.039
Really?
00:12:39.679 --> 00:12:41.519
I haven't been using it much at all.
00:12:41.679 --> 00:12:46.720
I've actually been like quite bored for I haven't been touching my GPD at all lately.
00:12:46.879 --> 00:12:56.480
Um and like, yeah, it was back in, I guess, August, but still like uh it's a it's yeah, I wouldn't say it's like the best model.
00:12:56.639 --> 00:13:10.399
I I hope my assumption is that the humans in the loop here were the ones that sort of were able to like get the unique combination of knowledge and history and like point it really at the right place.
00:13:11.120 --> 00:13:16.720
Um I assume that's what happened, just because it is such a weird deep vulnerability.
00:13:16.879 --> 00:13:25.600
Um, but we don't know, and obviously, like I'm not convinced that the next model is gonna be um I mean, the next model is definitely not gonna be stupider.
00:13:25.759 --> 00:13:32.240
We can say that at some point it will be able to like point itself and do this without the human in the loop.
00:13:32.799 --> 00:13:47.039
You is there any way, like, is it is it the case that the offensive side, the hackers are just always gonna have like people like looking for exploits are always gonna have upper hand of people defending future vulnerabilities and patches?
00:13:47.120 --> 00:13:50.320
Like, are we just gonna be playing cat and mouse for the inevitable future here?
00:13:50.399 --> 00:13:54.399
Like, is it every day there's some new panic that was found?
00:13:55.120 --> 00:13:57.440
I hope not every day, truly.
00:13:57.600 --> 00:14:00.159
Like, it's been crazy the last few days.
00:14:00.480 --> 00:14:09.679
I think that so there will be an equilibrium similar to like we've seen in crypto, but we've also seen in the real world.
00:14:09.840 --> 00:14:13.200
We are just in a period of like enormous shift right now.
00:14:13.440 --> 00:14:17.360
Um eventually there will be an equilibrium, right?
00:14:17.600 --> 00:14:22.879
The the new code that people write will be way more secure, people will secure their old code.
00:14:23.120 --> 00:14:30.720
I think we'll see a lot of people um just choosing to like rewrite old code bases or old products, right?
00:14:30.960 --> 00:14:32.879
Because the AI can just do it for you.
00:14:32.960 --> 00:14:39.200
You don't have to necessarily invest like billions of dollars to write this old portal, which used to be a thing, by the way.
00:14:39.360 --> 00:14:47.519
Like the reason banks will draw out on these antiquated systems is like it's a huge cost to create the like create a new secure system.
00:14:47.840 --> 00:14:49.759
And they have their real incentive to do it, right?
00:14:50.080 --> 00:14:50.960
Yeah, exactly.
00:14:51.120 --> 00:14:52.799
And so it's like, why turn it off?
00:14:52.879 --> 00:14:53.840
Why change it?
00:14:54.000 --> 00:15:05.759
Um, but I think with AI, like you know, the AI is is quite good at coding, so that's one thing that will change is the AI will get better at writing really secure code at finding the vulnerabilities for defenders.
00:15:06.000 --> 00:15:11.440
Um I think for the next I don't know, a couple years probably.
00:15:11.679 --> 00:15:21.679
Fuck it's gonna be, I think it's probably you're gonna see these like pockets of just like deluge where it feels like the the sky is literally falling.
00:15:21.919 --> 00:15:24.000
Um but we'll see.
00:15:24.159 --> 00:15:24.480
We'll see.
00:15:24.879 --> 00:15:27.279
I think we'll also we'll we have to get better at reacting.
00:15:27.360 --> 00:15:28.000
I will say that.
00:15:28.159 --> 00:15:31.200
Like we must, we must improve the reaction.
00:15:31.440 --> 00:15:34.080
What is the sign that the sky is actually falling?
00:15:34.240 --> 00:15:40.879
Like if X thing falls or X exploit is hit, I you should actually freak the fuck out and panic.
00:15:41.679 --> 00:15:48.159
Um so honestly, you probably like shouldn't ever panic.
00:15:48.320 --> 00:15:50.240
It's usually worse to panic.
00:15:50.639 --> 00:15:53.519
Um if you're in crypto, you probably know this, right?
00:15:53.759 --> 00:15:58.080
Like when the market starts like to crash, of course, don't go catch the falling knife.
00:15:58.240 --> 00:15:59.440
But it's the same with security.
00:15:59.519 --> 00:16:02.080
Like if you panic, it usually it usually gets worse.
00:16:02.320 --> 00:16:10.240
Um, I will say that I think that like the best advice I have for folks is um when you're not in a panic state.
00:16:10.399 --> 00:16:16.320
So when you're like in a controlled, calm state, think about all the different assets that you have.
00:16:16.480 --> 00:16:20.159
Think about all the different things that you have in your life that you value.
00:16:20.320 --> 00:16:26.639
Um, whether that's like your crypto, whether that's your investments, whether that's like certain accounts on your computer.
00:16:27.039 --> 00:16:35.440
Um, and think about how you can like secure those, but also how you can maybe diversify those to be secured by
different methods.
00:16:35.840 --> 00:16:40.159
Because we are getting to a point where there is just like so much happening.
00:16:40.320 --> 00:16:45.279
You don't want to get hacked and have your entire net worth wiped out, say, right?
00:16:45.519 --> 00:16:54.879
It's better to diversify so that only like one egg in one basket gets wrecked rather than all of the eggs in the one basket.
00:16:55.120 --> 00:17:03.840
So spread things out, use different wallets, use cold storage, you know, those sorts of things I think are like will give people a lot of peace of mind.
00:17:04.240 --> 00:17:07.279
I don't know how much you know about these like public cybersecurity companies.
00:17:07.440 --> 00:17:09.680
I don't really know that much, but I know the big names.
00:17:10.000 --> 00:17:15.119
Are any of them specifically like uniquely positioned to have the biggest impact?
00:17:15.279 --> 00:17:22.480
Like Cloudflare or something like this, like who is the most important in the way the ha uh the exploiting is going?
00:17:23.440 --> 00:17:36.319
Um, so Cloudflare is actually a really good example of a company that's not necessarily a security company, but it has stepped up numerous times over the past years to basically secure the entire internet.
00:17:36.720 --> 00:17:44.960
Um, like one thing with the PHP, I don't know if you saw this, with the PHP incident, they basically changed the rule sets for all users proactively.
00:17:45.359 --> 00:18:04.640
So that if you have PHP on your server and you have Cloudflare in front of your PHP server, um instead of just doing basic like DDoS protection, it also looked very carefully for any like um any requests that were coming in that were gonna try to hack your PHP and just block them.
00:18:04.880 --> 00:18:08.079
So it's sort of like you know the meme with the shield and the arrows?
00:18:08.160 --> 00:18:10.079
Yeah, Cloudflare was like literally doing that.
00:18:11.039 --> 00:18:17.119
Yeah, for all you all their users, even their free tier, they were like, We're not like the hackers aren't gonna win this one.
00:18:17.359 --> 00:18:19.759
Um so that I thought that was pretty cool.
00:18:19.920 --> 00:18:27.039
I know people have issues with Cloudflare as well, like, and it also feels weird to have the whole internet behind Cloudflare, like a single company.
00:18:27.359 --> 00:18:35.039
But in times like this, you know, people do unique things like that, um, and protect the end users.
00:18:35.119 --> 00:18:37.839
And I think that that's that's super, super valuable.
00:18:37.920 --> 00:18:44.480
And I think anyone else that's doing that sort of thing, who's like, what can how can we use our skills or our position to help people?
00:18:44.720 --> 00:18:49.519
Are you know, those are the companies that I would I would back in in the new future.
00:18:49.759 --> 00:18:53.279
What do you think about the uh I saw you tweeting about the railway to check?
00:18:53.519 --> 00:18:54.079
Yeah, railway.
00:18:54.319 --> 00:18:55.920
What are the implications of that?
00:18:56.960 --> 00:19:00.799
Well, your crypto is probably already drained if you had your crypto key in Railway.
00:19:00.960 --> 00:19:01.759
Oh my god.
00:19:02.559 --> 00:19:05.039
Um I don't even really know what Railway is.
00:19:05.119 --> 00:19:06.160
I've never used it before.
00:19:06.400 --> 00:19:15.119
Okay, so Railway is a um, it's like um, it's like one of those newfangled AI coding deployment building platforms.
00:19:15.920 --> 00:19:27.279
So basically, if you have like a GitHub with some code in it, if you have like if your AI agent built like a little applet, you have to like put it somewhere to get it deployed and you know, share it with your friends.
00:19:27.599 --> 00:19:31.119
Railway was like pretty uniquely positioned to do all that.
00:19:31.200 --> 00:19:35.359
So they they would like do a build or do a deploy for you and it'd be automatic.
00:19:35.519 --> 00:19:37.519
They made it really, really easy for you.
00:19:37.759 --> 00:19:50.400
And one way they did that was they also would like hold your secrets, and so secrets meaning your LLM like tokens, your API keys, your stripe keys, your uh your private keys for your wallets or whatever.
00:19:50.640 --> 00:19:51.119
That's crazy.
00:19:51.359 --> 00:20:02.640
Um, and so usually it's more hobby projects, but like um like trading bots and stuff sometimes run on or could theoretically run on Railway.
00:20:03.759 --> 00:20:06.160
Yeah, like MEV bots theoretically.
00:20:06.319 --> 00:20:28.799
Um and so basically, we don't exactly know what happened yet, but basically the hackers got all the secrets variables in all in everyone's accounts, and so that they've and they've just been going down and grabbing all the money they can out of the crypto keys, but also like stealing people's like credits, like their AI credits, uh basically whatever they can get their hands on.
00:20:29.039 --> 00:20:33.839
Um it's another it's just yeah, yeah.
00:20:34.000 --> 00:20:39.200
That apparently that's what apparently that's what they wanted more than the crypto.
00:20:39.599 --> 00:20:43.359
Um so yeah, and it's a good example though, right?
00:20:43.440 --> 00:20:50.640
Like if you are a person you're using Railway with crypto keys because you have a project or you have a whatever, that's fine, that's great.
00:20:50.799 --> 00:20:52.240
Just don't put all your money there.
00:20:52.400 --> 00:20:54.960
I would say don't even put like one percent of your money there, right?
00:20:55.039 --> 00:20:58.400
Like put a little pocket of money there, and you know what?
00:20:58.480 --> 00:21:01.599
If it gets wrecked, that sucks, but you're gonna be okay.
00:21:02.559 --> 00:21:02.880
Right?
00:21:03.039 --> 00:21:03.519
Yeah.
00:21:03.839 --> 00:21:15.440
Is there any crypto assets that you think are uniquely secure, like the private money stuff, Monero, Zcash, like Nier, stuff like this?
00:21:15.519 --> 00:21:22.160
Like, is there anything you were like this is battle tested in a really, really, really good spot for the future that we're entering?
00:21:23.440 --> 00:21:26.640
Uh uh.
00:21:28.240 --> 00:21:28.720
Fuck.
00:21:28.880 --> 00:21:32.400
I mean, okay, so I'll say privacy obviously is a big one.
00:21:32.799 --> 00:21:45.759
Um, I think especially as automation and just like the the ability for like random people to um like extrapolate huge amount of like intel from big data sets.
00:21:46.079 --> 00:21:55.599
Um, I think that that's gonna like lower the barrier and like it's gonna make it so that more people, like your average person, is just more aware of what they're sort of leaking on the internet.
00:21:56.079 --> 00:21:59.759
Um, so anything, anything that's privacy related is you.
00:22:00.160 --> 00:22:00.960
Usually a good call.
00:22:01.039 --> 00:22:04.640
I personally I stick with Monero and Zcash, both of them.
00:22:05.039 --> 00:22:06.480
I don't go after the newfangled ones.
00:22:06.640 --> 00:22:10.799
And you feel like Monero and Zcash are in like are not something to be concerned about.
00:22:11.759 --> 00:22:15.519
I mean, everything is on the table at this point.
00:22:15.680 --> 00:22:23.279
But I think in terms of like in terms of realistically, like, you know, they're they're more hardened than probably the rest.
00:22:23.920 --> 00:22:28.400
Um I'm yeah, I I like I'm a classic person though.
00:22:28.720 --> 00:22:32.240
Like I also like I I hold those alongside my Bitcoin and my Ethereum.
00:22:32.640 --> 00:22:34.160
Are you concerned about Bitcoin at all?
00:22:34.480 --> 00:22:44.640
After all this Justin Drake stuff and um I think that it'll be okay, but my biggest concern with Bitcoin is the Bitcoin culture.
00:22:45.039 --> 00:22:52.000
They just they spend so much energy fighting and not necessarily evolving.
00:22:53.119 --> 00:23:05.680
And this yeah, but I think that in the last six months or so, just with all the really sort of Bitcoin focused exploits and hacks that have happened and impacted the community, I think they're they're getting a lot better.
00:23:05.839 --> 00:23:09.759
They're like playing catch-up though, relative to Ethereum and Solana, right?
00:23:09.920 --> 00:23:16.160
Because again, like Ethereum's like been hardening the smart contracts, reacting to stuff, improving stuff.
00:23:16.319 --> 00:23:28.079
They have a really good um just like a way of navigating change where the Bitcoiners are basically have been trying to avoid any amount of change, and then when they're forced to change, it's quite hard.
00:23:28.400 --> 00:23:29.200
That's not great.
00:23:30.160 --> 00:23:31.680
That's that's fairly optimistic.
00:23:31.759 --> 00:23:32.799
I can like live with that.
00:23:32.960 --> 00:23:36.319
Okay, for not for me, but for the non-technical people in the chat.
00:23:36.480 --> 00:23:46.960
Do you have any advice on how to follow the significant moments and like the implications of what
happens here moving forward?
00:23:47.039 --> 00:24:04.960
Like, how do you figure out what is big and what is just like I know it's kind of a brutal question, but I am just curious like, what's just like Twitter hype versus what is actually impactful versus who is just LARPing versus who is serious and actually on sort of the front lines of protecting some of this stuff?
00:24:05.279 --> 00:24:13.279
Yeah, so I think it's actually quite similar to how you would like suss out like people who talk about the markets or the coins or whatever.
00:24:13.440 --> 00:24:19.680
Like there's people that write the like breaking warning, all caps stuff.
00:24:19.920 --> 00:24:24.880
And it's not necessarily that they're wrong, it's just like that's like your entry point.
00:24:25.039 --> 00:24:26.880
You're like, okay, something's happening here.
00:24:27.039 --> 00:24:30.720
You shouldn't actually take it that seriously.
00:24:30.880 --> 00:24:35.119
You should use it as like a jumping off point to go investigate further.
00:24:35.359 --> 00:24:50.240
Um, and then you want, yeah, you just want um to find people and articles and conversations that are a bit deeper and fly under the radar a bit and seemed more nuanced and not like freaking out.
00:24:50.400 --> 00:24:57.119
Um, and I also like, you know, when you especially like if you start clicking security stuff, you're gonna get more security stuff.
00:24:57.680 --> 00:25:09.119
Notice that for all these incidents, there's like a few people that are like they'll talk about one incident, but then the next incident, they're not, you'll go and look and they're not talking about it.
00:25:09.359 --> 00:25:14.400
It's that's usually like a pretty good indication that like everything's gonna be okay, right?
00:25:14.880 --> 00:25:15.200
Okay.
00:25:16.000 --> 00:25:22.720
Because like if it was if the world was literally going to end, every security expert would be talking about it.
00:25:22.880 --> 00:25:29.519
So while these are like bigger incidents, there's still like a lot of really smart people who are like, Shrug, like, I'm gonna go to the beach today.
00:25:29.759 --> 00:25:31.279
Okay, so you're not freaking the fuck out.
00:25:31.599 --> 00:25:32.799
You're not gonna like panic all day today.
00:25:32.880 --> 00:25:33.359
It's 7 a.m.
00:25:33.519 --> 00:25:34.480
Like what do you get off this call?
00:25:34.559 --> 00:25:35.839
Are you gonna be panicking and freaking out?
00:25:36.000 --> 00:25:43.519
Are you sort of like like where are you at on severity of today's like severity after looking at some of the damn at some of the damage?
00:25:44.079 --> 00:25:53.759
Um God, I mean I was uh I was up, I went to bed, and then I got back up, and then I'm probably gonna go back to bed after this and take another nap.
00:25:54.079 --> 00:26:01.920
So it's not like a normal, it's definitely not a normal day, but I we'll see.
00:26:02.400 --> 00:26:04.079
There's still a lot of cleanup to be done.
00:26:04.160
--> 00:26:09.359
I think we'll see a couple like um follow-up incidents on the PHP stuff, especially.
00:26:09.519 --> 00:26:12.400
Like there's gonna be another, someone's gonna find another vulnerability or something.
00:26:12.480 --> 00:26:14.240
We're gonna have to do it all over again.
00:26:14.559 --> 00:26:20.480
Um the railway one, I'm interested in seeing if there's any like fallout from that one.
00:26:21.039 --> 00:26:25.359
Um theoretically, they got like some admin keys and we just don't know it yet.
00:26:25.680 --> 00:26:28.799
Uh, but yeah, generally, I don't know.
00:26:30.480 --> 00:26:32.480
Don't okay, panicking is a bad idea.
00:26:32.799 --> 00:26:33.519
Okay, just remember.
00:26:33.839 --> 00:26:35.119
I won't use that word anymore, by the way.
00:26:35.200 --> 00:26:35.599
I'll stop.
00:26:35.680 --> 00:26:37.440
I'll I'll remove that from my vocabulary.
00:26:37.680 --> 00:26:39.359
I am my eyes are wide open though.
00:26:39.519 --> 00:26:39.680
Right.
00:26:39.920 --> 00:26:42.319
We are we are gonna be we're gonna be on it.
00:26:42.559 --> 00:26:43.599
It's gonna be a long couple months.
00:26:43.759 --> 00:26:44.799
Uh fair.
00:26:45.599 --> 00:26:48.319
Um, I mean, it's already been a long couple months, dude.
00:26:48.400 --> 00:26:50.000
It's every day, every day.
00:26:50.640 --> 00:26:56.480
I made a joke, like today's like the least eventful day of like the last month, you know, it's like nine things happen.
00:26:56.880 --> 00:26:59.119
Um it's kind of insane.
00:26:59.440 --> 00:27:01.839
Okay, you're incredible, and I really appreciate you coming on.
00:27:02.000 --> 00:27:24.799
Basically, my last question for you if you have any sage sage advice for crypto stuff, but I think we're relatively savvy with the crypto stuff and maybe some of the non-crypto regular internet opsec, is there any easy, quick stuff that especially now, people should be doing, paying attention to, using to protect themselves that maybe we are actively not?
00:27:25.839 --> 00:27:26.079
Yeah.
00:27:26.240 --> 00:27:38.480
So one thing to keep in mind is that when we have these like big web two trad internet things happening, is that it's it there's upside to not having to do things, right?
00:27:38.559 --> 00:27:43.279
So if you have all your money in Coinbase and PHP hits, you don't have to do anything.
00:27:43.519 --> 00:27:48.400
However, that means you're fully reliant on Coinbase to do the things.
00:27:48.720 --> 00:27:57.599
So this is another reason why again, I just I my best recommendation is like to have multiple eggs in multiple baskets.
00:27:57.839 --> 00:28:09.200
Um, Coinbase is obviously in a different, a different universe than some of the shadier exchanges, but also think about like your wallets, your trading bots, anywhere that has your private key.
00:28:09.440 --> 00:28:19.279
Think carefully about like how much money you have in those because um, you know, it only takes one incident for for that to just be gone.
00:28:19.359 --> 00:28:22.000
And you don't want it to be all your money, please.
00:28:22.240 --> 00:28:33.839
Um, and then yeah, also just in general with all your accounts, um the biggest thing people can do to level up is like get like a Yuba key or another hardware 2FA.
00:28:35.839 --> 00:28:38.160
Carry it around, put it on everything.
00:28:38.400 --> 00:28:41.519
Um, it really does make a huge difference.
00:28:41.839 --> 00:28:50.319
And there's a lot of instances where things will be compromised, but because you have that hardware, uh, they can't get into you know the most critical accounts.
00:28:50.480 --> 00:28:56.640
So think about like your Google accounts, your Dropbox, your Apple, like your computer, like you know, those sorts of things.
00:28:56.880 --> 00:29:02.559
The hardware helps helps a lot, but I think it's something that most people still don't have.
00:29:03.039 --> 00:29:04.880
The new ledger phone.
00:29:07.200 --> 00:29:11.200
I mean, maybe wait for version two for the ledger book.
00:29:11.920 --> 00:29:13.440
Um, Tay, thank you.
00:29:13.680 --> 00:29:14.400
Honestly, thank you.
00:29:14.480 --> 00:29:19.839
I I needed like a calm voice to come tell us that it's gonna be okay.
00:29:20.240 --> 00:29:21.440
The sky is not falling.
00:29:21.599 --> 00:29:22.640
Um, you're incredible.
00:29:22.720 --> 00:29:23.599
Do you have anything to show?
00:29:23.759 --> 00:29:24.640
Like, are you working anything?
00:29:24.720 --> 00:29:29.519
Do you want to direct people podcast, newsletter, anything you want to show reference?
00:29:29.599 --> 00:29:31.920
Because I think there's a lot of fans that would yeah.
00:29:32.079 --> 00:29:37.920
Well, okay, so I do I have my own podcast with like Kane and Austin, and that's uneasy money.
00:29:38.000 --> 00:29:39.039
So you can listen to me.
00:29:39.119 --> 00:29:42.559
We just like shoot the shit about AI and crypto all once a week.
00:29:42.720 --> 00:29:44.799
Um, but I'm also on Twitter.
00:29:44.960 --> 00:29:47.920
I don't have a job, I'm so unemployed right now, it's fantastic.
00:29:48.079 --> 00:29:49.039
I love everything.
00:29:49.279 --> 00:29:51.119
Um, but I'm on Twitter.
00:29:51.200 --> 00:29:56.000
My handle's Tay Bano, so T-A-Y-B-A-N-O, and then underscore at the end.
00:29:56.079 --> 00:29:56.880
I'm Tay.
00:29:57.039 --> 00:29:58.480
They can just find you from your freaking thing.
00:29:58.559 --> 00:29:59.359
Yeah, and I have you linked it.
00:29:59.519 --> 00:30:00.799
If you guys, yeah.
00:30:01.119 --> 00:30:05.599
So um, you can ask me questions, like at me and ask me stuff.
00:30:05.759 --> 00:30:07.599
And you know, what do you think about this?
00:30:07.680 --> 00:30:14.240
I'm I'm again very unemployed and very on Twitter or X or whatever we call it these days.
00:30:14.480 --> 00:30:15.680
I'm gonna take you up on it.
00:30:15.759 --> 00:30:17.119
Um Tay, you're the goat.
00:30:17.200 --> 00:30:18.960
Thank you so much, and good luck.
00:30:19.119 --> 00:30:19.599
Good luck.
00:30:19.759 --> 00:30:20.240
Yeah, good luck.
00:30:20.480 --> 00:30:20.799
You too.
00:30:21.039 --> 00:30:21.839
Okay, one.
00:30:22.000 --> 00:30:22.400
Much love.
00:30:22.480 --> 00:30:22.880
Thank you.
00:30:23.039 --> 00:30:23.599
Bye bye.
00:30:23.839 --> 00:30:24.160
Bye.