Christian Hohnstädt

Probably fixed with #366 (Not Responding after upgrade)

Created the branch xca-240-ossl3 with commit f5ac099e948ea354deac75ff9fa09d51453476e1 as fixup for 2.4.0. However, the deprecation warnings will remain, until I drop early Qt5 and openssl 1.1.1 support. Please close this issue...

For security reasons, the OCSP responder should be separated from the XCA GUI. Actually, there is a sample OCSP implementation in OpenSSL. It is only necessary tho access the XCA...

It defines the Extended Key Usage table content. But please send me the files from that directory, because If understood correctly, they were the culprit of the observed error (even...

What is the observed behavior when opening `\wsl%\Ubuntu\my-path\my-database.xdb` (Error message, nothing, crash, hang) Is it possible to import PEM items from the WSL?

Did you install XCA via homebrew or via my DMG? At least the DMG variant should not have external dependencies: $ otool -L xca.app/Contents/PlugIns/sqldrivers/libqsqlmysql.dylib | grep mariadb @executable_path/../Frameworks/libmariadb.3.dylib (compatibility version...

No, currently there are no plans to support CT/SCT in the near future. (To be honest: I'm not very familiar with this topic, yet) However, pull requests are always welcome.

XCA expects for every public key a private key object to be available on the token. This is used when required for signing. https://hohnstaedt.de/xca-doc/html/smartcard.html#key-management-on-the-token It is of course possible to...

> configure: WARNING: Qt pkg-config failed, using fallback defaults ( -lQtCore -lQtGui ) indicates the problem... After the 2.4.0 release I dropped the qt4 support. If compiling worked in the...

It is pretty undocumented. There is only the detailed commit message 22966937de709c0aeff8638fe4c4078480887cd9 Otherwise there are only the openssl specials `email:copy` / `issuer:copy` as described in https://www.openssl.org/docs/man1.1.1/man5/x509v3_config.html