Activity log for bug #1931174

Date Who What changed Old value New value Message
2021-06-07 22:34:31 Noah Meyerhans bug added bug
2021-06-07 22:37:18 Noah Meyerhans description Forwarded from https://bugs.debian.org/989575 From the original report: I use "ca-certs" to supply additional certificates. With just one certiticate everything works as expected, however when provided more than one, cloud-init adds them into a single file which causes "openssl rehash" to fail as it expects exactly one certificate per file. As the result programmes using openssl doen not trus certificates issued by provided CAs. The issue was reported against 20.2, but I have confirmed that the behavior is unchanged in 21.2. One possible approach to the solution would be to store each certificate individually in files named something like cloud-init-ca-cert-0.pem, cloud-init-ca-cert-1.pem, etc. Note that this breaks certificate usage only when performing verification using openssl's path-based verification functionality. Since all certificates in /etc/ssl/certs/ are concatenated into /etc/ssl/certs/ca-certificates.pem, that file can still be used to perform file-based verification. (See https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_default_verify_file.html for a description of these two modes, if you're not familiar.) Forwarded from https://bugs.debian.org/989575 From the original report:     I use "ca-certs" to supply additional certificates. With just one certiticate everything works as expected, however when provided more than one, cloud-init adds them into a single file which causes "openssl rehash" to fail as it expects exactly one certificate per file. As the result programmes using openssl doen not trus certificates issued by provided CAs. The issue was reported against 20.2, but I have confirmed that the behavior is unchanged in 21.2. One possible approach to the solution would be to store each certificate individually in files named something like cloud-init-ca-cert-0.pem, cloud-init-ca-cert-1.pem, etc. Note that this breaks certificate usage only when performing verification using openssl's path-based verification functionality. Since all certificates in /etc/ssl/certs/ are concatenated into /etc/ssl/certs/ca-certificates.pem, that file can still be used to perform file-based verification. (See https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_default_verify_file.html for a description of these two modes, if you're not familiar.)
2021-06-08 15:08:41 James Falcon cloud-init: status New Triaged
2021-06-08 15:08:43 James Falcon cloud-init: importance Undecided Wishlist
2023-02-15 04:58:43 Chad Smith cloud-init: status Triaged Fix Committed
2023-02-22 16:52:19 Alberto Contreras cloud-init: status Fix Committed Fix Released
2023-05-12 13:55:41 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/3880