Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#70095 - [ca-certificates-mozilla] Certificate poblem makes it impossible to restore packages from MS

Attached to Project: Arch Linux
Opened by Sergio Tridente (TioDuke) - Saturday, 20 March 2021, 18:25 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 21 March 2021, 09:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 14
Private No

Details

Description:
It is impossible to do a dotnet restore due to a known problem with Microsoft certificates not being trusted. The explanation for this problem can be found in the following link : https://github.com/NuGet/Announcements/issues/49 . Debian and Ubuntu have already issued a fix.

Additional info:
* package version(s) 3.63
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce: do a dotnet restore
This task depends upon

Comment by loqs (loqs) - Saturday, 20 March 2021, 18:28 GMT Comment by Sergio Tridente (TioDuke) - Saturday, 20 March 2021, 21:15 GMT
Unfortunately, [2] and [3] do not solve the issue for me as it did not for many people.
Comment by loqs (loqs) - Saturday, 20 March 2021, 21:44 GMT
If you downgrade ca-certificates-mozilla to 3.62-1 can you then execute dotnet restore?
You could also try locally installing the "VeriSign Universal Root Certification Authority" certificate.
Comment by Sergio Tridente (TioDuke) - Saturday, 20 March 2021, 22:38 GMT
Yes downgrading to 3.62 allows to execute dotnet restore without problems.

Can you point me to any ressource that explains how to locally install a certificate, please?
Comment by loqs (loqs) - Saturday, 20 March 2021, 23:00 GMT
With ca-certificates-mozilla 3.62-1 installed you should have /etc/ssl/certs/VeriSign_Universal_Root_Certification_Authority.pem
Copy that into the /etc/ca-certificates/trust-source/anchors/ directory then update to ca-certificates-mozilla 3.63-1 which will run update-ca-trust extract.

For more details see https://man.archlinux.org/man/update-ca-trust.8
Comment by Sergio Tridente (TioDuke) - Saturday, 20 March 2021, 23:01 GMT
Thank you
Comment by Luca Weiss (z3ntu) - Saturday, 03 April 2021, 12:31 GMT
Linking an "announcement" from NuGet: https://github.com/NuGet/Announcements/issues/56
Comment by loqs (loqs) - Monday, 05 April 2021, 19:17 GMT
https://github.com/NuGet/NuGet.Client/pull/3979 does apply to dotnet-core 5.0.4.sdk104 but it needs to be built with ca-certificates-mozilla 3.62-1.
Could you test that? I can supply built packages if it helps.
Comment by loqs (loqs) - Thursday, 15 April 2021, 14:18 GMT
Please try dotnet-sdk 5.0.5.sdk202-1 and ca-certificates-mozilla 3.63-1 without the additional "VeriSign Universal Root Certification Authority" certificate.
I assume the nuget package is also affected?
Comment by Gabriel Cainã (bieel1503) - Thursday, 15 April 2021, 18:52 GMT
The issue is fixed for me using the latest release '5.0.5.sdk202-1'. Thank you very much.

Loading...