Repository navigation
v1.3.5 needs to be signed, tagged and published. #405
Description
v1.3.5 was just released; https://github.com/docker/docker-bench-security/releases/tag/v1.3.5.
The image needs to be signed by Docker, have a :latest and a version tag added to the image and published.
Activity
konstruktoid commentedon Nov 6, 2019
Relates to #329
konstruktoid commentedon Nov 6, 2019
@diogomonica @docker/security?
konstruktoid commentedon Nov 12, 2019
https://github.com/orgs/docker/teams/security/discussions/1
justincormack commentedon Nov 12, 2019
Hmm, Diogo no longer works at Docker. I don't actually know who has access to the signing key (there may be a copy in the safe). @konstruktoid who has done this in the past?
konstruktoid commentedon Nov 12, 2019
Hi @justincormack, that's good to know since he was the creator (4873078) and original maintainer.
He also signed and pushed the images in the past, #138.
konstruktoid commentedon Feb 13, 2020
Any progress @justincormack @docker/security?
illyaMs commentedon Apr 11, 2020
A pity that this issue did not get proper attention during the 5 month since creation.
All recent additions/improvements are not delivered to image consumers, so everyone is using a 1.3.4 version.
We've managed to workaround it by pushing our own image built on latest state of
masterbranch. But that obviously is not a way we'd like to handle (sitting on upstreamdocker/docker-bench-securitywould be way better for obvious reasons).konstruktoid commentedon Apr 11, 2020
I totally agree @illyaMs.
Any progress @justincormack @docker/security?
konstruktoid commentedon May 19, 2020
Monthly reminder, @justincormack.
yaminisridaran commentedon May 21, 2020
@konstruktoid I would like to contribute for this issue to be solved. Can you please guide me
konstruktoid commentedon May 22, 2020
Thanks @yaminisridaran , but this is done by the Docker organization. Previously by Diogo Mónica and now ... someone else. See #405 (comment).
konstruktoid commentedon Jul 7, 2020
Ping @justincormack
konstruktoid commentedon Nov 18, 2020
Ping @justincormack
konstruktoid commentedon Feb 23, 2021
MonthlyYearly reminder.@justincormack
michi88 commentedon Jan 6, 2022
This has caused a lot of time for me to debug (that the latest docker version is not up to date with the sources here). Maybe we should add this to the README until it is resolved?
konstruktoid commentedon Jan 6, 2022
So sorry about that @michi88, I actually thought there was.
I merged #494
martongajarszky commentedon Mar 3, 2022
Hello @konstruktoid,
Will there be a new release of docker-bench?
Running the script from the master branch, states it is version 1.3.6 but it has not been released.
Thank You!
(Btw it is a nice piece of work!)
konstruktoid commentedon Mar 3, 2022
CIS Docker Benchmark v1.4.0 was published yesterday and I'll will update the scripts to match that one, and then tag and release 1.3.6.
I have no idea if there will be an official Docker image. I guess this comment counts as the yearly reminder.
brianonn commentedon Jan 16, 2023
reminder for 2023 :)
docker/docker-bench-security:latestis now just days away from being 4 years oldlast updated: Jan 24, 2019 at 7:48 am
konstruktoid commentedon Jun 12, 2023
I think we just passed 900 workdays 🍰
bignay2000 commentedon Jul 1, 2023
Docker not being able to Docker :)
xsolinsx commentedon Feb 21, 2024
yearly reminder I guess?
satandyh commentedon Jul 17, 2024
You should be kidding o_O.
konstruktoid commentedon Aug 14, 2024
Celebrating 1200 work days 🍰 🍸