text stringlengths 7 369 |
|---|
[2204.20 --> 2210.32] I was listening to your segment about what to do with syncing certificates to multiple servers using something like S3. |
[2210.80 --> 2212.04] And I have some comments. |
[2212.30 --> 2214.66] Please, for the love of God, don't do this. |
[2215.02 --> 2217.78] Firstly, because the certificates are the keys to your kingdom. |
[2218.16 --> 2224.70] A leak of those removes all security on your services and lets anyone in the middle snoop on whatever it is you're doing. |
[2225.64 --> 2228.76] Self-hosted or otherwise, certificates are massively important |
[2228.76 --> 2232.88] and shouldn't be stored anywhere other than where they're absolutely needed. |
[2233.46 --> 2235.86] Secondly, because it's just not necessary. |
[2236.32 --> 2241.32] If you're not using wildcard certificates, then just creating certificates for each domain is totally fine. |
[2241.58 --> 2244.68] And they can be stored and managed wherever the domain needs to be served from. |
[2244.88 --> 2248.82] If you are using wildcards, there's nothing which says only one can exist in the world. |
[2249.42 --> 2254.54] My servers each have their own wildcard automatically managed and renewed by Trafic. |
[2254.54 --> 2259.62] This way, there's neither a need to store their certificates anywhere other than the servers, |
[2259.82 --> 2263.52] nor to set up some secure storage or communication method. |
[2264.36 --> 2267.56] I don't even bother backing out my certificates anymore. |
[2267.82 --> 2268.96] That seems crazy to me. |
[2270.00 --> 2272.66] Let's Encrypt, or more specifically, Acme, |
[2272.92 --> 2276.32] makes provisioning certs insanely simple. |
[2276.72 --> 2278.68] Let them deal with the security side of things. |
[2278.68 --> 2283.18] We can just use their tools to create all the certificates we want, wherever we want. |
[2283.42 --> 2285.24] Thanks for reading, and keep up the great work. |
[2285.38 --> 2286.56] Your friendly neighbor, Orange. |
[2287.50 --> 2288.74] Thanks for writing in, Jake. |
[2288.84 --> 2293.48] Now, this is Jake of episode 42 fame, who came in on our first community spotlight. |
[2294.64 --> 2300.74] Also, we had Kevin write in, who told us that we're actually trying to overcomplicate the management of SSL certificate management. |
[2300.74 --> 2330.72] He says, |
[2330.74 --> 2330.86] Yeah. |
[2331.22 --> 2331.48] Yeah. |
[2331.78 --> 2332.84] I don't know why we missed that. |
[2333.44 --> 2334.64] It's a really obvious thing. |
[2334.72 --> 2337.96] Just run Acme or Certbot on each machine. |
[2338.36 --> 2339.12] Problem solved. |
[2340.02 --> 2340.36] Well, I do. |
[2340.66 --> 2343.12] This is, of course, easy for me to say now, |
[2343.20 --> 2347.44] but I remember specifically on the pre-show that we were not streaming. |
[2348.12 --> 2350.48] We thought, this guy isn't doing this right. |
[2350.58 --> 2353.44] And we did start talking about this, but then we just dropped it, |
[2353.54 --> 2355.60] and we got to the business of actually recording the show. |
[2355.60 --> 2359.36] We have this thing, don't we, where we're always having a pre-show conversation, |
[2359.52 --> 2363.06] and all the best versions of our problem solving comes out then, |
[2363.10 --> 2364.08] and we're like, save it for the show. |
[2364.20 --> 2366.46] And I guess we just forgot to save that nugget. |
[2367.32 --> 2367.48] Yeah. |
[2367.80 --> 2369.74] It is absolutely our bad. |
[2370.04 --> 2373.36] So, thankfully, we have an awesome audience who helps us with that kind of stuff. |
[2373.44 --> 2377.44] And we have no qualms at all about making corrections and fixing that sort of stuff, |
[2377.48 --> 2379.22] because it's all about just getting the best info out there. |
[2379.22 --> 2384.66] Now, I was hoping to solicit some feedback from the audience on my next networking upgrade. |
[2384.92 --> 2390.16] I've currently got a gigabit network everywhere, which, like most people, I did because it's cheap. |
[2390.30 --> 2393.16] You know, I can buy a five-port switch for 15 bucks at Best Buy. |
[2394.12 --> 2398.56] And every time I've looked at going more than gigabit, so, you know, 10 gigs, |
[2398.84 --> 2402.02] probably the next logical step, I'd look at the switch prices, |
[2402.02 --> 2404.78] and they're like $200, $300 per switch. |
[2404.78 --> 2408.66] And I think, oh, I'll just wait for the prices to come down a little bit. |
[2408.66 --> 2409.50] And they never seem to. |
[2410.16 --> 2413.12] And Jeff Geerling, you know, who was also on the show previously, |
[2413.40 --> 2422.16] just did a video on a Microtix switch, the CRS3091G8S plus IN. |
[2422.88 --> 2424.34] That name rolls off the tongue, doesn't it? |
[2424.42 --> 2424.86] Flipping heck. |
[2425.06 --> 2425.60] Yeah, nice. |
[2425.84 --> 2426.28] Smooth. |
[2427.70 --> 2429.78] So, basically, questions for the audience. |
[2430.00 --> 2433.20] If you've done 10 gig, I'm really curious to know how you did it. |
[2433.20 --> 2435.08] Did you run fiber in your house? |
[2435.20 --> 2436.78] Did you do it with CAT 6A? |
[2436.78 --> 2441.24] Thankfully, I ran CAT 6A on the trunks in my house when I moved in three years ago. |
[2441.98 --> 2444.90] Or am I shooting for the stars with 10 gig? |
[2444.98 --> 2447.10] Is 2.5 enough for my needs right now? |
[2448.20 --> 2449.46] That's a fair question. |
[2449.58 --> 2453.68] I'm curious what you're doing right now that makes even gigabit insufficient. |
[2454.14 --> 2455.82] Well, I've got gigabit WAN. |
[2455.82 --> 2461.80] So, sometimes, if I'm pulling something down from the internet and then trying to stream something to Plex, |
[2462.20 --> 2467.28] you know, like a high bitrate movie or moving some files around from my desktop to my NAS, for example, |
[2467.94 --> 2470.50] that can sometimes cause issues. |
[2471.12 --> 2471.20] Sure. |
[2471.50 --> 2476.46] Yeah, especially when you're, you know, not working with, like, Cisco switches there at your house, right? |
[2476.52 --> 2477.98] So, that also makes a difference. |
[2478.06 --> 2482.08] That makes, I mean, I'm never going to stop a guy from going as much performance as possible. |
[2482.08 --> 2482.90] I'm all about it. |
[2483.44 --> 2485.60] I think that's a great question. |
[2485.82 --> 2487.44] Is 2.5 gigabit enough? |
[2488.34 --> 2491.54] And is it worth the leap to 10 gigabit? |
[2491.76 --> 2499.62] I have to tell you, Alex, I feel like you're the kind of guy that appreciates the value of doing it once and just doing it right. |
[2500.14 --> 2504.92] You know, like, you could do 2.5 gigabits, and you could probably get away with it for a couple of years, |
[2505.06 --> 2506.08] probably even five years. |
[2506.08 --> 2511.04] But there's going to be a point where you're going to wish it was faster because you're just that kind of guy. |
[2511.36 --> 2512.98] And you know it could be better, too. |
[2513.08 --> 2513.84] That's the other thing. |
[2514.50 --> 2516.58] You are totally spot on. |
[2516.78 --> 2519.50] Now, Lucas writes in the live chat, |
[2520.08 --> 2525.82] I impulse signed up for 2 gig Google Fiber and realized almost nothing I have can distribute it across the LAN. |
[2526.58 --> 2527.26] Oh, no. |
[2528.34 --> 2531.70] Who thought we'd have WAN connections that were faster than gigabit, huh? |
[2532.10 --> 2532.40] Yeah. |
[2532.54 --> 2534.14] I mean, I would love to have that problem. |
[2534.14 --> 2536.94] I'm still stuck with 300 megabits here at the studio. |
[2537.12 --> 2537.62] That's what I get. |
[2537.62 --> 2538.18] I'm with you, Chris. |
[2539.24 --> 2540.30] I'm not even joking. |
[2540.44 --> 2545.32] There are days when the Starlink in the RV performs better than the Comcast here at the studio. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.