These updates contain no new security fixes beyond what already shipped in 6.0.18 / 7.0.7. If you are not affected by the functional regression described above, you can safely remain on 6.0.18 / 7.0.7. There is no need to install these updates unless you are affected by the functional regression listed at KB5028608. You can download 7.0.8 and 6.0.19 versions for Windows, macOS, and Linux, for x86, 圆4, Arm32, and Arm64. This regression was unintentional and a fix is being offered for affected applications.Īlso documented at. Callers may non-deterministically observe a CryptographicException being thrown by the X509Certificate constructor on those runtimes. NET 6.0.18 and 7.0.7 may fail to import PKCS12 blobs whose private keys are protected by a null password. We learned from customer reports during the week of Jthat. We created a specific exception message with a link to a known issue KB to describe these behavioral changes. The NET 6.0.18 and 7.0.7 updates update added constraints to PFX certificate loading to fix a DoS vulnerability (CVE-2023-29331).
The regression is functional and doesn’t require action on your part unless you are affected by the issue. We have released a second update this month to address a regression in our earlier release (June 13th). This fixes it but I'm not sure what is requiring the aspnet image vs the regular runtime image.June 13th, 2023 2 2 Update - June 22, 2023 I've updated my image to use the aspnet:6.0 image instead to run the service. Why is the runtime:6.0 image having trouble? This is being deployed using docker and the image is built to use the runtime:6.0 like this: FROM /dotnet/runtime:6.0 AS service You can resolve the problem by installing the specified framework and/or SDK. The framework '', version '6.0.0' (圆4) was not found. It was not possible to find any compatible framework version net6 and in my services (not using aspnet), I am getting this error when it tries to start up.
0 kommentar(er)
