-
-
-
Report trust status (including EV) for multiple trust stores.
See also https://github.com/kirei/catt.
-
At the moment only a single trust store is supported. This is sufficient for basic environments relying only on globally trusted certificate authorities. Though, once custom certificate authorities co…
-
Currently, it seems like that SSH3 only implements self signed certificates, nothing more.
In situations where you get them via Let's Encrypt, it would be nice if it could work out of the box.
-
**Describe the bug**
Things work as expected overall, but I get a warning, both on Mac Intel & Mac Silicon.
```
poetry run sslyze vagrant-$$REDACTED$$:443{192.168.33.14} --certinfo
/Users/th…
thbar updated
2 weeks ago
-
Desire : As part of notation we would like to add publicly trusted codesigning roots as a named trust-store that can be readily used by consumers.
Expected Outcome: An agreed upon source where publ…
-
```
The HTTPS element only supports *trust stores*, not *key stores*.
This is confusing and looks to have been caused by the JSSE storage object used
by KeyManagerFactory and TrustManagerFactory be…
-
**Describe the bug**
UnicodeError is thrown when sslyze parses my system's CA certificate authority list.
Here are the problematic bytes in `ca-bundle.crt`. They are in the file because their CA's…
yrro updated
18 hours ago
-
See the discussion beginning https://github.com/davidben/merkle-tree-certs/issues/80#issuecomment-2252439958. In looking at rebasing MTCs atop this, we realized that MTCs, since it induces many many i…