<html><head></head><body><div class="ydp7ee4e587yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">From what I researched, KeypassXC is the app for Windows, Mac and Linux, and KeepassXD is for Android. If Syncthing is also used, the ecosystem could operate entirely without a Cloud account. The database could also be stored as the original or a copy on USB media, which would make it available to any device as long as you have the USB storage with the database on it at hand. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">KeypassXC and KeypassXD use the same database format, but reading with KeypassXD from an SD Card can be complicated by file system issues. (SD Cards use a DOS (FAT) format, which often can't be read by modern Android without going through some hoops.)</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">KeypassXC and KeypassXD looks like a fairly complete solution, with the database stored on some sort of modern USB storage like a flash drive. An Android phone would also need to be able to connect the flash drive to USB-C, which is trivial these days. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Compatibility issues between Google and Microsoft implementations of passkeys are not the fault of the standards people. Those companies are not using the standards suggested by the FIDO Alliance, but proprietary variations. The fault is with them, not the Alliance. There is in fact only one standard officially recommended for passkeys. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">-- Bob Primak </div><div dir="ltr" data-setdir="false"><br></div>
</div><div id="yahoo_quoted_9948118506" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, October 17, 2024 at 01:46:31 AM EDT, Drew King via LCTG <lctg@lists.toku.us> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv7002085028"><div>
<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 clear="none">
</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 clear="none">
</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 clear="none">
</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 clear="none">
</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 clear="none">
</font></p>
<p><br clear="none">
</p>
<p><font size="5">Drew</font><br clear="none">
</p>
<div id="yiv7002085028yqt06809" class="yiv7002085028yqt1305243282"><div class="yiv7002085028moz-cite-prefix">On 10/17/2024 1:13 AM, Rich Moffitt
wrote:<br clear="none">
</div>
<blockquote type="cite">
</blockquote></div></div><div><div id="yiv7002085028yqt31187" class="yiv7002085028yqt1305243282"><div>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><br clear="none">
</div>
</div>
<br clear="none">
<div class="yiv7002085028gmail_quote">
<div dir="ltr" class="yiv7002085028gmail_attr">On Wed, Oct 16, 2024, 10:04 PM
Drew King via LCTG <<a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:lctg@lists.toku.us" target="_blank" href="mailto:lctg@lists.toku.us" class="yiv7002085028moz-txt-link-freetext">lctg@lists.toku.us</a>>
wrote:<br clear="none">
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="yiv7002085028gmail_quote">
<div style="padding-bottom:1px;">
<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 clear="none">
</p>
<p><a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://support.google.com/accounts/answer/13548313?hl=en&sjid=13375659196123546943-NA">https://support.google.com/accounts/answer/13548313?hl=en&sjid=13375659196123546943-NA</a></p>
<p><br clear="none">
</p>
<p><br clear="none">
</p>
<p><img alt="" width="1197" height="653"></p>
<div>-- <br clear="none">
Drew King <br clear="none">
<br clear="none">
<br clear="none">
</div>
<div id="yiv7002085028m_5783206719160869362m_-3868915287918397107DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br clear="none">
<table style="border-top:1px solid rgb(211,212,222);"><tbody><tr><td colspan="1" rowspan="1" style="width:55px;padding-top:13px;"><a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"><img alt="" style="width:46px;min-height:29px;" width="46" height="29"></a></td><td colspan="1" rowspan="1" 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 rel="nofollow noopener noreferrer" shape="rect" target="_blank" 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);">www.avast.com</a></td></tr></tbody></table>
<a rel="nofollow noopener noreferrer" shape="rect" href="#m_5783206719160869362_m_-3868915287918397107_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"> </a></div>
</div>
===============================================<br clear="none">
::The Lexington Computer and Technology Group Mailing List::<br clear="none">
Reply goes to sender only; Reply All to send to list.<br clear="none">
Send to the list: <a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:LCTG@lists.toku.us" target="_blank" href="mailto:LCTG@lists.toku.us" class="yiv7002085028moz-txt-link-freetext">LCTG@lists.toku.us</a>
Message archives: <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="http://lists.toku.us/pipermail/lctg-toku.us/" class="yiv7002085028moz-txt-link-freetext">http://lists.toku.us/pipermail/lctg-toku.us/</a><br clear="none">
To subscribe: email <a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:lctg-subscribe@toku.us" target="_blank" href="mailto:lctg-subscribe@toku.us" class="yiv7002085028moz-txt-link-freetext">lctg-subscribe@toku.us</a>
To unsubscribe: email <a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:lctg-unsubscribe@toku.us" target="_blank" href="mailto:lctg-unsubscribe@toku.us" class="yiv7002085028moz-txt-link-freetext">lctg-unsubscribe@toku.us</a><br clear="none">
Future and Past meeting information: <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="http://LCTG.toku.us">http://LCTG.toku.us</a><br clear="none">
List information: <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="http://lists.toku.us/listinfo.cgi/lctg-toku.us" class="yiv7002085028moz-txt-link-freetext">http://lists.toku.us/listinfo.cgi/lctg-toku.us</a><br clear="none">
This message was sent to <a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:rich@richmoffitt.org" target="_blank" href="mailto:rich@richmoffitt.org" class="yiv7002085028moz-txt-link-freetext">rich@richmoffitt.org</a>.<br clear="none">
Set your list options: <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="http://lists.toku.us/options.cgi/lctg-toku.us/rich@richmoffitt.org" class="yiv7002085028moz-txt-link-freetext">http://lists.toku.us/options.cgi/lctg-toku.us/rich@richmoffitt.org</a><br clear="none">
</blockquote>
</div></div>
<div class="yiv7002085028moz-signature">-- <br clear="none">
Drew King
<br clear="none">
<br clear="none">
<br clear="none">
</div>
</div></div><div class="yqt1305243282" id="yqt27172">===============================================<br clear="none">::The Lexington Computer and Technology Group Mailing List::<br clear="none">Reply goes to sender only; Reply All to send to list.<br clear="none">Send to the list: <a shape="rect" ymailto="mailto:LCTG@lists.toku.us" href="mailto:LCTG@lists.toku.us">LCTG@lists.toku.us</a> Message archives: <a shape="rect" href="http://lists.toku.us/pipermail/lctg-toku.us/" target="_blank">http://lists.toku.us/pipermail/lctg-toku.us/</a><br clear="none">To subscribe: email <a shape="rect" ymailto="mailto:lctg-subscribe@toku.us" href="mailto:lctg-subscribe@toku.us">lctg-subscribe@toku.us</a> To unsubscribe: email <a shape="rect" ymailto="mailto:lctg-unsubscribe@toku.us" href="mailto:lctg-unsubscribe@toku.us">lctg-unsubscribe@toku.us</a><br clear="none">Future and Past meeting information: <a shape="rect" href="http://LCTG.toku.us" target="_blank">http://LCTG.toku.us</a><br clear="none">List information: <a shape="rect" href="http://lists.toku.us/listinfo.cgi/lctg-toku.us" target="_blank">http://lists.toku.us/listinfo.cgi/lctg-toku.us</a><br clear="none">This message was sent to <a shape="rect" ymailto="mailto:bobprimak@yahoo.com." href="mailto:bobprimak@yahoo.com.">bobprimak@yahoo.com.</a><br clear="none">Set your list options: <a shape="rect" href="http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com" target="_blank">http://lists.toku.us/options.cgi/lctg-toku.us/bobprimak@yahoo.com</a><br clear="none"></div></div>
</div>
</div></body></html>