On Sun, 19 Sep 2010 17:12:36 +0200, Michael Snoyman wrote:
> Let me respond to this directly since a number of people have brought this up:
>
> Due to spam reasons we can't trust the email given via an OpenID
> provider in general. For example, it would be trivial for me to create
> an OpenID pro
Let me respond to this directly since a number of people have brought this up:
Due to spam reasons we can't trust the email given via an OpenID
provider in general. For example, it would be trivial for me to create
an OpenID provider for myself, set my email address as and essentially spam them.
On Fri, Sep 17, 2010 at 6:47 PM, Michael Snoyman wrote:
>
> * OpenID. Fixes the extra password problem, but doesn't give us any
> extra information about the user (email address, etc).
>
I have my open id with verisign. https://pip.verisignlabs.com/
Verisign doesn't give me an email address but
OpenID sounds like a plan. I'll probably add OpenID support to
hpaste.org for management over pastes/remembering user details/default
language, tracking annotations of your pastes, etc. We already have an
OpenID Haskell implementation. Programming sites are already using it
(Google, StackOverflow),
* Michael Snoyman [2010-09-17 08:47:02+0200]
> * OpenID. Fixes the extra password problem, but doesn't give us any
> extra information about the user (email address, etc).
This is a popular misconception. As was noted on this thread, many
OpenID provideers may provide you an email or other inform
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/17/10 17:43 , Brandon S Allbery KF8NH wrote:
> On 9/17/10 05:27 , Neil Davies wrote:
>> Why not use kerberos?
> Mind, we use Kerberos heavily around here... but we have the infrastructure
> that uses it. Web application space is *not* something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/17/10 05:27 , Neil Davies wrote:
> Why not use kerberos?
>
> We find it works for us, integrates with web (natively or via WebAuth),
> remote command execution (remctl) and ssh - widely used, scales brilliantly.
1. Kerberos is only authenticatio
Excerpts from Neil Davies's message of Fri Sep 17 05:27:34 -0400 2010:
> Why not use kerberos?
>
> We find it works for us, integrates with web (natively or via
> WebAuth), remote command execution (remctl) and ssh - widely used,
> scales brilliantly.
MIT uses Kerberos and it is quite nice to
Why not use kerberos?
We find it works for us, integrates with web (natively or via
WebAuth), remote command execution (remctl) and ssh - widely used,
scales brilliantly.
Neil
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haske
On Fri, 17 Sep 2010 08:47:02 +0200, Michael Snoyman wrote:
> Hi cafe,
Hi,
> Let me preface this by stating that this is purposely a half-baked
> idea, a straw man if you will. I'd like to hear what the community
> thinks about this.
>
> I mentioned yesterday that I was planning on building haske
On Thu, Sep 16, 2010 at 11:47 PM, Michael Snoyman wrote:
> Hi cafe,
>
> Let me preface this by stating that this is purposely a half-baked
> idea, a straw man if you will. I'd like to hear what the community
> thinks about this.
>
> I mentioned yesterday that I was planning on building haskellers.
On 17 September 2010 15:47, Michael Snoyman wrote:
> Hi cafe,
>
> I mentioned yesterday that I was planning on building haskellers.com.
> The first technicality I considered was how login should work. There
> are a few basic ideas:
>
> * Username/password on the site. But who wants to deal with *a
Hi cafe,
Let me preface this by stating that this is purposely a half-baked
idea, a straw man if you will. I'd like to hear what the community
thinks about this.
I mentioned yesterday that I was planning on building haskellers.com.
The first technicality I considered was how login should work. Th
13 matches
Mail list logo
