You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After receiving some keys with data already on them I tried to remove them by revoking the access key and writing over them (I didn't know about tools > delete at the time). Which resulted in the serial number information dissappearing until I delete the config via tools > delete at which point it returned.
This was pretty confusing and irritating as I thought I had borked my key on the first day.
This sounds like the option "API call" under "Serial # Visibility Settings" in the Settings tab is unchecked. If it is the tool can not read the serial number from the key.
I was pointed this way by the support team and it was not turned off (I had previously made sure all the boxes in visibility were ticked). Also I could see the serial numbers then when I went to protected keep protected it removed the serial number information and wouldn't appear after replug/reboot or using in a vm.
I'm struggling to reproduce it after the tools > delete option as I can't apply access codes on Arch, which is another issue I was going to raise after I had delved into the dependencies for the Ubuntu install and see if there is a difference. The pic below is just after creating the config on slot 2.
No offence meant but linux support seems to mean works on Ubuntu.
After receiving some keys with data already on them I tried to remove them by revoking the access key and writing over them (I didn't know about tools > delete at the time). Which resulted in the serial number information dissappearing until I delete the config via tools > delete at which point it returned.
This was pretty confusing and irritating as I thought I had borked my key on the first day.
Firmware: 3.4.6
Distro: Arch
Kernel: 4.4.1-2
Yubi GUI: 3.1.24
The text was updated successfully, but these errors were encountered: