Skip to content

eMudhra CA bundle fix - #134

Open
ricci-mwangela wants to merge 1 commit into
mainfrom
emudhra-ca-bundle-update
Open

ricci-mwangela wants to merge 1 commit into
mainfrom
emudhra-ca-bundle-update

Conversation

@ricci-mwangela

Copy link
Copy Markdown

The ruby:3.4.9-alpine3.22 base image was last built in April 2026 and ships ca-certificates-bundle 20260413, which still trusts the eight compromised eMudhra intermediate certificates. The image connects to the incident test hosts when it should refuse them.

Alpine fixed this in ca-certificates-bundle 20261020-r0 and cut point releases on 21 October 2026:
https://alpinelinux.org/posts/Alpine-3.21.9-3.22.7-3.23.7-3.24.3-released.html

ruby:3.4.11-alpine3.24 was rebuilt on that base and carries the new bundle.

Verified inside the built amd64 image: wget and the http gem both reject dv-g3b-emudhra and dv-g3b-aaa-emudhra .we-have-a-problem.com with a certificate error, and ws.postcoder.com still connects. Rubocop and rspec pass.

The ruby:3.4.9-alpine3.22 base image was last built in April 2026 and
ships ca-certificates-bundle 20260413, which still trusts the eight
compromised eMudhra intermediate certificates. The image connects to the
incident test hosts when it should refuse them.

Alpine fixed this in ca-certificates-bundle 20261020-r0 and cut point
releases on 21 October 2026:
https://alpinelinux.org/posts/Alpine-3.21.9-3.22.7-3.23.7-3.24.3-released.html

ruby:3.4.11-alpine3.24 was rebuilt on that base and carries the new
bundle.

Verified inside the built amd64 image: wget and the http gem both
reject dv-g3b-emudhra and dv-g3b-aaa-emudhra .we-have-a-problem.com with
a certificate error, and ws.postcoder.com still connects. Rubocop and
rspec pass.
@ricci-mwangela
ricci-mwangela requested a review from a team as a code owner October 22, 2026 16:32

@davidrapson davidrapson left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small question about version and noting that Ruby 3.4.12 is also out but approving so you can make those changes without re-review.

Comment thread lib/version.rb
# frozen_string_literal: true

VERSION = "4.4.0"
VERSION = "4.5.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be 4.4.1 or 4.5.0?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4.5.0 was released in May 12 https://github.com/citizensadvice/postcoder/releases/tag/v4.5.0 so I went with 4.5.1. Is the version set in lib/version.rb the same as release tag?

Comment thread Dockerfile
@@ -1,4 +1,4 @@
FROM ruby:3.4.9-alpine3.22 AS base
FROM ruby:3.4.11-alpine3.24 AS base

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New image not been published yet, not sure on the timeline we could wait then incorporate it into this PR docker-library/ruby#531

@davidrapson

Copy link
Copy Markdown

Actually mind updating https://github.com/citizensadvice/gotenberg-docker/blob/main/.github/CODEOWNERS whilst we are here, and bundling #133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants