Eric Chiang

I've started an implementation here that appears to work: https://github.com/go-piv/piv-go/pull/85 Will finish up when I get the chance. Likely won't be before this weekend.

Note that Yubico doesn't sell older keys so I can't buy test hardware for this. https://www.yubico.com/store/

6302 is odd. It should be 63c2. I can send a fix anyway though. https://cardwerk.com/smart-card-standard-iso7816-4-section-5-basic-organizations/#table14

#64 fixes the "blocking pin: verify pin: smart card error" message

Yep I'm not surprised this only works with YubiKeys since it's the only thing I've tested against. Much of the spec logic is ported directly from the ykpiv C codebase....

#51 now marks the smartcard context as exclusive so other applications that try to access the card will fail instead of hang. Did a little looking into SCardGetStatusChange to see...

Releasing the smart card context can already be done by calling YubiKey.Close(), right? It's probably better for applications to define what "idle" is instead of this package. https://pkg.go.dev/github.com/go-piv/piv-go/piv?tab=doc#YubiKey.Close On a...

If anyone wants to add a client option to opt into SCARD_SHARE_SHARED I'm happy to review. https://github.com/go-piv/piv-go/blob/v1.8.0/piv/piv.go#L135

@FStelzer, @rajnikant12345 started a PR here to allow shared connections: https://github.com/go-piv/piv-go/pull/100 There's an upstream proposal to allow key erasure in the Go runtime that might be interesting to you as...

Mind expanding on what the change would look like to this package? I'm testing on 10.15.4 and haven't had any issues :)