Hi Tomás, Unfortunately, updating the package to a version with a renewed certificate is not a solution. It merely resets the same 'time bomb' to explode later down the road. It's bad enough that nobody will be able to build a tested ruby-net-smtp@0.3.3 again, at least until Linux can virtualise a wall clock.
Fortunately, it appears that upstream has since added the exact commands needed to regenerate the certificates: <https://github.com/ruby/net-smtp/blob/master/test/net/fixtures/Makefile>. We can generate new ones at build time. I only wonder whether openssl would stall on build machines with insufficient entropy available, or whether that's not an issue. Kind regards, T G-R Sent on the go. Excuse or enjoy my brevity.
