News for hackers. Stuff that matters.
Re:Pulling GitHub into the Linux kernel process by andrewchambers on Wednesday June 23, 2021 @07:51PM (#27612107)
Yes, but google could easily support per application passwords. They just don't want to... in fact, they used to and removed it.

They could also invest in other ways to make existing workflows work securely instead of imposing their own ones.

Re:Pulling GitHub into the Linux kernel process by oauea on Wednesday June 23, 2021 @08:11PM (#27612271)
Did they remove app passwords? This page is still there https://support.google.com/accounts/answer/185833?hl=en
Re:Pulling GitHub into the Linux kernel process by andrewchambers on Wednesday June 23, 2021 @08:55PM (#27612581)
For me it originally worked flawlessly.

Then I tried to use it again and lots of the menus the support pages referenced were no longer present. It was an endless cycle of broken links and features being hidden deeper and deeper in menus.

If that haven't removed it (I thought they had), it kind of made the intention clear to me.

Re:Pulling GitHub into the Linux kernel process by arp242 on Thursday June 24, 2021 @04:44AM (#27615239)
That's just Google doing their usual best at designing UIs and documenting things. It's like watching your 5-year old do their best "helping" doing housework. Cute, but not actually very helpful.
Re:Pulling GitHub into the Linux kernel process by judge2020 on Wednesday June 23, 2021 @07:55PM (#27612135)
Sounds like oauth, which is an open standard.
Re:Pulling GitHub into the Linux kernel process by jeroenhd on Wednesday June 23, 2021 @08:12PM (#27612276)
OAuth is far from standard in email. Google is the only company I know of that uses it for email.

Per-application passwords are static passwords you generate for special applications. This way, the standard IMAP/SMTP logins will work, but a leaked password does not expose your entire Google account, only the email part. It also allows revocation of one application without re-entering your password on every device.

It works flawlessly for many services, and Google supports/supported it as well. Using it just flags/flagged your account as "insecure" for some reason. Probably because they want you to use their propietary OAuth flow where they have more control over your software.

Re:Pulling GitHub into the Linux kernel process by g_p on Wednesday June 23, 2021 @08:52PM (#27612559)
Microsoft, Yahoo (i.e. OATH) and others also use it, but it has limited adoption beyond the "big giants" of email.

https://docs.microsoft.com/en-us/exchange/client-developer/l...

In a way, server providers prefer it as (in theory) users' long term credentials don't end up stored locally in plain text. A revocable per application token is used instead, and they can trace that back to a specific application or developer registration.

That it trains users it's ok to enter passwords in bespoke web views using abnormal or no clear URL view is a big issue though in my opinion - I've never liked flows that encourage entering passwords into web browsers you didn't open yourself, let alone ones provided by third party software, which can capture anything happening within the app itself.