Richard Levitte

So here are some options: 1. Choose *one* build system: - there's the current one - there's the cmake proposal: #10902 - there's the meson proposal (this issue) - while...

On the subject of NIDs in libssl, I find that I have a change of heart as long as they're kept internal to libssl (and libcrypto, of course). I think...

On the subject of TLS-SIGALG parameter names and descriptions, the recent conversations make it quite apparent that there's a bit of confusion. This is understandable, 'cause it *is* confusing with...

Regarding my proposal, it may be that OIDs aren't interesting, *if* an OBJ and NID can be created for just a (short) name (no oid). `OBJ_create()` doesn't currently support that,...

> So, if NIDs without ASN1_OBJECT (OID) was made possible, that would remove the burden of adding them in parameters, and still support getting a fetchable name from a NID....

> Some specific questions to see whether I understood things right: When you state > > > Y if "sigalg-name" isn't provided > > you mean "Y if "sigalg-name" does...

New commits noted. I'm currently on vacation for the rest of this year, as most of my colleagues. I'm personally interested, though, so will probably look from that standpoint some...

> @t8m Could you please revise the tag "hold: needs tests"? The tests exist and are available for review at [baentsch#1](https://github.com/baentsch/openssl/pull/1). This is in my own repo as I'm not...

So, I didn't do much with this during my vacation. I'll do a deeper dive today.

Nothing stops anyone from making a separate provider that provides this. In fact, there could be a separate project producing a provider with algorithms that haven't been accepted in the...