https://bz.apache.org/bugzilla/show_bug.cgi?id=69481
--- Comment #3 from Steve Newbold <[email protected]> --- (In reply to Joe Orton from comment #2) > Thanks a lot for testing this out! > > 1) If you're using the RHEL httpd rather than testing upstream sources it > would be better to report issues in RHEL Jira directly. > https://issues.redhat.com/secure/CreateIssue!default.jspa > > 2) Can you try by using the PKCS#11 URI support instead directly? > > remove `SSLCryptoDevice pkcs11` > add `SSLCertificateFile pkcs11:token=rhel8` assuming that URI is sufficient > to select bot Hi Joe, Thank you for helping! I have a teammate with a RHEL ticket open, 03998844. (In reply to Joe Orton from comment #2) > Thanks a lot for testing this out! > > 1) If you're using the RHEL httpd rather than testing upstream sources it > would be better to report issues in RHEL Jira directly. > https://issues.redhat.com/secure/CreateIssue!default.jspa > > 2) Can you try by using the PKCS#11 URI support instead directly? > > remove `SSLCryptoDevice pkcs11` > add `SSLCertificateFile pkcs11:token=rhel8` assuming that URI is sufficient > to select bot Thank you Joe, I really appreciate the help. 1. We have a ticket open with RHEL, 03998844, we are using the standard RHEL yum httpd packages. 2. I tried "SSLCertificateFile pkcs11:token=rhel8", and "SSLCertificateFile pkcs11:token=rhel8;object=POC" and "SSLCertificateFile pkcs11:token=rhel8;object=POC;pin-value=RedHat#137" All without the `SSLCryptoDevice pkcs11`. I will say that I'm also getting some additional errors from the systemctl status, jpeg attached. We weren't aware that mod_ssl would support a pkcs11 token natively. When I ran the first command in the list above, it prompted for the token password, and seemed to connect. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
