<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;" text="#000000" bgcolor="#ffd1bb">
<p><font size="5">Correct.</font></p>
<p><font size="5">Right now 99% of the people who have implemented
passkeys have no idea where they are or how to manage them, they
just know that they work somehow.<br>
</font></p>
<p><font size="5">That is one of the reasons why it is a good idea
to use a single platform for the use and implementation of
passkeys. Passkeys are still in flux regarding the way they are
managed because there's no standard for sharing passkey
information between different products. If you're entirely in
an apple ecosystem then you have coordination, but if you want
to use even one Windows computer it throws everything out of
balance because there's no sharing between Windows and Apple. <br>
</font></p>
<p><font size="5">My preference is to have all passkeys stored in my
password manager. Unfortunately, my password manager is not
under management of only one developer or organization.<br>
</font></p>
<p><font size="5">I use an open source password manager on my
desktop platform and on my mobile devices and the developer of
the desktop app and the developer of the mobile app are
different, and they have not coordinated in any way on how to
share and use passkeys.</font></p>
<p><font size="5">KeepassXC supports passkeys on Windows, Linux and
Mac. The information stored in the database however does not
coordinate with Android or Apple mobile devices. Unlike with
BitWarden which develops the desktop app and the mobile app,
Keepass is too open right now. <br>
</font></p>
<p><font size="5">If you use bitWarden on your PC and on your phone,
you can use passkeys and have them all stored inside your
BitWarden database rather than randomly stored in different
places on different devices. Microsoft stores passkeys one way
and Google does it another way. Right now, the best way to
collect all of your pass keys in one place so they can be easily
managed is in a password manager that supports passkeys across
all hardware devices. BitWarden is an example of one company
that provides passKeys across Android, Apple, Windows, Mac, and
Linux.</font></p>
<p><font size="5">Google is trying to make it easy to use passkeys
across Windows and Android by having you store all of your
password information in their browser password manager, which
many people don't want to do.</font></p>
<p><font size="5">The passkey rollout I thought was going to be
clean, but it is not turning out to be that way. The password
manager that I use on my phone, is coded by only one person and
that makes it very difficult for his customers to count on him
to be able to implement passkeys with other open source
developers that have no connection to him.<br>
</font></p>
<p><br>
</p>
<p><font size="5">Drew</font><br>
</p>
<div class="moz-cite-prefix">On 10/17/2024 1:13 AM, Rich Moffitt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALB7WzvJXvpO7yV7wvbW4AE5KvQx+jWmSBgU24XD5CPx+sSpmQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Minor point, but something to keep in mind: you're
not so much deleting the passkeys from the lost device as you
are invalidating the keys stored on that device for use on a
particular service. This also means that if you have passkeys
for 5 different web sites on a single device, you may have to
invalidate the passkeys on each of the 5 sites independently
(unless they all use the same authentication service).
<div dir="auto"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 16, 2024, 10:04 PM
Drew King via LCTG <<a href="mailto:lctg@lists.toku.us"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">lctg@lists.toku.us</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="padding-bottom:1px" text="#000000"
bgcolor="#ffd1bb">
<p>All,</p>
<p>Additional info regarding Passkeys:</p>
<p>This is an article that covers a lot of information and
answers a lot of questions about passkeys. One question
that was asked this morning at the meeting was what
happens if you lose your device that you installed a
passkey on. If somebody has your device and they can log
into it or unlock it then they have your passkeys. This
article covers how to log into your Google account from a
computer and delete passkeys that are on your lost or
stolen device.<br>
</p>
<p><a
href="https://support.google.com/accounts/answer/13548313?hl=en&sjid=13375659196123546943-NA"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://support.google.com/accounts/answer/13548313?hl=en&sjid=13375659196123546943-NA</a></p>
<p><br>
</p>
<p><br>
</p>
<p><img alt="" moz-do-not-send="true" width="1197"
height="653"></p>
<div>-- <br>
Drew King <br>
<br>
<br>
</div>
<div
id="m_5783206719160869362m_-3868915287918397107DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid rgb(211,212,222)">
<tbody>
<tr>
<td style="width:55px;padding-top:13px"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true"><img alt=""
style="width: 46px; height: 29px;"
moz-do-not-send="true" width="46" height="29"></a></td>
<td
style="width:470px;padding-top:12px;color:rgb(65,66,78);font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free.<a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
style="color:rgb(68,83,234)"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">www.avast.com</a></td>
</tr>
</tbody>
</table>
<a
href="#m_5783206719160869362_m_-3868915287918397107_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"
width="1" height="1" rel="noreferrer noreferrer"
moz-do-not-send="true"> </a></div>
</div>
===============================================<br>
::The Lexington Computer and Technology Group Mailing List::<br>
Reply goes to sender only; Reply All to send to list.<br>
Send to the list: <a href="mailto:LCTG@lists.toku.us"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">LCTG@lists.toku.us</a>
Message archives: <a
href="http://lists.toku.us/pipermail/lctg-toku.us/"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.toku.us/pipermail/lctg-toku.us/</a><br>
To subscribe: email <a href="mailto:lctg-subscribe@toku.us"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">lctg-subscribe@toku.us</a>
To unsubscribe: email <a
href="mailto:lctg-unsubscribe@toku.us"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">lctg-unsubscribe@toku.us</a><br>
Future and Past meeting information: <a
href="http://LCTG.toku.us"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">http://LCTG.toku.us</a><br>
List information: <a
href="http://lists.toku.us/listinfo.cgi/lctg-toku.us"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.toku.us/listinfo.cgi/lctg-toku.us</a><br>
This message was sent to <a
href="mailto:rich@richmoffitt.org"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">rich@richmoffitt.org</a>.<br>
Set your list options: <a
href="http://lists.toku.us/options.cgi/lctg-toku.us/rich@richmoffitt.org"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.toku.us/options.cgi/lctg-toku.us/rich@richmoffitt.org</a><br>
</blockquote>
</div>
</blockquote>
<div class="moz-signature">-- <br>
Drew King
<br>
<br>
<br>
</div>
</body>
<lt-container></lt-container>
</html>