Neil Horman
Neil Horman
ugh, thats right, we don't have a way to fetch the context from the loaded config. I think what you need to do is, in CONF_modules_load_file, after the call to...
barring that, is there a better way to avoid having to set a hard coded limit for maxmem here that you can think of?
Would it be a reasonable solution to augment OSSL_LIB_CTX_load_config such that in addition to calling CONF_modules_load_file_ex, we add an additional call to NCONF_new_ex and NCONF_load, storing the resultant pointer in...
I'd be ok with that, but I presume that would block progress on this issue, until such time as this is resolved (more than a year away). That would be...
Well, I suppose I'll leave that to the reporter to answer, @randombit how critical is this for you? As to the interim fix, I think its arguably not that worrysome...
@paulidale @levitte @t8m thoughts on the above proposal?
@levitte is this still relevant?
no response, marking as inactive, to be closed at the end of 3.4 dev barring further input
is this still an issue on openssl 3.3? If so, can you please attach the csr that you are using to reproduce this problem?
no response, marking as inactive, to be closed at the end of 3.4 dev barring further input