text stringlengths 7 369 |
|---|
[2906.08 --> 2916.00] Yeah, it's kind of sounding like maybe the handling of the secrets, distributing that to multiple machines, that workflow hasn't really been worked out yet in this case. |
[2916.88 --> 2918.54] That's a fine thing to experiment with. |
[2918.64 --> 2927.78] But if that's not an essential, you know, if that's just going to be an implementation detail to the actual point of getting this done, you don't need to be the one handling that part of it. |
[2927.78 --> 2929.76] What about just something like S3? |
[2930.00 --> 2932.02] You know, I mean, you can secure that. |
[2932.12 --> 2935.94] You can also set time-expiring links, if that was the kind of thing you were worried about. |
[2936.36 --> 2938.02] And you don't have to host it. |
[2938.50 --> 2939.18] Exactly right. |
[2939.30 --> 2943.98] Yeah, I mean, you can do, like you say, authentication on an S3 request. |
[2945.08 --> 2948.60] It's easily accessible over the internet, safely, securely. |
[2948.76 --> 2950.14] People do it all the time. |
[2950.14 --> 2956.66] I'm sure you've all seen the web URL of an S3 item in your URL bar at some point. |
[2957.72 --> 2962.34] You know, it's a chicken and egg problem with SSH that you come across all the time, right? |
[2962.36 --> 2966.96] I want to automate this thing, but I need my SSH key over there already before I do the thing. |
[2967.52 --> 2967.96] Yep. |
[2968.90 --> 2969.30] Yep. |
[2969.88 --> 2970.08] That's true. |
[2970.10 --> 2973.14] SS3 solves that particular problem, or any kind of object storage, really. |
[2974.02 --> 2978.44] But the reason I think that we talked about S3 in particular is that it's authenticated. |
[2978.44 --> 2986.14] And if you're putting a secret up there, like a certificate, you need to have some kind of authentication in front of it. |
[2986.50 --> 2989.94] And you could just use object storage at Linode already, because that's S3 compatible. |
[2990.42 --> 2990.90] Good to go. |
[2991.24 --> 2992.76] So nobody's going to suggest sync thing. |
[2992.86 --> 2994.18] Okay, so don't use sync thing, man. |
[2994.20 --> 2994.98] We did mention it. |
[2995.10 --> 2995.86] Yeah, yeah, yeah. |
[2996.22 --> 2997.44] I don't know, like it's... |
[2998.18 --> 3001.56] How secure is it with third-party bounce servers and stuff like that? |
[3001.80 --> 3003.06] It's probably fine. |
[3003.26 --> 3005.44] Yeah, it just doesn't seem like the right tool, does it? |
[3005.44 --> 3008.48] I mean, it seems like you could do it, but it doesn't seem like the right way to do it. |
[3008.56 --> 3010.08] Go old school and use BitTorrent. |
[3010.22 --> 3011.02] Yeah, there you go. |
[3011.06 --> 3012.56] Or BitTorrent Sync, you could do that. |
[3012.62 --> 3013.64] I think you mean Resilio. |
[3014.06 --> 3014.90] Resilio Sync, yeah. |
[3015.70 --> 3021.12] I mean, the thing is, with the S3 solution, it would work in much a similar way as sync thing, right? |
[3021.12 --> 3028.12] I guess with sync thing, you could, and this is just solutionizing off the top of my head, which I hate doing, but anyway. |
[3028.74 --> 3042.08] You could encrypt the secret on whatever box is running Lego, and then sync the encrypted thing with sync thing, and then have the logic to decrypt it at the remote site that way. |
[3042.16 --> 3044.58] And that would be kind of secure as it's going over the wire, but... |
[3044.58 --> 3046.04] I bet you that's how I would do it. |
[3046.22 --> 3048.68] If I were to solve this problem, that's probably what I would do. |
[3048.68 --> 3049.40] But here's the downside. |
[3049.66 --> 3053.30] On each of those other four remote systems, you still need the decryption password. |
[3053.40 --> 3053.58] Yeah. |
[3053.92 --> 3055.38] Probably stored in plain text. |
[3055.72 --> 3056.52] Probably on disk. |
[3056.70 --> 3057.08] So... |
[3057.08 --> 3057.40] Yeah. |
[3057.40 --> 3062.44] Are you in any better solution than just doing it with a sync thing naked? |
[3062.66 --> 3063.10] I don't know. |
[3063.48 --> 3063.84] Probably not. |
[3064.16 --> 3065.68] But if anybody has an idea, let us know. |
[3065.84 --> 3067.30] Selfhosted.show slash contact. |
[3067.90 --> 3069.98] Or send us a boost like Optimus Gray did. |
[3070.54 --> 3071.50] Optimus boosted in. |
[3071.56 --> 3073.00] He said, I hope to see you next week. |
[3073.36 --> 3075.44] If gas prices aren't too high, that is. |
[3075.56 --> 3077.00] But don't work Brent too much. |
[3077.04 --> 3077.72] I want to see Brent. |
[3078.24 --> 3078.84] That's what he said. |
[3079.14 --> 3080.92] He sent us 500 sats to say that. |
[3080.92 --> 3083.92] If you want to give us a boost, it's like the bat line into the show. |
[3084.26 --> 3086.90] You go get a new podcast app at newpodcastapps.com. |
[3087.40 --> 3089.46] Load that wallet up and send us a boost. |
[3089.82 --> 3091.22] And we'll get it here on the show. |
[3092.04 --> 3096.34] I want to say a big thank you to our SRE, Site Reliability Engineer subscribers. |
[3096.56 --> 3100.52] You make this show possible over at selfhosted.show slash SRE. |
[3101.10 --> 3105.16] And they can join the party, Jupiter.party, if they want to support the entire network. |
[3105.72 --> 3108.34] And get access to all the special features of the shows. |
[3108.94 --> 3109.34] Yeah. |
[3109.48 --> 3111.66] I wonder, you know, I wonder if we'll have some extras. |
[3112.04 --> 3113.66] We should probably plug the extras just in case. |
[3113.78 --> 3116.36] And we get any extra content that we record here with the group of us. |
[3116.36 --> 3117.20] Selfhosted.show. |
[3117.80 --> 3119.30] Wes, thanks for hanging out with us. |
[3119.44 --> 3120.26] Thanks for having me. |
[3120.36 --> 3122.72] We really didn't give him a chance to stretch his wings. |
[3123.20 --> 3127.00] You know, we could get into some topic down the road that Wes could probably really dig |
[3127.00 --> 3127.28] into. |
[3127.92 --> 3128.72] We should think about that. |
[3129.20 --> 3131.70] So Wes, you're just going to have to come back so that way we can do it again. |
[3132.16 --> 3133.46] Oh, I think we can come up with something. |
[3133.80 --> 3135.02] I think we can indeed. |
[3135.38 --> 3136.92] Go find our contact page. |
[3136.92 --> 3137.66] Send us in your thoughts. |
[3137.78 --> 3138.36] Let us know what you think. |
[3138.42 --> 3140.48] Maybe you got a solution for one of the things we talked about today. |
[3140.96 --> 3143.66] Selfhosted.show slash contact is the place to get in touch. |
[3143.66 --> 3145.00] You can find me on Twitter. |
[3145.10 --> 3146.02] I'm at ChrisLAS. |
[3146.18 --> 3147.94] I thought we weren't doing the Twitter thing anymore. |
[3148.02 --> 3148.92] I decided to do it this week. |
[3149.00 --> 3149.30] Okay. |
[3149.46 --> 3149.70] Okay. |
[3149.80 --> 3151.34] It's because Elon's on board now, is it? |
[3151.52 --> 3151.78] Yeah. |
[3151.78 --> 3152.04] Okay. |
[3153.12 --> 3155.32] I'm on Twitter also at Ironic Badger. |
[3155.46 --> 3158.48] I'm also, and this is something that a listener wrote in and let me know about. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.