While Themis can apparently build against OpenSSL 3.0 without errors, there is something not quite right with the way we use OpenSSL API and some unit tests fail. OpenSSL 3.0 is not a fully support cryptographic engine yet, so let's play it safe and explicitly request OpenSSL 1.1.
When publishing the updated formula it would be nice to bump the revision to 1 so that people having previous default revision 0 will know that this is a viable upgrade. I have (hopefully) taught the templating script to accept a new, optional parameter --revision which can be used to set this value automatically.
I'm not sure how exactly that's handled so I'll leave it to @shadinua vOv
While Themis can apparently build against OpenSSL 3.0 without errors, there is something not quite right with the way we use OpenSSL API and some unit tests fail. OpenSSL 3.0 is not a fully support cryptographic engine yet, so let's play it safe and explicitly request OpenSSL 1.1.
When publishing the updated formula it would be nice to bump the
revisionto 1 so that people having previous default revision 0 will know that this is a viable upgrade. I have (hopefully) taught the templating script to accept a new, optional parameter--revisionwhich can be used to set this value automatically.I'm not sure how exactly that's handled so I'll leave it to @shadinua vOv