| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Apparently I should have used 2023 despite sharing versions of these
files with several people under this license (and thus permitting them
to redistribute and share with the public). It makes no sense to me,
but shrug.
|
| |
|
|
|
|
|
|
|
| |
These were the last four RFC 3779 things that check_complete.pl x509v3
complained about. I will surely tweak and try to improve a few things
in the coming days, but the pages should now be stable enough that
review efforts will likely not be wasted. Any feedback appreciated.
|
|
|
|
|
|
| |
First RFC 3779 page without a BUG section. It could have one, but I'm
in a lenient mood right now. Maybe it's just that this is bad but not
quite as bad as EVP.
|
|
|
|
| |
Mention a few more bugs and unify manpage descriptions
|
|
|
|
| |
Also note another bug in X509v3_asid_{canonize,is_canonical}(3).
|
|
|
|
| |
Let's just say there's room for improvement...
|
|
|
|
|
| |
Someone clearly didn't actually use much of the code they wrote and exposed
and therefore didn't think it through properly.
|
|
|
|
| |
ASRange and ASIdOrRange
|
| |
|
|
This documents the part of the API that allows building the two
extensions. It is all very complicated and the bug density is
quite high. Surely there's lots of room for improvement, but
I've been sitting way too long on versions of these. I'll never
finish. Let's fix and improve in tree.
|