<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="https://forum.yubico.com/feed.php?f=4&amp;t=2742" />

<title>Yubico Forum</title>
<subtitle>...visit our web-store at</subtitle>
<link href="https://forum.yubico.com/index.php" />
<updated>2017-10-09T19:26:56+01:00</updated>

<author><name><![CDATA[Yubico Forum]]></name></author>
<id>https://forum.yubico.com/feed.php?f=4&amp;t=2742</id>
<entry>
<author><name><![CDATA[Morthawt]]></name></author>
<updated>2017-10-09T19:26:56+01:00</updated>
<published>2017-10-09T19:26:56+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9841#p9841</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9841#p9841"/>
<title type="html"><![CDATA[Re: [Question] Upon too many PIV/Key management failures. Er]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9841#p9841"><![CDATA[
Very nice. Thanks for letting me know.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=1739">Morthawt</a> — Mon Oct 09, 2017 7:26 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[ChrisHalos]]></name></author>
<updated>2017-10-09T19:25:26+01:00</updated>
<published>2017-10-09T19:25:26+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9840#p9840</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9840#p9840"/>
<title type="html"><![CDATA[Re: [Question] Upon too many PIV/Key management failures. Er]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9840#p9840"><![CDATA[
Three attempts to verify the PIN and the PIN is blocked. Three attempts to verify the PUK and the PUK is blocked. At this point the only option is to reset the PIV applet. Management Key is the only thing that can hypothetically be brute-forced, but the person with the management key can't use the certificate that's stored on the YubiKey. They would have to generate a new one to use the key. All scenarios are basically covered on our developer website. Recommend you start with <!-- m --><a class="postlink" href="https://developers.yubico.com/PIV/Introduction/Admin_access.html">https://developers.yubico.com/PIV/Intro ... ccess.html</a><!-- m --><br /><br />There is no way to render the PIV applet completely useless (otherwise lots of customers will experiment, lock the PIV applet permanently, and demand a replacement). This isn't like a basic smart card where you lock it and you have to throw it away and buy another one. There are several other manufacturers that offer those.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=3140">ChrisHalos</a> — Mon Oct 09, 2017 7:25 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Morthawt]]></name></author>
<updated>2017-10-04T18:38:30+01:00</updated>
<published>2017-10-04T18:38:30+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9818#p9818</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9818#p9818"/>
<title type="html"><![CDATA[[Question] Upon too many PIV/Key management failures. Erase?]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2742&amp;p=9818#p9818"><![CDATA[
If someone tries to use certs I have in my PIV, for, code signing say. They try and try and try, I assume it gets locked right? Are there any conditions where the Yubikey will &quot;maliciously&quot; (desired) destroy the key upon too many failures or anything? Or does it just &quot;choose&quot; to deny the usage of the contained keys and rely on the protection of the secure element to hopefully prevent forced physical access to the key information?<br /><br />Clarification would be very helpful to know what is what.<br /><br />Thanks.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=1739">Morthawt</a> — Wed Oct 04, 2017 6:38 pm</p><hr />
]]></content>
</entry>
</feed>