openSUSE-Leap-16.0-4 moderate SUSE SLFO 1.2 This update for cloud-regionsrv-client fixes the following issues: Update version to 10.5.2 (bsc#1247539) + When an instance fails verification server side the default credentials were left behind requireing manual intervantion prior to the next registration attempt. + Fix issue triggered when using instance-billing-flavor-check due to IP address handling as object rather than string introduced 10.5.0 cloud-regionsrv-client-10.5.2-160000.3.1.noarch.rpm cloud-regionsrv-client-10.5.2-160000.3.1.src.rpm cloud-regionsrv-client-generic-config-1.0.0-160000.3.1.noarch.rpm cloud-regionsrv-client-license-watcher-1.0.0-160000.3.1.noarch.rpm cloud-regionsrv-client-plugin-azure-2.0.0-160000.3.1.noarch.rpm cloud-regionsrv-client-plugin-ec2-1.0.5-160000.3.1.noarch.rpm cloud-regionsrv-client-plugin-gce-1.0.0-160000.3.1.noarch.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.aarch64.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.ppc64le.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.s390x.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.x86_64.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.aarch64.rpm flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-debuginfo-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-debuginfo-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-guestvm-tools-debuginfo-3.1.22-160000.1.1.aarch64.rpm flake-pilot-podman-3.1.22-160000.1.1.aarch64.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.ppc64le.rpm flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-firecracker-3.1.22-160000.1.1.ppc64le.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.ppc64le.rpm flake-pilot-podman-3.1.22-160000.1.1.ppc64le.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.s390x.rpm flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-debuginfo-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-debuginfo-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-guestvm-tools-debuginfo-3.1.22-160000.1.1.s390x.rpm flake-pilot-podman-3.1.22-160000.1.1.s390x.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-3.1.22-160000.1.1.x86_64.rpm flake-pilot-debuginfo-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-debuginfo-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-guestvm-tools-debuginfo-3.1.22-160000.1.1.x86_64.rpm flake-pilot-podman-3.1.22-160000.1.1.x86_64.rpm openSUSE-Leap-16.0-packagehub-1 critical openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.76: * Do not send URLs as AIM input. This is to resolve a privacy concern, around passing urls to AI Mode. Chromium 141.0.7390.65 (boo#1251334): * CVE-2025-11458: Heap buffer overflow in Sync * CVE-2025-11460: Use after free in Storage * CVE-2025-11211: Out of bounds read in WebCodecs Chromium 141.0.7390.54 (stable released 2025-09-30) (boo#1250780) * CVE-2025-11205: Heap buffer overflow in WebGPU * CVE-2025-11206: Heap buffer overflow in Video * CVE-2025-11207: Side-channel information leakage in Storage * CVE-2025-11208: Inappropriate implementation in Media * CVE-2025-11209: Inappropriate implementation in Omnibox * CVE-2025-11210: Side-channel information leakage in Tab * CVE-2025-11211: Out of bounds read in Media * CVE-2025-11212: Inappropriate implementation in Media * CVE-2025-11213: Inappropriate implementation in Omnibox * CVE-2025-11215: Off by one error in V8 * CVE-2025-11216: Inappropriate implementation in Storage * CVE-2025-11219: Use after free in V8 * Various fixes from internal audits, fuzzing and other initiatives Chromium 141.0.7390.37 (beta released 2025-09-24) Chromium 140.0.7339.207 (boo#1250472) * CVE-2025-10890: Side-channel information leakage in V8 * CVE-2025-10891: Integer overflow in V8 * CVE-2025-10892: Integer overflow in V8 chromedriver-141.0.7390.76-bp160.1.1.aarch64.rpm chromium-141.0.7390.76-bp160.1.1.aarch64.rpm chromium-141.0.7390.76-bp160.1.1.nosrc.rpm openSUSE-Leap-16.0-packagehub-1 critical openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.76: * Do not send URLs as AIM input. This is to resolve a privacy concern, around passing urls to AI Mode. Chromium 141.0.7390.65 (boo#1251334): * CVE-2025-11458: Heap buffer overflow in Sync * CVE-2025-11460: Use after free in Storage * CVE-2025-11211: Out of bounds read in WebCodecs Chromium 141.0.7390.54 (stable released 2025-09-30) (boo#1250780) * CVE-2025-11205: Heap buffer overflow in WebGPU * CVE-2025-11206: Heap buffer overflow in Video * CVE-2025-11207: Side-channel information leakage in Storage * CVE-2025-11208: Inappropriate implementation in Media * CVE-2025-11209: Inappropriate implementation in Omnibox * CVE-2025-11210: Side-channel information leakage in Tab * CVE-2025-11211: Out of bounds read in Media * CVE-2025-11212: Inappropriate implementation in Media * CVE-2025-11213: Inappropriate implementation in Omnibox * CVE-2025-11215: Off by one error in V8 * CVE-2025-11216: Inappropriate implementation in Storage * CVE-2025-11219: Use after free in V8 * Various fixes from internal audits, fuzzing and other initiatives Chromium 141.0.7390.37 (beta released 2025-09-24) Chromium 140.0.7339.207 (boo#1250472) * CVE-2025-10890: Side-channel information leakage in V8 * CVE-2025-10891: Integer overflow in V8 * CVE-2025-10892: Integer overflow in V8 chromedriver-141.0.7390.76-bp160.1.1.ppc64le.rpm chromium-141.0.7390.76-bp160.1.1.nosrc.rpm chromium-141.0.7390.76-bp160.1.1.ppc64le.rpm openSUSE-Leap-16.0-packagehub-1 critical openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.76: * Do not send URLs as AIM input. This is to resolve a privacy concern, around passing urls to AI Mode. Chromium 141.0.7390.65 (boo#1251334): * CVE-2025-11458: Heap buffer overflow in Sync * CVE-2025-11460: Use after free in Storage * CVE-2025-11211: Out of bounds read in WebCodecs Chromium 141.0.7390.54 (stable released 2025-09-30) (boo#1250780) * CVE-2025-11205: Heap buffer overflow in WebGPU * CVE-2025-11206: Heap buffer overflow in Video * CVE-2025-11207: Side-channel information leakage in Storage * CVE-2025-11208: Inappropriate implementation in Media * CVE-2025-11209: Inappropriate implementation in Omnibox * CVE-2025-11210: Side-channel information leakage in Tab * CVE-2025-11211: Out of bounds read in Media * CVE-2025-11212: Inappropriate implementation in Media * CVE-2025-11213: Inappropriate implementation in Omnibox * CVE-2025-11215: Off by one error in V8 * CVE-2025-11216: Inappropriate implementation in Storage * CVE-2025-11219: Use after free in V8 * Various fixes from internal audits, fuzzing and other initiatives Chromium 141.0.7390.37 (beta released 2025-09-24) Chromium 140.0.7339.207 (boo#1250472) * CVE-2025-10890: Side-channel information leakage in V8 * CVE-2025-10891: Integer overflow in V8 * CVE-2025-10892: Integer overflow in V8 chromedriver-141.0.7390.76-bp160.1.1.x86_64.rpm chromium-141.0.7390.76-bp160.1.1.nosrc.rpm chromium-141.0.7390.76-bp160.1.1.x86_64.rpm openSUSE-Leap-16.0-openSUSE_Backports_SLE-16.0 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.107: * CVE-2025-11756: Use after free in Safe Browsing (boo#1252013) chromedriver-141.0.7390.107-bp160.1.1.aarch64.rpm chromium-141.0.7390.107-bp160.1.1.aarch64.rpm chromium-141.0.7390.107-bp160.1.1.nosrc.rpm openSUSE-Leap-16.0-openSUSE_Backports_SLE-16.0 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.107: * CVE-2025-11756: Use after free in Safe Browsing (boo#1252013) chromedriver-141.0.7390.107-bp160.1.1.ppc64le.rpm chromium-141.0.7390.107-bp160.1.1.nosrc.rpm chromium-141.0.7390.107-bp160.1.1.ppc64le.rpm openSUSE-Leap-16.0-openSUSE_Backports_SLE-16.0 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.107: * CVE-2025-11756: Use after free in Safe Browsing (boo#1252013) chromedriver-141.0.7390.107-bp160.1.1.x86_64.rpm chromium-141.0.7390.107-bp160.1.1.nosrc.rpm chromium-141.0.7390.107-bp160.1.1.x86_64.rpm