I installed Samba4 and configured it to be domain controller, and it auto generated ca.pem, cert.pem, key.pem.
And now I want to use the same CA of samba to sign the new certificates (maybe generated by easyRSA or OpenSSL).
Can somebody please guide me how to do that (either using easyRSA or OpenSSL)?
The main difficulty is that I have just pem files from samba (not crt and key files), therefore I am not sure how can I do what I want.
- A related question: how can I know if my pem file includes just the certificate or both the certificate and the private key as well? (that point is important to understand my main question as I think). And in case it holds both cert and private key, how can I separate them just to use them conveniently as crt and key files?
What I intend to do is actually using Samba4 AD DC to authenticate OpenVPN using starttls, but for some reason openvpn does not accept that and I think the problem is because of the different ca signiture to the server certs. Any help is really appreciated.
Bad idea:
Version 4.1.21-SerNet-RedHat-11.el7
) ca.pem has only year of validity.ca.pem
- is CA certificate,cert.pem
is AD's certificate andkey.pem
is AD's key,Solution? Do it backwards - use EasyRSA (3.0!) and regererate keys for samba's AD.
Simple:
RFC's 1421 pem x509 certificate file contains only lines like:
RFC's 1421 pem x509 key:
No, samba uses (source What is a Pem file and how does it differ from other OpenSSL Generated Key File Formats?):
Using Easy RSA you will generate (source What is a Pem file and how does it differ from other OpenSSL Generated Key File Formats?):
But you can convert it using OpenSSL by:
So cert .cer .crt A .pem (or rarely .der) format looks like:
And pem defined in RFC 1421
I completely miss sense of this. I don't know what did you read and what signature are you talking about.
I've never seen RFC's 1421 pem certificate with key inside (or with whole keychain), but I believe it'll look like:
I mean one file that contains this lines with hidden by me cryptographic data. I have always two files, one for private key and one with public.