Quick q, since I've been away from this so long: Where/how does one get specifics on CVE reports? I can understand if access is restricted to avoid making vulnerabilities too easy to exploit, but presumably there is some way to get the analysis so one can isolate/fix/test...
(Feel free to lmgtfy me if I'm missing the obvious. It _is_ 3AM here.)
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
On Aug 2, 2022 10:29 AM, Vladimir Sitnikov <sitnikov.vladi...@gmail.com> wrote:
> I'm happy to share that, I've been successful to run XalanJ smoke>tests on latest XalanJ codebase.Nice to hear that.>It seems that, I've solved the running tests hurdle, for XalanJ.Could you please clarify which modifications have you put to make it run?Do you execute the tests in CI?>releasing new version on XalanJIt is worth releasing an updated version to fix BCEL CVE.Vladimir
