#2797 image-build target does not have a way to specify SSL certificates (or disable SSL)
Closed: Fixed 2 years ago by tkopecek. Opened 3 years ago by lon.

When using koji image-build, a kickstart template and URLs are provided to the process in order to build qcow2 images.

The generated kickstart file contains "repo" lines. In the case that the URLs have certificates which are self-signed or signed by a non-public CA, there is no way to tell Koji:

  • to disable SSL verification (e.g. repo --noverifyssl https://... in the generated kickstart file), or
  • to specify the root CA file to use when verifying the non-publicly signed certificate

I assume that Anaconda has no way to reference a non-public CA's certificate, either.


Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue tagged with: discussion

3 years ago

FYI it's important to delete non-public CAs from images, or we can face some issues like these:

https://www.infoworld.com/article/3008422/security/what-you-need-to-know-about-dells-root-certificate-security-debacle.html
https://www.computerworld.com/article/3008521/security/a-second-dangerous-dell-root-certificate-discovered.html

Even if we don't include the private key for the CA, it's still important that we don't ship images with non-public CAs.

The OSBS project handles this by deleting the files during the build, https://github.com/containerbuildsystem/atomic-reactor/pull/1597

if self._builder_ca_bundle:
    lines.append(f'RUN rm -f /tmp/{self._ca_bundle_pem}')

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.26

2 years ago

Metadata Update from @jcupova:
- Issue tagged with: testing-ready

2 years ago

Metadata Update from @julian8628:
- Issue status updated to: Open (was: Closed)

2 years ago

Metadata Update from @mfilip:
- Issue tagged with: testing-done

2 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #2945 Merged 2 years ago
  • #2860 Merged 2 years ago