News for hackers. Stuff that matters.
Re:HTTP cookies, or how not to design protocols by tptacek on Friday October 29, 2010 @01:29PM (#1848103)
Basic auth is only simpler than cookie auth if you (a) aren't using a modern web stack (ie, you aren't using ASP.NET, J2EE, Rails, Django, &c) and (b) have only a few users.

If either (a) or (b) do not hold, Basic Auth is at least as hard as cookie auth.

Re:HTTP cookies, or how not to design protocols by mike-cardwell on Friday October 29, 2010 @01:49PM (#1848187)
I use HTTP authentication when I want to password protect a bunch of static files, or a third party web app. Using the PAM auth module with Apache is particularly nice. Just drop a few lines in a .htaccess file and it uses your users system credentials, eg /etc/passwd and /etc/shadow.

HTTP Authentication comes in several flavours. I've not done it myself, but I think you can do interesting things to with Kerberos. Good for Intranet systems.

HTTP Authentication does have its places.

Re:HTTP cookies, or how not to design protocols by tptacek on Friday October 29, 2010 @01:58PM (#1848238)
In other words, HTTP Authentication is useful in the same sense as FTP is useful: it's outmoded but sometimes convenient.
Re:HTTP cookies, or how not to design protocols by mike-cardwell on Friday October 29, 2010 @02:02PM (#1848254)
HTTP Authentication is sessionless. In any scenario where you want to protect something without establishing and maintaining a session, it's useful.

The only large public website that I know of which still uses HTTP Authentication though is http://www.123-reg.co.uk/

Re:HTTP cookies, or how not to design protocols by tptacek on Friday October 29, 2010 @02:05PM (#1848261)
What's the browser app scenario in which having a session is a liability, but having a stored HTTP Auth credential isn't?
Re:HTTP cookies, or how not to design protocols by kls on Friday October 29, 2010 @07:43PM (#1849522)
Actually the elimination of server side session reduces distributed application topology significantly. It is far easier to scale a stateless app than it is a statefull app.
Re:HTTP cookies, or how not to design protocols by psadauskas on Friday October 29, 2010 @01:52PM (#1848203)
But if your clients include things that aren't browsers, HTTP Auth is the only acceptable choice.
Re:HTTP cookies, or how not to design protocols by tptacek on Friday October 29, 2010 @01:57PM (#1848235)
That's not true either; you can just do what big API apps do and generate access tokens. Amazon Web Services don't rely on HTTP-Auth.
Re:HTTP cookies, or how not to design protocols by psadauskas on Friday October 29, 2010 @02:22PM (#1848339)
Using curl to access AWS is kind of a pain, since you have to hash the body and your keys into a header. For others, you have to set the token in a header, and it (should) change periodically.

Compare to:

    curl --anyauth --user login:password https://example.com/
Re:HTTP cookies, or how not to design protocols by tptacek on Friday October 29, 2010 @02:26PM (#1848366)
It's a "1 line of Python" pain, true, but it's also significantly more secure. From a cost/benefit perspective, it's an API, a building block of a software development project, and optimizing it for curl-ability doesn't seem like a major win.

But my point is just: HTTP Auth is not the best-practices answer to non-browser web services auth. Both API-key and signed URLs are both competitive (and probably better) options.

Re:HTTP cookies, or how not to design protocols by mjw on Friday October 29, 2010 @04:22PM (#1848868)
What about for SSL-based APIs? it seems a pretty optimal choice for those.
Re:HTTP cookies, or how not to design protocols by tptacek on Friday October 29, 2010 @04:33PM (#1848906)
I don't think it is, for two reasons:

(1) For most large apps, you're not really SSL in the provider's own network, so there's always the cross-app risk if something horrible happens.

(2) It's forcing app-to-app, business-to-business authentication into a username/password mold that doesn't many any real sense; a 128 bit random key (or an SSL client cert) makes more sense anyways.

Against those two problems --- which are marginal, I concede --- HTTP Basic offers... exactly what advantage? I don't see it.