ubuntu-docker-images team mailing list archive

[security-team-toolbox-bot@xxxxxxxxxxxxx]

A scan of this rock shows that it was built with packages from the Ubuntu
archive that have since received security updates. The following lists new
USNs for affected binary packages in each rock revision:

Revision r01bc2d15700d (arm64; channels: 9.16-20.04_beta, 9.16-20.04_edge)
 * libgssapi-krb5-2: 5959-1
 * libk5crypto3: 5959-1
 * libkrb5-3: 5959-1
 * libkrb5support0: 5959-1
 * libpython3.8-minimal: 5960-1
 * libpython3.8-stdlib: 5960-1
 * python3.8: 5960-1
 * python3.8-minimal: 5960-1

Revision r8eb7f0a7ae49 (ppc64le; channels: 9.16-20.04_beta, 9.16-20.04_edge)
 * libgssapi-krb5-2: 5959-1
 * libk5crypto3: 5959-1
 * libkrb5-3: 5959-1
 * libkrb5support0: 5959-1
 * libpython3.8-minimal: 5960-1
 * libpython3.8-stdlib: 5960-1
 * python3.8: 5960-1
 * python3.8-minimal: 5960-1

Revision rab559ee6f20e (s390x; channels: 9.16-20.04_beta, 9.16-20.04_edge)
 * libgssapi-krb5-2: 5959-1
 * libk5crypto3: 5959-1
 * libkrb5-3: 5959-1
 * libkrb5support0: 5959-1
 * libpython3.8-minimal: 5960-1
 * libpython3.8-stdlib: 5960-1
 * python3.8: 5960-1
 * python3.8-minimal: 5960-1

Revision rd3d1f73a2286 (amd64; channels: 9.16-20.04_beta, 9.16-20.04_edge)
 * libgssapi-krb5-2: 5959-1
 * libk5crypto3: 5959-1
 * libkrb5-3: 5959-1
 * libkrb5support0: 5959-1
 * libpython3.8-minimal: 5960-1
 * libpython3.8-stdlib: 5960-1
 * python3.8: 5960-1
 * python3.8-minimal: 5960-1

Simply rebuilding the rock will pull in the new security updates and
resolve this. If your rock also contains vendored code, now might be a
good time to review it for any needed updates.

Thank you for your rock and for attending to this matter.

References:
 * https://ubuntu.com/security/notices/USN-5959-1/
 * https://ubuntu.com/security/notices/USN-5960-1/