All,
See $SUBJECT. :)
https://www.suse.com/releasenotes/s390x/SUSE-SLES/15-SP1/
Please (please) read the release notes. There are lots of changes in
this service pack.
Mark Post
--
For LINUX-390 subscribe / signoff / archive
We have a couple of top level domains in the company but not all of them are
supported by those that process certificate requests. I don't know if and to
what extent there is a name constraint, if I try to get a certificate for
they simply reject it because it's not the "correct"
domain name.
Hi,
Hopefully everyone was able to take advantage of early-bird pricing for
their registration and are setting up your schedules. Consider chairing a
session (or more) for the LVM program. If you're going to attend one of
these sessions anyway, you're in the perfect position to help out the
progra
Which means you’re not going to be a CA with all the rights, privileges,
and responsibilities applying thereto, so don’t worry about It.
It sounds like they have a commercial signing certificate which has name
constraints, and your domain names aren’t in scope. That’s weird.
Regards,
Alan Altma
Hi Philipp,
That sounds like we could just ignore CRL/OCSP entirely. So we could then just
create the certificates for our servers without additional tasks.
Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen
Flight Forum 3000 5657 EW Eindhoven
-Original Me
Indeed we do have a company CA in place. But they don't (or rather will not)
support our server domain name. So any request to our company CA to process a
certificate request is denied. That's why I would like to enroll my own root CA
and sign the certificates myself. Indeed the public root cert
