The req.pem contents: -----BEGIN CERTIFICATE REQUEST----- MIICbDCCAVQCAQAwJzEUMBIGA1UEAwwLJChob3N0bmFtZSkxDzANBgNVBAoMBnNl cnZlcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKXeMnFZM4+aAtyb YJwau1WLdAFxtlNiLKPZ6WdX0cGyEFeMa9DG+f6R6ZBn6ifwiae8KJmK+maeN5Th +NKKYRvJQaNo5h/62lqJMjuLDZqS9B+WtPmu7ZwWqltIIysmROHOPILGTLnypYNO g48pThDDEM+2WL6FfqB7zFApjVI893tC7q+YW4ZvRvcC+mdasEJY2lrbPZsnPofL l3K/hQRMw04Ta3WpvF1GkNJTCZ+dNo65LCMlSArRzIwvap1OlQV8oRaKVMMIqbR7 WsxOZkwinaDnhyJJcISsemv/dkYqG+lXRGoJUOEl+8kP4bGN4zsLz5EC5v8Eggzm kHc2I4kCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBZmrwQpKqZppdX0x0v3AMm gakW7cBqN99XcltasciDwt0UTIva42DGkNtXSizy40TsNZwPyu7ZRKx6AnRQ4KWY whKZNUXl1VxcctR/7lW5aR58dDTeiCRZRhk6vMfIYVLPlI+GmCvlS+6s9rV48LHx /tn3kHh+dskO7+D1f5xy9/A8oWhRsSurkXREuk9v22dgkgBDTbafszb/4F1V4yQN 6zB7R6UIkzMZ9pVUImV2vjbs2y6bqxes8/t3tQTzfz2P3RfM2LPqgX3nPU80vK/Q SrRacEUzOrinThIZ4Wvv0Mjlg7BLbIdOFJkVerYzZKN8kg4V1N3HNR13iP5EuJuv -----END CERTIFICATE REQUEST----- -----Original Message----- From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> On Behalf Of Michael Wojcik Sent: Saturday, August 21, 2021 1:22 PM To: openssl-users@xxxxxxxxxxx Subject: RE: Need some help signing a certificate request > From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> On Behalf Of > rgordey@xxxxxxxxxxxxxxx > Sent: Saturday, 21 August, 2021 09:48 > Thanks for the comment. I have tried both `/` and `\` with no change. Most or all Windows APIs, and most programs, support the forward slash as a directory separator. The exceptions are mostly the cmd.exe built-ins. > On Sat, Aug 21, 2021 at 09:21 <mailto:rgordey@xxxxxxxxxxxxxxx> wrote > When I type ‘openssl ca -config .\openssl.cnf -in ../server/req.pem > -out We need to see the contents of openssl.cnf. It might also help to have the CSR (req.pem). Since a CSR doesn't contain the private key (the CA should never see the private key), this is safe to share. -- Michael Wojcik
