Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[2414.94 --> 2415.44] consequences.
[2415.44 --> 2416.94] It's like something terrible happens.
[2417.02 --> 2419.28] And we're like, oh no, this terrible thing happened.
[2419.38 --> 2422.08] But so much of the time, that terrible thing was completely predictable.
[2422.74 --> 2426.50] And we just didn't predict it because we thought it'd go fine.
[2427.08 --> 2428.18] Like I worked for a lifeguard.
[2428.36 --> 2429.70] When I was younger, I worked as a lifeguard.
[2429.70 --> 2434.60] I remember one of the things that we always did is we trained a lot, but also did a lot
[2434.60 --> 2437.50] to make sure that the environment was always a safe one.
[2438.08 --> 2439.12] So it was like, we did a lot of...
[2439.12 --> 2441.14] That's why lifeguards yell at people so much.
[2441.26 --> 2442.04] And they're like, don't run.
[2442.22 --> 2445.02] Don't do these things that might result in you getting injured.
[2445.50 --> 2448.40] I kind of feel like in software engineering, we just let people do whatever.
[2448.74 --> 2452.02] And then people slip and bash their head and they're bleeding all over the place.
[2452.08 --> 2453.44] And we're like, oh no, how did this happen?
[2453.56 --> 2458.78] And it's like, well, not only did we not tell people not to run, but we also left giant puddles
[2458.78 --> 2462.40] of water on the floor because we didn't put down the proper mats to make sure that even
[2462.40 --> 2463.92] if they are running, they can do it safely.
[2464.16 --> 2467.82] There's all these other things that you have to set up as precautions that I feel like in
[2467.82 --> 2469.96] software engineering, we just kind of don't do.
[2470.04 --> 2474.96] And part of me wonders if we don't do that because there aren't enough consequences flowing
[2474.96 --> 2476.16] down to the engineers.
[2476.16 --> 2481.78] I feel like the number of times I've been at companies that I've worked at banks and
[2481.78 --> 2484.46] people have been like, well, you know, this isn't like life or death.
[2484.62 --> 2488.12] And I'm like, this is affecting people's money and their livelihood.
[2488.56 --> 2489.72] Like, what do you mean?
[2490.50 --> 2494.04] And that's always a thing that gets rolled out is if it's like, oh, well, we're not doing
[2494.04 --> 2495.14] things that could kill people.
[2495.28 --> 2498.02] It's like, well, we're doing things that can substantially affect people's lives.
[2498.24 --> 2501.00] And I feel like we have to take that into account.
[2501.00 --> 2505.32] Because when we don't, we do lots of immoral things like run psychological experiments
[2505.32 --> 2508.22] on people without their knowledge and other terrible things.
[2508.22 --> 2510.48] Because we're like, ah, what's the harm?
[2510.64 --> 2511.84] I haven't done that for weeks.
[2512.00 --> 2513.04] I don't know why you're bringing it up.
[2515.08 --> 2515.92] It's spooky.
[2516.84 --> 2518.08] It's a spooky show.
[2525.02 --> 2526.78] I have a spooky story, I think.
[2527.02 --> 2527.98] It feels spooky.
[2527.98 --> 2530.92] So I'd recently joined this company.
[2531.94 --> 2535.28] And of course, because it's the modern day, they're using Kubernetes.
[2536.24 --> 2538.44] And of course, they're using all the shiny things of Kubernetes.
[2538.60 --> 2539.46] They're also using Istio.
[2540.10 --> 2541.56] No one actually knows how any of this works.
[2541.62 --> 2543.92] It's just like, oh, this is what we're supposed to be using.
[2544.08 --> 2547.98] So we have this big old cluster and it's running and our DevOps people are pulling their hair
[2547.98 --> 2549.04] out because I hate all of this.
[2549.52 --> 2552.08] And I start reading through the code base and looking at things.
[2552.18 --> 2555.22] And I'm like, okay, these auth policies look a little funky.
[2555.22 --> 2559.70] And then I go talk to people and they're like, we don't really have any auth policies.
[2560.12 --> 2561.90] Everything's just kind of open right now.
[2562.38 --> 2564.08] Everything in the back end, you just talk to each other.
[2564.16 --> 2564.98] There's no auth policies.
[2565.14 --> 2566.96] And I'm like, are you sure?
[2567.04 --> 2568.92] Because I see these auth policies in the code base.
[2569.00 --> 2571.32] They're like, yeah, but we don't think they're being used for anything.
[2571.46 --> 2572.58] And I was like, okay.
[2572.86 --> 2575.12] So I just kind of let it go and go about my business.
[2575.26 --> 2576.92] And then I have a few more of these conversations.
[2577.16 --> 2578.84] And I'm like, this feels weird.
[2578.96 --> 2580.86] But all these people know more than I do.
[2580.86 --> 2590.56] And then months and months later, someone stumbles across this one auth policy that has no labels and no access rules.
[2591.24 --> 2596.34] Which in Istio language means that it applies to literally everything and allows all traffic in.
[2597.06 --> 2605.86] So this one policy had just opened our entire API, including the public API, to the entire internet for anybody to do anything without needing any authorization.
[2605.86 --> 2610.76] You just needed a JSON web token that you could easily get from anywhere.
[2611.72 --> 2614.22] And I was just like, so it caused all these problems, right?
[2614.68 --> 2615.64] Everybody's freaking out.
[2616.14 --> 2617.98] And then they just ripped that policy out.
[2618.06 --> 2619.98] And they're like, okay, well, without this policy would be fine.
[2620.18 --> 2624.48] But then all of those auth policies that had been sitting there that I was like, these look funky.
[2624.70 --> 2625.84] All those took over.
[2626.00 --> 2627.22] And all of those were broken.
[2627.62 --> 2629.36] So then it broke all the APIs.
[2629.36 --> 2637.98] So then they had to put the other policy back and then go through and go find every single auth policy within Istio and then fix all of those auth policies.
[2638.66 --> 2643.38] And then they could finally remove that one policy that was opening everything to the world.
[2643.50 --> 2646.98] And I think the total amount of time that the door was just open was about nine months.
[2648.02 --> 2651.32] And to the knowledge that people have, nothing bad happened.
[2651.98 --> 2654.70] But yeah, it was quite horrifying.
[2655.42 --> 2658.76] That is still a security incident requiring disclosure, I'm afraid.
[2658.76 --> 2659.12] Yeah.
[2659.72 --> 2660.24] I know.
[2660.34 --> 2661.86] I'm just like, is this disclosure?
[2664.00 --> 2665.24] No, it was, yeah.
[2665.32 --> 2666.80] I was like, oh, oh no.
[2667.28 --> 2671.44] It taught me a lesson that like when I see funky things, I should probably bring them up a little bit soon.
[2671.52 --> 2672.90] It's like, no, that policy is there.
[2672.94 --> 2675.30] And that policy definitely doesn't work.
[2675.88 --> 2681.12] And some of the broken things were like some YAML white spacing thing where it's like something was tabbed in a little too far.
[2681.16 --> 2684.84] And then people were just copying and pasting these policies and then not testing them,
[2684.84 --> 2690.88] which was like another thing that we had to go back and be like, please test the things that you put into the code base.
[2691.20 --> 2691.76] Pretty please.
[2691.86 --> 2692.20] Thank you.
[2692.40 --> 2692.48] Yeah.
[2692.54 --> 2699.54] I think that also is a bit of a lesson is if there are bits of code and you're like, no, yeah, but that doesn't do anything now.
[2699.62 --> 2702.20] Like that used to be doing something and now it doesn't.
[2702.20 --> 2704.68] It's like either take it out.
[2705.00 --> 2707.18] If it's really not doing something, get rid of it.
[2707.34 --> 2707.60] Prove it.
[2708.00 --> 2708.32] Exactly.