You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Supported Versions
4
4
5
-
Distroless currently tracks debian 12 ([bookworm](https://packages.debian.org/bookworm)) packages.
5
+
Distroless currently tracks debian 12 ([bookworm](https://packages.debian.org/bookworm/allpackages)) and debian 13 ([trixie](https://packages.debian.org/trixie/allpackages)) packages.
6
6
7
7
Debian package versions used for the current build are found in https://github.com/GoogleContainerTools/distroless/blob/main/private/repos/deb. It can be parsed and printed into simple json data by invoking `./knife deb-versions` at the root of this project.
8
8
@@ -11,6 +11,6 @@ Debian package versions used for the current build are found in https://github.c
11
11
If a distroless image you are using contains a CVE or other vulnerability:
12
12
1. ensure you are using a [currently supported image](https://github.com/GoogleContainerTools/distroless#what-images-are-available)
13
13
1. find the appropriate debian security-tracker notice: `https://security-tracker.debian.org/tracker/CVE-XXXX-YYYYY`, for [example](https://security-tracker.debian.org/tracker/CVE-2022-21476).
14
-
1. check if a fix is available for the appropriate debian version in the main/security channels (ex `bookworm`, `bookworm (security)`).
14
+
1. check if a fix is available for the appropriate debian version in the main/security channels (ex `trixie`, `trixie (security)`).
15
15
1. if a fix is not yet available, do not file a bug, track it in your internal tracker until one becomes available.
16
16
1. if a fix is available *and* it has been more than 48 hours, please let the team know by creating an issue and pointing to the CVE or vulnerability disclosure.
0 commit comments