| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-Original-To: | cygwin AT cygwin DOT com |
| Delivered-To: | cygwin AT cygwin DOT com |
| DMARC-Filter: | OpenDMARC Filter v1.4.1 sourceware.org 3E22A3858C60 |
| Authentication-Results: | sourceware.org; |
| dmarc=none (p=none dis=none) header.from=tlinx.org | |
| Authentication-Results: | sourceware.org; spf=pass smtp.mailfrom=tlinx.org |
| Message-ID: | <61485B73.1090402@tlinx.org> |
| Date: | Mon, 20 Sep 2021 02:59:15 -0700 |
| From: | L A Walsh <cygwin AT tlinx DOT org> |
| User-Agent: | Thunderbird 2.0.0.24 (Windows/20100228) |
| MIME-Version: | 1.0 |
| To: | "Henry S. Thompson" <ht AT inf DOT ed DOT ac DOT uk>, |
| "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com> | |
| Subject: | Re: Can't ssh to cygwin after switching sign-in to Windows Hello PIN |
| References: | <f5bwnnla1qa DOT fsf AT ecclerig DOT inf DOT ed DOT ac DOT uk> |
| <74a78044-5ddd-c2f0-1d1b-bdb092a8c2b2 AT SystematicSw DOT ab DOT ca> | |
| <f5btuil39b4 DOT fsf AT ecclerig DOT inf DOT ed DOT ac DOT uk> | |
| In-Reply-To: | <f5btuil39b4.fsf@ecclerig.inf.ed.ac.uk> |
| X-Spam-Status: | No, score=-0.5 required=5.0 tests=BAYES_05, KAM_DMARC_STATUS, |
| SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 | |
| X-Spam-Checker-Version: | SpamAssassin 3.4.4 (2020-01-24) on |
| server2.sourceware.org | |
| X-BeenThere: | cygwin AT cygwin DOT com |
| X-Mailman-Version: | 2.1.29 |
| List-Id: | General Cygwin discussions and problem reports <cygwin.cygwin.com> |
| List-Archive: | <https://cygwin.com/pipermail/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-request AT cygwin DOT com?subject=help> |
| List-Subscribe: | <https://cygwin.com/mailman/listinfo/cygwin>, |
| <mailto:cygwin-request AT cygwin DOT com?subject=subscribe> | |
| Sender: | "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com> |
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. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |