text stringlengths 0 1.36k |
|---|
[798.88 --> 808.52] I mean, this is one of the problems with, you know, get not updating and getting rid of this is that, you know, people take their best practices from their common tools and and, you know, not using a secure hashing. |
[808.68 --> 810.52] It's just not sending a very good message. |
[810.52 --> 814.66] But I'd like to see, you know, like, Alex, you work for a bank extensively. |
[815.34 --> 817.80] You know, what authentication scheme are you using over there? |
[817.80 --> 825.36] But for I guess for which this is a seems like a very broad question. |
[825.80 --> 828.28] Like what how do we off our employees? |
[828.40 --> 828.94] How do we off? |
[829.74 --> 830.88] How do you off like customers? |
[830.88 --> 837.84] Like, do you do you actually, you know, encrypt or hash different pieces of, you know, the stripe thing? |
[837.92 --> 838.88] I hope you do. |
[839.66 --> 842.62] I hope my credit card number is not just like sitting there. |
[842.62 --> 843.14] Yeah. |
[843.38 --> 850.90] So PCI determines all of the algorithms for how you must store credit card numbers and things like that. |
[851.00 --> 864.48] So I would probably I have a pretty good guess on what it is, but I'm not even credentialed enough to touch or look at any of that code as an early employee at Stripe. |
[864.48 --> 869.34] So I think that's another one of the security precautions that PCI mandates. |
[869.60 --> 872.50] But yeah, it is. |
[872.56 --> 874.46] It is mandated by a body. |
[874.76 --> 892.40] But but as far as just like all of this off goes, I feel like maybe my security brain is coming out a little bit like the way that your password gets hacked is not hashing algorithm collisions currently. |
[892.40 --> 894.16] Um, this one's bad. |
[894.28 --> 896.20] I don't think too many people are using SHA-1. |
[896.40 --> 898.70] Even if you use like HMAC with SHA-1, it's fine. |
[898.78 --> 898.92] Right. |
[899.00 --> 904.30] Like, like there's even ways to to make SHA-1 fine. |
[904.42 --> 908.42] But like use Bcrypt to do passwords. |
[908.84 --> 909.98] Actually, don't. |
[910.66 --> 916.66] My number one recommendation is don't implement any security stuff yourself. |
[916.94 --> 919.80] Use libraries that are well known and well tested. |
[919.80 --> 924.82] Um, like the number one rule at Stripe is don't implement your own crypto. |
[925.00 --> 928.94] Don't don't invent your own crypto because you have not thought it through correctly. |
[929.66 --> 932.54] Um, so that that's my advice. |
[933.56 --> 934.40] Yeah, agreed. |
[934.64 --> 938.18] I tend to rely on people, modules written by smarter people than me. |
[938.30 --> 939.72] Um, right. |
[939.80 --> 948.20] Like the the wide use of something signals far more security than like a smart person to write. |
[948.20 --> 954.02] Like someone can be smart and have a glaring hole that they singularly forgot because there's only one set of eyes on it. |
[954.12 --> 962.16] Uh, but like you can be pretty sure like the rails off stuff works pretty well because every side of the internet would be down if it didn't. |
[962.26 --> 964.32] Unless Linus Torvalds is maintaining that library. |
[964.72 --> 965.28] Then sure, sure, sure. |
[965.28 --> 968.54] But at least it's well known, right? |
[968.62 --> 968.94] Like that. |
[969.06 --> 972.12] Like no one's, uh, no one's being quiet about it. |
[972.84 --> 972.98] Yeah. |
[973.32 --> 973.56] Yeah. |
[973.88 --> 983.38] I've, I've actually been using sodium encryption and signing, uh, for quite a while, which is, I don't know who came up with the standard, but, um, Matthias Boos and the node community has gotten really into it. |
[983.42 --> 986.32] And so there's really good libraries that work both in the browser end and node. |
[986.32 --> 990.68] Um, and it's a really, you know, good, consistent, easy way to do signing in crypto. |
[991.32 --> 1003.36] I, I, the stuff that I've seen, um, from previous jobs that I was at where we did a lot of node stuff, um, it was more like built into CI tests. |
[1003.36 --> 1014.36] So when it would check, uh, to make sure all the tests pass, it would also check for like known vulnerabilities, uh, and maybe like certain NPM packages or the way that like node was written. |
[1014.36 --> 1023.52] So it, would that be separate to other things that people would want to integrate into their like regular behavior? |
[1023.52 --> 1028.02] Or is that just another like good level of authentication? |
[1028.02 --> 1038.88] I mean, it's a good practice to, um, so SNK, S-N-Y-K, um, has a service that you can kind of plug your open source module into, I believe for free. |
[1038.88 --> 1047.38] And then, you know, on your GitHub PRs and stuff like that, um, it'll check if you have any vulnerabilities and there's obviously like a proprietary version as well. |
[1047.38 --> 1052.04] But that, you know, looks through your NPM tree and sees if there's any known vulnerabilities. |
[1052.72 --> 1055.72] Um, and in fact, even offers you ways to patch them and stuff like that. |
[1055.78 --> 1056.94] So it's, it's a pretty nice tool. |
[1056.94 --> 1063.16] Um, but that's really just for, for known vulnerabilities, you know, things that we, we've already seen out in the wild. |
[1063.16 --> 1065.48] It doesn't really protect against, it gets bad practices. |
[1065.84 --> 1075.24] Um, and also, you know, you run into this problem, like Alex was saying, you know, if, if nobody's using the module, then nobody's probably going to take the time to find these vulnerabilities early on. |
[1075.78 --> 1080.92] And so, you know, using well, well known, well trafficked modules will really help as well. |
[1081.76 --> 1082.26] All right. |
[1082.30 --> 1083.90] I think we're, I think we're pretty good there. |
[1083.90 --> 1086.72] I think that we're actually coming into a time for a break now. |
[1086.94 --> 1090.90] First sponsor of the show today is our friends at Rollbar. |
[1091.06 --> 1093.06] Put errors in their place with Rollbar. |
[1093.32 --> 1095.04] Easily get set up for your application. |
[1095.50 --> 1097.94] NPM install dash dash save. |
[1098.20 --> 1098.64] Rollbar. |
[1098.90 --> 1100.60] That'll get you set up with Rollbar's notifier. |
[1101.10 --> 1102.16] You also need an account. |
[1102.30 --> 1104.84] So go to rollbar.com slash changelog. |
[1105.08 --> 1105.58] Sign up. |
[1105.62 --> 1107.92] Get the bootstrap plan for free for 90 days. |
[1107.92 --> 1110.00] With Rollbar's full stack error monitoring. |
[1110.00 --> 1114.70] You get the context, the insights, and the control you need to find and fix bugs faster. |
[1115.04 --> 1117.10] No more relying on users to report your errors. |
[1117.40 --> 1123.62] Digging through log files to debug issues or dealing with a million alerts in your inbox ruining your day. |
[1123.62 --> 1126.54] Once again, rollbar.com slash changelog. |
[1126.62 --> 1126.94] Sign up. |
[1126.96 --> 1128.94] Get the bootstrap plan for free for 90 days. |
[1129.14 --> 1130.42] And now back to the show. |
[1132.90 --> 1133.58] All right. |
[1134.52 --> 1136.30] Let's dive into this a little bit. |
[1136.46 --> 1140.58] So a relatively routine new version of Node came out. |
[1141.28 --> 1142.30] 7.6. |
[1142.46 --> 1144.20] Like we do these releases all the time. |
[1144.20 --> 1151.18] But this one is a big deal and people are making a big deal out of it because V8 got updated in the background. |
[1151.44 --> 1158.92] They've been doing a lot of work so that we can actually take new versions of V8 in point releases and not break the ABI for everybody. |
[1159.04 --> 1159.72] So that's been great. |
[1160.76 --> 1166.24] But in this release, async slash await came out from under a flag. |
[1166.68 --> 1171.32] So now in a current release of Node, you can do async await. |
[1171.32 --> 1178.86] So I'm curious what y'all think of this and what your views are on it. |
[1179.14 --> 1181.22] Because before I get into my view. |
[1182.90 --> 1185.70] I suppose I don't have a ton of opinions. |
[1186.98 --> 1189.56] I understand the two sides of this. |
[1190.18 --> 1200.68] And I feel like I think the primary, at least the thing people are calling their primary concern is performance of this versus callbacks or promises or whatever. |
[1201.32 --> 1207.26] But I think that's silly because A, it'll get faster, the next version. |
[1207.66 --> 1211.30] And B, it's such a small performance hit that who cares. |
[1212.04 --> 1214.46] It's primarily sugar. |
[1214.82 --> 1219.16] So I guess there are the people who dislike sugar and there are people who like sugar. |
[1219.74 --> 1221.40] And just use whatever you want. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.