From: L A Walsh <cygwin@tlinx.org>
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Can't ssh to cygwin after switching sign-in to Windows Hello PIN
Date: Mon, 20 Sep 2021 02:59:15 -0700 [thread overview]
Message-ID: <61485B73.1090402@tlinx.org> (raw)
In-Reply-To: <f5btuil39b4.fsf@ecclerig.inf.ed.ac.uk>
On 2021/09/15 12:53, Henry S. Thompson via Cygwin wrote:
> frankly, it seems like a bug, and
> if Microsoft succeeds in moving more people to using PINs for login,
> it will surely begin to bite others...
----
Isn't the idea of using the PIN login to get rid of the use (and the
ability) to use passwords?
I agree with you that it is likely to cause problems, but creating
a block to using a password seems to be intentional.
It's a bit like some of the problems with the 'Oauth' system where
one provider (like google) provides a way to allow you to login to
other sites using your google authentication, but not requiring you
give the "other site" a password. When I first read about it though,
it seemed like the authorization process required web access for
the authorization to be exchanged, but I'm not 100% sure about that.
If it required web-auth, that has its own set of problems.
next prev parent reply other threads:[~2021-09-20 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 22:05 Henry S. Thompson
2021-09-13 17:21 ` Andrey Repin
2021-09-13 20:01 ` Henry S. Thompson
2021-09-15 17:20 ` Henry S. Thompson
2021-09-15 17:58 ` Brian Inglis
2021-09-15 19:53 ` Henry S. Thompson
2021-09-20 9:59 ` L A Walsh [this message]
2021-09-21 10:11 ` Henry S. Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61485B73.1090402@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=ht@inf.ed.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).