News for hackers. Stuff that matters.
Re:Why does your API still use HTTP Basic Auth? by rb2k_ on Thursday April 18, 2013 @05:54AM (#5569666)
The main problem isn't the response, the problem is that on the initial request, the insecure password will be sent in plaintext.
Re:Why does your API still use HTTP Basic Auth? by barredo on Thursday April 18, 2013 @07:25AM (#5569915)
But that's not the problem of the API provider. If you explain that you only allow HTTPS and someone makes an HTTP on an unsecured connection, well...
Re:Why does your API still use HTTP Basic Auth? by smtddr on Thursday April 18, 2013 @07:40AM (#5569975)
Oh but it IS the problem with the provider. Or rather, it will be when some crazy PR storm hits the interwebz with "$YOURCOMPANYNAME leaked passwords!" when someone comes up with some clever way to hack/manipulate traffic with XSS or something. I was able to fetch private authtokens of a Wii game because port 80 was open on one of nintendo's servers(I assume it's there to test in plain text and just didn't close it later) and I was able to fool the software into using port 80 instead of port 443. That wouldn't have worked if port 80 was closed.
Re:Why does your API still use HTTP Basic Auth? by barredo on Thursday April 18, 2013 @09:48AM (#5570544)
Makes total sense. Thanks
Re:Why does your API still use HTTP Basic Auth? by burrows on Thursday April 18, 2013 @07:46AM (#5569987)
Pretending that your customers won't make mistakes?

Sounds insecure.

Re:Why does your API still use HTTP Basic Auth? by drivebyacct2 on Thursday April 18, 2013 @06:35AM (#5569789)
Isn't this sort of issue basically only going to happen during development or such?