Armijn Hemel
Armijn Hemel
> > `be` > > in 2021, when the only sensible endianness (`le`) is mainstream in hardware > > facepalm Yet the format uses `be`
> Well, found some more files to test with, so I will go back to the drawing board first: > > https://dev.serpentos.com/pool/b/bash/ It seems that `zstd` is not universally supported...
Hm. seems something went wrong when pushing.
https://github.com/charmplusplus/charm4py/blob/fb67656fc0f39773c567fcc4181fbf76429fe5ab/LICENSE
The project license was changed recently to vanilla Apache 2 with LLVM exceptions which is obviously not the license I was talking about. That's this one: https://github.com/charmplusplus/charm/blob/046c0b5b4231a2e2c1dc20e55d7fe02668356b36/LICENSE
In OpenSSL 1.1.x the function OpenSSL_add_all_ciphers was deprecated and replaced with OPENSSL_init_crypto: https://www.openssl.org/docs/man1.1.0/crypto/OpenSSL_add_all_ciphers.html in configure.ac I replaced the OpenSSL_add_all_ciphers line with this: AC_CHECK_LIB([crypto], [OPENSSL_init_crypto], , [have_libcrypto="0"]) then reran autogen.sh and...
I will first need to run a few more tests to see if it actually works as expected before I create a PR. Also, this change will break building with...
All the trace options mentioned will include that data :)
A good start would be to index the ones that VulDB added to CVEs themselves (which I would assume are public). It would not be the full dataset of course.