NuGet package signing Errors and Warnings
Pages 155
-
LoadingHome
-
Loading[Spec] Deterministic Pack
-
Loading[Spec] Fallback package folders
-
Loading[Spec] MSBuild restore target
-
Loading[Spec] NuGet settings in MSBuild
-
Loading[spec] NuGet.org replication API
-
Loading[Spec] Package download API
-
Loading[Spec] PackageDownload support
-
LoadingAdvanced Search on NuGet.org
-
LoadingAuthor Package Signing
-
LoadingBatch Events
-
LoadingConfig Max Http Request In NuGet
-
LoadingContribute to NuGet
-
LoadingDeprecate packages
-
Loadingdotnet list package
-
Loadingdotnet list package vulnerable
-
LoadingDotnetCliToolReference restore
-
LoadingEnhanced package upload workflow
-
LoadingFilter OData query requests
-
LoadingFull support of LSL
-
LoadingIcons as part of the nupkg
-
LoadingImplemented
-
LoadingIncubation
-
LoadingIsLatest Duplicates
-
LoadingLogging Guidance
-
LoadingMultiple API Keys
-
LoadingMVP Summit 2020
-
LoadingNuGet Account Deletion Workflow
-
LoadingNuGet Client Package Debugging
-
LoadingNuGet Client Test Plan
-
LoadingNuGet Errors and Warnings
-
LoadingNuGet Gallery Test Plan
-
LoadingNuGet Localization Design
-
LoadingNuGet Package Download Plugin
-
LoadingNuGet packages cache management
-
LoadingNuGet Restore Manager
-
LoadingNuGet Restore No Op
-
LoadingNuGet Sign Command
-
LoadingNuGet Verify Command
-
LoadingNuGetizer 3000
-
LoadingNuGetizer Core Features
-
LoadingNuGetizer Core Scenarios
-
LoadingNuGetizer Future Features
-
LoadingNuGetizer Principles
-
LoadingNupkg Metadata File
-
LoadingOrganizations on NuGet.org
-
LoadingPackage Immutability
-
LoadingPackage Markdown Support
-
LoadingPackage README.md support
-
LoadingPackage signing
-
LoadingPackage Sources Diagnostics
-
LoadingPackage Type [Packing]
-
LoadingPackageReference enhancements
-
LoadingPackageReference Specification
-
LoadingPackages.config SHA Validation
-
LoadingPackaging Icon within the nupkg
-
LoadingPlugin Diagnostic Logging
-
LoadingRepository Signatures
-
LoadingRestore errors and warnings
-
LoadingSecret Rotation
-
LoadingSemver 2.0.0 Protocol
-
LoadingSemVer 2.0.0 support
-
LoadingShow outdated packages
-
LoadingSidebar Archive 9_14_2017
-
LoadingSubmitting Bugs and Suggestions
-
LoadingSupport package renames
-
LoadingUpdate Command in Context Menu
-
LoadingUWP Project Json Upgrader
Home
Contributing
Specs
Incubation
Reviewing
- Centrally-managing-NuGet-package-versions
- Package Applicability
- dotnet list package --vulnerable
- Machine-readable output for dotnet list package
- Support Package Renames
- Advanced Search on NuGet.org
Reviewed
Implemented
- Enhanced package upload workflow
- Register package signing certificates
- Organizations on NuGet.org
- 2 Factor Auth for NuGet.org sign in
- Add nuget sources command to the dotnet CLI
- Author Package Signing
- Backporting PC to msbuild restore
- Deprecate packages
- Dotnet list package
- Enable repeatable package restore using lock file
- NuGet Client Package Debugging
- NuGet Package Debugging & Symbols Improvements
- NuGet Package Identity Verification
- NuGet Package Signing Client Policy
- NuGet Sign Command
- NuGet Verify Command
- Storing trusted repository
- Package Signatures Technical Details
- Package signing
- Packages.config SHA Validation
- Packaging Icon, License and Documentation within the nupkg
- Repository Signatures and Countersignatures Technical Specification
- Repository Signatures
- Show outdated packages
- Symbols Package Upload and Delete Workflow
Templates
Clone this wiki locally
This document contains a list of all warnings and errors that may occur during signing, verifying and using signed packages.
Package signing related errors and warnings should be in the following range -
| Log Message Type | Starting Code | Ending Code |
|---|---|---|
| Errors | NU3000 | NU3099 |
| Warnings | NU3500 | NU3599 |
Errors
3000
Issue
Default signature issue
NU3001
Issue
Input error in sign/verify command - In sign command -
- The certificate file is not found.
- The certificate file is not a valid pfx file.
In verify command -
- Package signature is invalid.
- Package is not signed.
NU3002
Issue
Package verification fails due to one of the following -
- Package integrity check failed. The package has been tampered.
- Author signature verification failed.
- Signature does not have a certificate.
- Certificate does not meet the public key requirements.
- Unable to validate signer certificate chain.
NU3003
Issue
Invalid number of matching certificates in sign command -
- Multiple certificates were found that meet all the given criteria. Use the '-CertificateFingerprint' option with the hash of the desired certificate.
- No certificates were found that meet all the given criteria. For a list of accepted ways to provide a certificate, please visit https://docs.nuget.org/docs/reference/command-line-reference
NU3011
Issue
Certificate chain cannot be built for the following cases -
- The timestamp service's certificate chain could not be built for the following certificate -
NU3012
Issue
Certificate not valid in the following cases -
- Author certificate was not valid when it was timestamped.
NU3013
Issue
The certificate's private key cannot be read - The following certificate cannot be used for package signing as the private key provider is unsupported.
NU3014
Issue
Invalid password was provided for the certificate file '<cert_file_path>'. Please provide a valid password using the '-CertificatePassword' option
NU3021
Issue
Timestamp authority response not valid in the following cases -
- Timestamp service's response does not meet the NuGet package signature specification: Timestamp response does not contain a matching response.
- Timestamp service's response does not meet the NuGet package signature specification: Timestamp response does not contain an acceptable hash algorithm.
- Timestamp service's response does not meet the NuGet package signature specification: Timestamp signature contains invalid content type.
- Timestamp service's response does not meet the NuGet package signature specification: Timestamp response contains invalid signature value hash.
- Timestamp service's response does not meet the NuGet package signature specification: Timestamp service's certificate does not contain a valid Enhanced Key Usage for timestamping.
NU3022
Issue
Signed package contains an invalid timestamp -
- The signature contains an invalid timestamp. Detailed log contains more detailed failure.
# Warnings
NU3500
Issue
Default signing warning
NU3501
Issue
Certificate does not build to a trusted root - Signing certificate does not chain to a trusted root.
NU3502
Issue
Signature information unavailable. [Currently not thrown]
NU3521
Issue
No -Timestamper option was provided the signed package will not be timestamped. To learn more about this option, please visit https://docs.nuget.org/docs/reference/command-line-reference