Commit 508bfaf
committed
fix(docker): waive the two Compose advisories the image cannot yet clear
The remaining data-manager scan findings are in the bundled Compose
binary, not in anything this repository builds: 5.5.0 is the newest
official release and both advisories postdate it. They join the eleven
waivers already covering that binary and the Docker CLI, scoped to the
same path and carrying the same expiry, so a newer upstream build has to
replace them rather than the waiver quietly outliving the problem.
The ssh advisory is recorded as critical, but it reaches only callers
that dial over SSH; the data-manager drives Compose against the
bind-mounted socket and sets no DOCKER_HOST.
Also drops the x/crypto pin added to the gtfsclean build a commit ago.
That binary embeds neither module — the findings were always in Compose —
so the pin bought nothing and pushed x/text past the version deliberately
pinned beside it.1 parent 625d605 commit 508bfaf
2 files changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
50 | 50 | | |
51 | 51 | | |
52 | 52 | | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
28 | 27 | | |
29 | 28 | | |
30 | 29 | | |
| |||
0 commit comments