dotnet
/
core
зеркало из https://github.com/dotnet/core.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Correct version numbers for 8.0 and 9.0 (#9505)

This commit is contained in:
Jeff Handley 2024-09-14 15:53:20 -07:00 коммит произвёл GitHub
Родитель e0ff1a1b67
Коммит eef549e888
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: B5690EEEBB952194
2 изменённых файлов: 4 добавлений и 4 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

4
release-notes/8.0/known-issues.md
Просмотреть файл

@ -24,7 +24,7 @@ The `CopyWithPrivateKey` methods that combine a certificate with its associated
Callers of these methods on macOS 15 ("Sequoia") will receive a `CryptographicException`, specifically `Interop+AppleCrypto+AppleCommonCryptoCryptographicException: The specified item is no longer valid. It may have been deleted from the keychain.` The `dotnet dev-certs https` command relies on `CertificateRequest.CreateSelfSigned` and fails with this error.
This issue is addressed in the upcoming .NET 6.0.34 release, scheduled for release in October 2024.
This issue is addressed in the upcoming .NET 8.0.10 release, scheduled for release in October 2024.
### Root Cause
@ -32,6 +32,6 @@ macOS 15 uses a different status code to indicate a key is not in a Keychain tha
### Workarounds
If you have not already upgraded to macOS 15 from a prior version and use .NET, you are not impacted by this issue. If you are planning to upgrade to macOS 15, the workaround is to upgrade to .NET 6.0.34 (scheduled for October 2024) prior to upgrading to macOS 15.
If you have not already upgraded to macOS 15 from a prior version and use .NET, you are not impacted by this issue. If you are planning to upgrade to macOS 15, the workaround is to upgrade to .NET 8.0.10 (scheduled for October 2024) prior to upgrading to macOS 15.
Loading a certificate and its associated private key from a PKCS#12/PFX are not affected. If you are using an application that supports loading a certificate (and associated private key) by either PFX or PEM, converting your PEM contents to PFX - and updating configuration appropriately - may unblock you.

4
release-notes/9.0/known-issues.md
Просмотреть файл

@ -71,7 +71,7 @@ The `CopyWithPrivateKey` methods that combine a certificate with its associated
Callers of these methods on macOS 15 ("Sequoia") will receive a `CryptographicException`, specifically `Interop+AppleCrypto+AppleCommonCryptoCryptographicException: The specified item is no longer valid. It may have been deleted from the keychain.` The `dotnet dev-certs https` command relies on `CertificateRequest.CreateSelfSigned` and fails with this error.
This issue is addressed in the upcoming .NET 6.0.34 release, scheduled for release in October 2024.
This issue is addressed in the upcoming .NET 9.0.0-rc2 release, scheduled for release in October 2024.
### Root Cause
@ -79,6 +79,6 @@ macOS 15 uses a different status code to indicate a key is not in a Keychain tha
### Workarounds
If you have not already upgraded to macOS 15 from a prior version and use .NET, you are not impacted by this issue. If you are planning to upgrade to macOS 15, the workaround is to upgrade to .NET 6.0.34 (scheduled for October 2024) prior to upgrading to macOS 15.
If you have not already upgraded to macOS 15 from a prior version and use .NET, you are not impacted by this issue. If you are planning to upgrade to macOS 15, the workaround is to upgrade to .NET 9.0.0-rc2 (scheduled for October 2024) prior to upgrading to macOS 15.
Loading a certificate and its associated private key from a PKCS#12/PFX are not affected. If you are using an application that supports loading a certificate (and associated private key) by either PFX or PEM, converting your PEM contents to PFX - and updating configuration appropriately - may unblock you.