<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Keep it short!<br><br><div id="AppleMailSignature" dir="ltr"><div><span style="font-size: 13pt;">Roxanna I. Cieplinska</span></div><div><span style="font-size: 13pt;">M: + 1 (415) 412-7699</span></div><div><span style="font-size: 13pt;"><br></span></div><div><span style="font-size: 13pt;">Sent from my iPhone</span></div></div><div dir="ltr"><br>On Mar 22, 2019, at 5:50 PM, Michael Thomas <<a href="mailto:mike@mtcc.com">mike@mtcc.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p><span style="color: rgb(29, 33, 41); font-family: Helvetica,
Arial, sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">I know it's a
little tangential, but it's a huge operational issue for network
operations too. Have any NANOG folks been paying attention to
webauthn? i didn't know about until yesterday, though i wrote a
proof of concept of something that looks a lot like webauthn in
2012. The thing that is kind of concerning to me is that there
seems to be some amount of misconception (I hope!) that you need
hardware or biometric or some non-password based authentication
on the user device in the many write ups i've been reading. i
sure hope that misconception doesn't take hold because there is
nothing wrong with *local* password based authentication to
unlock your credentials. i fear that if the misconception takes
hold, it will cause the entire effort to tank. the issue with
passwords is transmitting them over the wire, first and
foremost. strong *local* passwords that unlock functionality is
still perfectly fine for many many applications, IMO.</span></p>
<p><span style="color: rgb(29, 33, 41); font-family: Helvetica,
Arial, sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">Which isn't
to say that hardware/biometric is bad, it's just to say that
they are separable problems with their own set of tradeoffs.
NANOG folks sound like prime examples of who should be using 2
factor, etc. But we don't want to discourage, oh say, Epicurious
to implement webauthn to get to my super-secret recipe box
because they don't think people will buy id dongles.<br>
</span></p>
<p><span style="color: rgb(29, 33, 41); font-family: Helvetica,
Arial, sans-serif; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">Mike<br>
</span></p>
</div></blockquote></body></html>