From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: conference slides in wiki |
Date: | 2016-04-28 18:37:42 |
Message-ID: | CA+OCxowp011NbRYZB1H0xt71uwdR+1_yRfNaSLm6dGnQUackuQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Thu, Apr 28, 2016 at 7:32 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> On 04/28/2016 11:29 AM, Stefan Kaltenbrunner wrote:
>
>>> I think a reasonable solution would be to allow anyone who has a
>>> community account to be able to edit the wiki. Here is the catch:
>>>
>>> Turn on 2FA
>>>
>>> Spammers (for the most part) are not going to bother trying to get into
>>> the system with 2FA configured. They are after low hanging fruit.
>>
>>
>> what would you use as the second factor?
>
>
> I would use Google Authenticator. It is open source and works on Windows,
> Android, Linux(Chrome), Apple etc...
We've seen them wait out the cool-off period, and take the time to
email us asking to get editor privileges. I don't believe using Google
Authenticator would put them off at all.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Rader, David | 2016-04-28 18:43:46 | Re: Let's get the OpenSCG packages listed on download |
Previous Message | Joshua D. Drake | 2016-04-28 18:32:50 | Re: conference slides in wiki |