[Nuget.exe Bug]: Package signing using USB eToken Certificate not supported

[Willy-Kimura]

Impact

I'm unable to use NuGet.org

Describe the bug

NuGet package signing using nuegt.exe does not support or recognize cryptographic USB eTokens, only file-based key signing using p12/pfx files. Currently due to this it's literally impossible to upload any of my NuGet packages. The error raised is Key does not exist.

Repro Steps

Simply try using the nuget sign command to sign a package while your USB eToken is connected to your device.

Expected Behavior

The error raised upon trying to sign is Key does not exist.
This is even when the cryptographic USB eToken is connected.

Screenshots

No response

Additional Context and logs

No response

[joelverhagen]

Hey @Willy-Kimura, this sounds like a problem related to nuget sign, a part of our client software, since it is about using a certificate for signing that isn't installed to the local machine store. I am going to move this issue to the NuGet/Home repo where we track client issues. NuGet/NuGetGallery is more for nuget.org specifically.

When you get a signed package, you should be able to extract your public .cer (certificate) file from the sign package and upload it to your NuGet.org account page to allow the upload of the signed package.

[Willy-Kimura]

Sure @joelverhagen

[erdembayar]

It sounds feature request to me, but it's dependent on hardware/driver of usb device.
Probably best way of solving this is talk to vendor created the hardware/driver for usb device. Did you check their forum/website?