[BUG] IsNfcRestricted needs to be invalidated

[virot]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

IsNfcRestricted cache is not invalidated efter SetIsNfcRestricted(true) is run.

Expected Behavior

The cache for IsNfcRestricted should be invalidated

Steps To Reproduce

var yubiKey = YubiKeyDevice.FindAll().First();
yubiKey.SetIsNfcRestricted(true);
yubiKey.IsNfcRestricted

https://github.com/virot/YubiKeyTests/blob/main/RestrictNFC/Program.cs

Version

1.12.1

Version

5.7.1

Anything else?

No response

[DennisDyallo]

Hi @virot
Yes, this is a known limitation of the SDK in the state it is in right now and I have myself found myself wanting this functionality. None of the properties behave in the way you ask, i.e. having the properties updated after the commands have been issued. The way it works now it simply issues the commands and doesn't update the YubiKeyDevice. One would have to reopen the connection (which reads the DeviceInfo anew). Having this done automatically would likely require a larger effort in the caching and the listeners.

As for priority, this will likely take a back seat to implementing the remaining 5.7 features. I bring it to our manager and circle back here to give you updates if any.

Thanks for your continued support in making the SDK great.