Re: Google signin

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: Google signin
Date: 2017-07-13 18:54:27
Message-ID: F4BC327D-2304-4C9C-8541-A0F2AF0E66E2@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

> On 12 Jul 2017, at 16:52, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> On Wed, Jul 12, 2017 at 4:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>
> I don't mind reducing barriers to entry when we can, but recent experience
> says that there has to be some barrier :-(
>
> Definitely. But unless we want to whitelist email providers (and exclude google), we already have that problem, and I don't think this is actually maknig it any worse.

I don’t think this will change anything for malicious users, but will make it
easier for legitimate ones. When implementing this at $job-1 we didn’t see any
change re scammers/spammers, they are on top of these sorts of barriers already
(others are needed).

cheers ./daniel

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2017-07-13 19:18:46 Re: Google signin
Previous Message Magnus Hagander 2017-07-13 18:53:14 Re: Google signin