letsencrypt

In all of our current uses of os.umask or filesystem.umask, we always temporarily set it to a different value and then restore it using a try/finally block. I expect this pattern to continue.

Because of that, why don't we create a simple function in certbot.util that can be used as a context manager to set umask to a value and restore it to its previous value when exiting the with blo

Checklist

• Dependencies installed
• No typos
• Searched existing issues and docs

Issue Description

When using the RateLimiter Middleware with a rate between 0 and 1 all events will be rejected instead of applying the specified rate. E.g.: e.Use(middleware.RateLimiter(middleware.NewRateLimiterMemoryStore(0.5)))

I am not saying that it is a common use case to have

Information

Browser Info

Details

Description

The translation for "Copy a base64 string of the compressed config" will revert to English after clicked. Also, the "Copied" text isn't translatable.

Steps to reproduce

Scroll down to Download section and "click on the Copy a base64 string of the compressed config" link.

Inspired by this reddit thread

We currently hardcode a pod security context when we create acmesolver pods:

https://github.com/cert-manager/cert-manager/blob/33c7c298b19364d66f6b3f23de7796b4b5c635ee/pkg/issuer/acme/http/pod.go#L176-L181

This enforces RunAsNonRoot which is a sane default given