SHA-1
14
MENTIONS
10
EPISODES
9
PODCASTS
Search complete. 14 mentions across 10 episodes found for "SHA-1".
Sep 10, 2026
Can You Hack a Human? Transhumanism & Implant Tech Explained | Len Noe
L
20:17Len NgoGUEST
So this chip is FIPS compliant.
L
20:21Len NgoGUEST
It can do HMAC SHA-1.
L
20:24Len NgoGUEST
It can do OTP.
L
20:26Len NgoGUEST
It can do GP.
Password Length vs Complexity: Why Longer Always Wins
W
11:44W. Curtis PrestonHOST
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?
M
12:06Mike SaylorGUEST
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.
M
12:23Mike SaylorGUEST
And having done all of that, the database is currently at just over 20 terabytes.
M
12:28Mike SaylorGUEST
20 terabytes of text file.
M
12:31Mike SaylorGUEST
They've yet to really expand that.
M
12:34Mike SaylorGUEST
Let's see.
M
12:34Mike SaylorGUEST
Common hashes, MD5 SHA-1, SHA-256, and SHA-512
W
12:42W. Curtis PrestonHOST
is
Is Tim making the Nix-killer?
T
56:08Tim de HerreraGUEST
And it's really not the shape of what you would want it to be because of two reasons.
T
56:14Tim de HerreraGUEST
First of all, it's just the practical reason of Git uses SHA-1.
T
56:19Tim de HerreraGUEST
for its hashes right now.
T
56:21Tim de HerreraGUEST
It does have SHA-256 support, but SHA-1 is still the most common.
T
56:27Tim de HerreraGUEST
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.
T
56:53Tim de HerreraGUEST
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.
Mega Edition: The USVI Targets Glenn Dubin And Bella Klein In Their Investigation (9/5/26)
B
27:59Bobby CapucciHOST
J. Deduplicate prior to production.
B
28:03Bobby CapucciHOST
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.
B
28:23Bobby CapucciHOST
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.
B
28:40Bobby CapucciHOST
4.
Technology Thursdays: Mobile Hotspot Security and VPN Compliance
E
32:04Eddie Montes TravisHOST
On September 22, chaos for anyone who didn't prepare.
E
32:08Eddie Montes TravisHOST
All legacy cryptography, algorithms like SHA-1 for signatures or RSA-1024 keys, are officially banned for federal and financial sector transactions.
M
32:18Marylyn Lee TrotterHOST
Banned.
M
32:18Marylyn Lee TrotterHOST
Wow.
Chapter 394 - Making Git Scale
A
4:26AmitHOST
Git is essentially a content addressable data store.
A
4:29AmitHOST
Every blob, tree, and commit is keyed by an SHA-1 hash of its contents.
Y
4:35YuvalHOST
That sounds like it would map perfectly to a distributed key value store.
Y
4:38YuvalHOST
You use the SHA-1 as the key, and the actual object as the value.
Y
4:43YuvalHOST
That could provide a clean way to scale out.
A
4:45AmitHOST
It sounds elegant, but it falls apart in practice.
A Modest Proposal Proposal
C
18:18Chris BrandoHOST
I mean, they were gonna put under crypto, right? So that tells you that they didn't really understand UUIDs.
C
18:24Chris BrandoHOST
They also, you know, were like, "SHA i- SHA-1 is insecure." And it's like, not for this use case.
C
18:30Chris BrandoHOST
It's broken in a very particular use case that's over there.
C
18:33Chris BrandoHOST
This is, this is a different one, which also is why it shouldn't go under crypto.
EP 91: Three Years Until Your Encryption Stops Working
E
21:11Ellen BoehmGUEST
We've been building them into our products so that we can issue a post-quantum certificate that is based around this new math.
E
21:22Ellen BoehmGUEST
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.
E
21:32Ellen BoehmGUEST
It's kind of a similar, and I've heard my CTO talk about this, that took decades.
E
21:37Ellen BoehmGUEST
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.
EP 91: Three Years Until Your Encryption Stops Working
E
21:11Ellen BoehmGUEST
We've been building them into our products so that we can issue a post-quantum certificate that is based around this new math.
E
21:22Ellen BoehmGUEST
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.
E
21:32Ellen BoehmGUEST
It's kind of a similar, and I've heard my CTO talk about this, that took decades.
E
21:37Ellen BoehmGUEST
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.
Guarding the Trust: Advanced Cybersecurity - Test Your Knowledge Tuesday
E
47:38Eddie Montes TravisHOST
Option A: Enable data compression to optimize speed and maintain support for legacy RC4 cipher suites to ensure maximum backwards compatibility.
E
47:46Eddie Montes TravisHOST
Option B: Restrict all network connections to the TLS 1.0 protocol utilizing SHA-1 hashing algorithms.
M
47:53Marylyn Lee TrotterHOST
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.
M
48:08Marylyn Lee TrotterHOST
Or option D, route the heavy video stream over unencrypted HTTP protocols to conserve bandwidth, reserving TLS encryption exclusively for the final payment gateway.