Closed shawnzhu closed 4 years ago
I triggered a new build and v1.0.0 has been updated. That do the trick?
Yes!
> docker run -it --rm --entrypoint /bin/bash sqitch/sqitch:latest -c 'dpkg -l | egrep \'(e2fsprogs|openssl)\''
ii e2fsprogs 1.44.5-1+deb10u2 amd64 ext2/ext3/ext4 file system utilities
ii libgnutls-openssl27:amd64 3.6.7-4 amd64 GNU TLS library - OpenSSL wrapper
ii openssl 1.1.1d-0+deb10u2 amd64 Secure Sockets Layer toolkit - cryptographic utility
@theory Thank you!
Since it starts to use
debian:buster
insqitch/sqitch:1.0.0
, I've got feedback about security vulnerabilities out of the latest container image:Problems
DSA-4539-3:
CVE-2019-5094
Actual result
So I can not use
sqitch/sqitch:1.0.0
until :point_up: fixes are included.Expectation
Just rebuild container image
sqitch/sqitch:1.0.0
especially it was built over one month ago.