text stringlengths 0 2.35k |
|---|
[2161.70 --> 2166.20] Like if you released something on Git that had private keys, clearly you need to try to clean that up. |
[2166.30 --> 2168.36] But it's, I agree with you that it is hard. |
[2168.54 --> 2173.18] Like, I don't know, people should be okay with mistakes, but I feel like in practice, people are weird with them. |
[2173.18 --> 2176.56] And there is actually a technical situation that could happen. |
[2176.86 --> 2177.84] There is a rollback. |
[2178.12 --> 2186.34] If you are using, let's say, a single master, a single node, and then it crashes, and you cannot recover the data. |
[2187.08 --> 2196.80] So if the backup you have is old, then older than the state that the client has, they will comply about that situation. |
[2197.26 --> 2202.08] So that is a situation that could happen and has to be taken into account. |
[2202.08 --> 2207.80] So the mistake there will be on having only one node or not having a backup. |
[2208.34 --> 2209.86] I think it's okay to admit mistakes. |
[2210.04 --> 2211.60] I guess mistakes are part of life. |
[2211.72 --> 2212.16] It's okay. |
[2212.38 --> 2214.68] You know, just make a new thing and put that out there. |
[2214.76 --> 2219.32] And hopefully people don't download your mistake before you had a chance to replace it. |
[2219.86 --> 2223.82] Now, I do want to switch gears real quick to the operability aspect of things. |
[2223.82 --> 2233.46] Obviously, if one were to find a use case for MUDB or really immutable databases in general, it's interesting. |
[2233.82 --> 2239.52] As I was researching the technology, I came across other things that I've come across before but didn't realize that's what they were. |
[2239.66 --> 2242.74] Like I came across Amazon's QLDB. |
[2243.20 --> 2244.90] I'm like, hey, that sounds familiar. |
[2244.90 --> 2248.18] And basically, I started tracking basically the origin of these things. |
[2248.30 --> 2250.10] When did these things become popular? |
[2250.38 --> 2252.76] And there are references going back a few years. |
[2252.92 --> 2264.00] But these types of technologies became very popular, I think, in part as a result of an executive order that was issued maybe like a year or so ago on cybersecurity and things like that. |
[2264.00 --> 2269.44] And there was mention of producing or having things like a software bill of materials. |
[2269.76 --> 2272.84] And then I'm like, hey, I'm starting to hear more and more about that now. |
[2273.22 --> 2278.12] There's like advancements we've made with shipping and packaging software and things like that. |
[2278.28 --> 2285.64] And all of a sudden, these dots are connecting for me about all these things that I've read in the past and didn't really know where did this thing come from kind of thing. |
[2285.88 --> 2288.48] And for those listening in, it's interesting. |
[2288.66 --> 2289.82] Basically, find the executive order. |
[2289.94 --> 2292.22] It's called a cybersecurity something, something. |
[2292.22 --> 2295.74] It's basically you can find it on the White House.gov website or whatever. |
[2295.88 --> 2301.48] But you'll see like this mandate, right, with lots and lots of requirements for cybersecurity and everything else. |
[2301.58 --> 2304.48] And you're going to find software bill of materials and stuff mentioned in there and whatnot. |
[2304.70 --> 2313.66] And you can see how things like that, right, are sort of pushing forward the innovation that's happening in this space, especially with things like EMUDB and whatnot. |
[2313.66 --> 2326.36] And one of the things that one of the use cases that you're enabling or solving for is the whole sort of software, you know, verifying the content of a software package. |
[2326.48 --> 2326.60] Right. |
[2326.60 --> 2332.68] So we just talked about how, you know, basically the GoMod proxy, right, basically part of the thing that is also part. |
[2332.90 --> 2348.78] And for those who basically download your modules and you see this weird Go.sum file with all the checksums in there and whatnot, that, you know, all these things sort of play a role, right, into basically verifying that the version of the piece of software that you just got is indeed, right. |
[2348.78 --> 2352.72] It's not going to basically, you're not going to get a different version that has the same checksum, right. |
[2352.72 --> 2356.50] So all these things come together to provide that sort of verifiability thing, right. |
[2356.82 --> 2363.48] So, but I know one of those use cases that you try to sort of solve for head on, right, is this SBOM thing. |
[2363.58 --> 2365.34] Can you take a little bit about that? |
[2365.40 --> 2368.92] And then I want to talk about what it's like to actually run EMUDB in production. |
[2369.32 --> 2369.46] Yes. |
[2369.56 --> 2376.82] So SBOM, so software bill of material, is a term that is used to, let's say, that you create a software and you create it. |
[2376.82 --> 2379.52] Today, you don't write all the software by yourself. |
[2379.64 --> 2381.56] You just use external packages. |
[2382.24 --> 2389.62] And when we look at, let's say, don't JS application, it usually has hundreds of different dependencies. |
[2390.50 --> 2391.98] And the same with Golang, right. |
[2392.08 --> 2395.54] You don't write HTTP server by yourself. |
[2395.64 --> 2400.98] You just take what in standard library and you do the same with contributions from other people. |
[2400.98 --> 2408.30] And the software bill of material is basically describing that if we have this binary or this product, what is it made of? |
[2409.08 --> 2416.88] And here we can actually use this immutable ledger because we just produce those assets, those binaries once. |
[2416.88 --> 2427.38] And we can identify them by, let's say, taking a hash, which is uniquely specifying this specific binary and say that this consists of other components. |
[2427.52 --> 2431.80] And those components also have this unique ID, maybe some kind of hashes. |
[2431.80 --> 2438.40] So that means that if you change anything, even a smaller bit, you will get totally different binary. |
[2439.12 --> 2444.70] And you also have this specific set of components that it was built from. |
[2445.10 --> 2452.68] And when you take software companies that are running these binaries then, and then it turns out that there is one specific library that has vulnerability. |
[2452.68 --> 2458.68] How can you figure out where are those old components that are vulnerable? |
[2459.86 --> 2469.22] And by just taking the software bill of material information and by just scanning it, what is actually running in the production, you can very quickly identify vulnerable components. |
[2469.44 --> 2470.64] And then this, fix this. |
[2471.06 --> 2479.10] Because there were attacks where actually until now people may not know that their software that they are running is vulnerable. |
[2479.10 --> 2486.38] And this executive order is actually saying that you should have this software bill of material so that you can trace this information. |
[2487.04 --> 2494.30] And when we talk about immutable ledgers, you can also store this information in a secure way. |
[2494.36 --> 2501.00] So that if it is persisted and database has given you the proof, then you can rely on this information. |
[2501.36 --> 2503.22] You can rely on the fact that it was not changed. |
[2503.22 --> 2519.24] Because maybe there would be an attack that someone goes into your database and your production environment changes some kind of libraries and then attacks also the database that stores information about this bill of material relations, the relations between packages, how you find this. |
[2519.70 --> 2523.12] And immutability here protects you that you can rely on this information. |
[2523.12 --> 2534.74] So if we're talking about sort of one of the recent vulnerabilities in Log4j, for example, that made, you know, basically the rounds a few weeks ago, if I wanted to find out, okay, I'm running Java software. |
[2535.14 --> 2539.84] Am I running the version of Log4j that was susceptible to that vulnerability? |
[2540.54 --> 2546.38] With the software bill of materials, I can find out exactly, okay, do I have this specific version anywhere in my infrastructure, right? |
[2546.38 --> 2556.26] And then with something like immutability, an attacker that is leveraging this vulnerability couldn't go and change the software bill of material in immutability. |
[2556.60 --> 2564.60] They couldn't say you're not really running the vulnerable software by changing the software bill of materials in immutability because you'd have to convince the clients that that wasn't true, right? |
[2564.78 --> 2567.38] That change was true, whatever it is that we're changing. |
[2567.38 --> 2568.22] Yes, exactly. |
[2568.38 --> 2582.84] And actually, that is what is the base for the Code Notary, the company that is building immutability, the base of their financial, let's say, base that there is this Code Notary cloud that is using immutability to actually store this information. |
[2583.38 --> 2591.44] Because it looks like even if you don't have to, if you're not obliged to have this software bill of material, then it's still good to have this information. |
[2591.44 --> 2604.50] Because Log4J came out a few months ago, and it was a very critical vulnerability where you could execute a code by just sending, in many cases, some packet to the server. |
[2605.42 --> 2610.18] And we know that there will be more vulnerabilities like that in the future. |
[2610.60 --> 2615.04] So it's better to right now be prepared and to start creating this software bill of materials. |
[2615.54 --> 2619.60] And when such vulnerability will happen, to quickly find it. |
[2619.80 --> 2621.20] Okay, cool, cool. |
[2621.20 --> 2631.76] Very briefly, does running immutability, is that process markedly different from, say, managing your traditional RDBMS or traditional key value store? |
[2632.26 --> 2633.62] All things being equal, right? |
[2633.64 --> 2641.02] Do I have to do more or less than I would need to, say, run a Postgres server or a Redis server or something like that? |
[2641.06 --> 2644.80] Just run Docker image or download binary and run it and that's it. |
[2644.94 --> 2645.54] And then run it. |
[2645.68 --> 2646.22] Yeah, yes. |
[2646.34 --> 2647.54] So the beauty of Go, right? |
[2647.80 --> 2648.52] That's the beauty of it. |
[2648.56 --> 2649.28] Got your executable. |
[2649.28 --> 2659.12] And depending on the amount of data you are dealing with, it will require some operational procedures like doing a compaction of the index. |
[2659.12 --> 2665.00] But there is some already, this is already implemented in UDB, for instance. |
[2665.08 --> 2672.90] But this is for reducing the space that is required for indexing because the index itself is an append-only data structure. |
[2672.90 --> 2679.20] So there is an operational procedure to automatically compact the index. |
[2679.66 --> 2682.44] That is one of the things to take into account. |
[2683.16 --> 2688.44] And the other is to be aware that you cannot fully the clients that are using. |
[2688.44 --> 2695.46] So if you try to revert to another backup, the clients will comply about that. |
[2695.46 --> 2714.80] Hey there, it's Jared again. |
[2715.06 --> 2716.72] Have you heard about Changelog++? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.