Skip to main content

Search complete. 14 mentions across 10 episodes found for "SHA-1".

Sep 10, 2026

Len NgoGUEST
20:17
So this chip is FIPS compliant.
Len NgoGUEST
20:21
It can do HMAC SHA-1.
Len NgoGUEST
20:24
It can do OTP.
Len NgoGUEST
20:26
It can do GP.
W. Curtis PrestonHOST
11:44
Is it the case that given that this project has been running for 15 years and given the fact that they have to support, for lack of a better word, so many different systems that they have to do this password for every different system that they support, Can we assume that they haven't gotten very far in terms of length of passwords?
Mike SaylorGUEST
12:06
Doing some research on the Rainbow Tables project, their hashing activities include LM, NTLM, so Landman, NTLandman, MD5, SHA-1, and they're currently only up to password length of 10 characters.
Mike SaylorGUEST
12:23
And having done all of that, the database is currently at just over 20 terabytes.
Mike SaylorGUEST
12:28
20 terabytes of text file.
Mike SaylorGUEST
12:31
They've yet to really expand that.
Mike SaylorGUEST
12:34
Let's see.
Mike SaylorGUEST
12:34
Common hashes, MD5 SHA-1, SHA-256, and SHA-512
W. Curtis PrestonHOST
12:42
is
Tim de HerreraGUEST
56:08
And it's really not the shape of what you would want it to be because of two reasons.
Tim de HerreraGUEST
56:14
First of all, it's just the practical reason of Git uses SHA-1.
Tim de HerreraGUEST
56:19
for its hashes right now.
Tim de HerreraGUEST
56:21
It does have SHA-256 support, but SHA-1 is still the most common.
Tim de HerreraGUEST
56:27
And that is just not a cryptographically secure algorithm, which just means that in the simplest possible sense, there are mathematically feasible attacks where you could replace content without changing the hash, right? In terms of how practical that is for an actual attack, it's still probably not very likely, but it's nonetheless, it's not something security-minded people are very happy about, first of all.
Tim de HerreraGUEST
56:53
But the other reason is because Git signing is attached to the commit boundary, and we're actually only needing to work one level lower than that at the tree.
Bobby CapucciHOST
27:59
J. Deduplicate prior to production.
Bobby CapucciHOST
28:03
To the extent that exact duplicate documents based on MD5 or SHA-1 hash values at the document level reside within the party's dataset, each party is only required to produce a single copy of a responsive document so long as there is a data field which identifies each custodian who had a copy.
Bobby CapucciHOST
28:23
In addition, documents may be deduplicated in such a way as to eliminate earlier or incomplete chains of emails and produce only the most complete iteration of an email chain so long as there is a data field that identifies each custodian who had a copy.
Bobby CapucciHOST
28:40
4.
Eddie Montes TravisHOST
32:04
On September 22, chaos for anyone who didn't prepare.
Eddie Montes TravisHOST
32:08
All legacy cryptography, algorithms like SHA-1 for signatures or RSA-1024 keys, are officially banned for federal and financial sector transactions.
Marylyn Lee TrotterHOST
32:18
Banned.
Marylyn Lee TrotterHOST
32:18
Wow.
AmitHOST
4:26
Git is essentially a content addressable data store.
AmitHOST
4:29
Every blob, tree, and commit is keyed by an SHA-1 hash of its contents.
YuvalHOST
4:35
That sounds like it would map perfectly to a distributed key value store.
YuvalHOST
4:38
You use the SHA-1 as the key, and the actual object as the value.
YuvalHOST
4:43
That could provide a clean way to scale out.
AmitHOST
4:45
It sounds elegant, but it falls apart in practice.
Chris BrandoHOST
18:18
I mean, they were gonna put under crypto, right? So that tells you that they didn't really understand UUIDs.
Chris BrandoHOST
18:24
They also, you know, were like, "SHA i- SHA-1 is insecure." And it's like, not for this use case.
Chris BrandoHOST
18:30
It's broken in a very particular use case that's over there.
Chris BrandoHOST
18:33
This is, this is a different one, which also is why it shouldn't go under crypto.
Ellen BoehmGUEST
21:11
We've been building them into our products so that we can issue a post-quantum certificate that is based around this new math.
Ellen BoehmGUEST
21:22
And so from what we've seen, that is... yes, I guess you could maybe relate it to how we migrated things in the past from like SHA-1 to SHA-2.
Ellen BoehmGUEST
21:32
It's kind of a similar, and I've heard my CTO talk about this, that took decades.
Ellen BoehmGUEST
21:37
So now if we're talking about migrating RSA or ECC, which is today's classical algorithms, pretty solid, right? But not when the PQC computer has that capability.
Ellen BoehmGUEST
21:11
We've been building them into our products so that we can issue a post-quantum certificate that is based around this new math.
Ellen BoehmGUEST
21:22
And so from what we've seen, that is... yes, I guess you could maybe relate it to how we migrated things in the past from like SHA-1 to SHA-2.
Ellen BoehmGUEST
21:32
It's kind of a similar, and I've heard my CTO talk about this, that took decades.
Ellen BoehmGUEST
21:37
So now if we're talking about migrating RSA or ECC, which is today's classical algorithms, pretty solid, right? But not when the PQC computer has that capability.
Eddie Montes TravisHOST
47:38
Option A: Enable data compression to optimize speed and maintain support for legacy RC4 cipher suites to ensure maximum backwards compatibility.
Eddie Montes TravisHOST
47:46
Option B: Restrict all network connections to the TLS 1.0 protocol utilizing SHA-1 hashing algorithms.
Marylyn Lee TrotterHOST
47:53
Option C: Enforce TLS 1.2 as the absolute minimum baseline, require full support for TLS 1.3, strictly utilize RSA 2048 or ECDSA P256 cryptographic keys, and absolutely disable all PLS data compression.
Marylyn Lee TrotterHOST
48:08
Or option D, route the heavy video stream over unencrypted HTTP protocols to conserve bandwidth, reserving TLS encryption exclusively for the final payment gateway.

We value your privacy

We use cookies to understand how you use our platform and to improve your experience. Click “Accept All” to consent, or “Decline non-essential” to opt out of non-essential cookies. Read our Privacy Policy.