mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #306] update-ca-certificates rehash error (hash table overflow) #197
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#197
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aral on GitHub (Nov 3, 2020).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/306
Encountered with mkcert version 1.4.1.
I’m not entirely sure why this started happening today but I’m going to document it here in case it helps anyone else.
When running my tests (which generate certificate authorities), I started encountering the following error:
Running
sudo update-ca-certifiates -fby itself gave me the same error.Given that it started happening without any other changes, I started wondering if it had to do with the sheer number of mkcert root CAs I had generated while running my tests over however many months/years.
So I tried:
followed by:
And that solved the issue.
The output of that last command informed me that 426 previously-trusted certificates were now removed.
I’m pretty sure most folks won’t run into this unless they’re testing a tool like auto-encrypt-localhost that uses mkcert to generate certificate authorities and certificates and tests them but still, in case anyone does, I hope this issue helps.
Please feel free to close it.
@FiloSottile commented on GitHub (Nov 22, 2020):
Thanks for filing an issue for people to find. Indeed, this seems like a limitation of
update-ca-certifiates. Kind of surprising it would struggle with fewer than a thousand entries, but I guess most people never encounter that.