News for hackers. Stuff that matters.
Re:Pin is Australia’s first all-in-one payment API by Cogito on Thursday June 07, 2012 @09:28AM (#4078895)
This was exactly what I thought as well.

Using an HTTPS connection is all well and good, but it is not enough. HTTPS is susceptible to man in the middle attacks [1], and securing the params with a pre-shared secret key is essential.

The extra cost in 'complexity' is really far outweighed by the (warranted) extra security.

[1] http://www.thoughtcrime.org/software/sslstrip/

Re:Pin is Australia’s first all-in-one payment API by asharp on Thursday June 07, 2012 @10:50AM (#4079249)
Would you mind elaborating?

ssltrip requires a valid root ca, or an ssl library that doesn't check the signing chain. After using it though, the parameters are unencrypted and so can simply be sniffed.

Are you attempting to reencrypt the parameters with another key? If so then why run that through https?

Re:Pin is Australia’s first all-in-one payment API by Aqua_Geek on Thursday June 07, 2012 @11:41AM (#4079525)
> Are you attempting to reencrypt the parameters with another key? If so then why run that through https?

I think they are talking about generating a hash from all of the parameters in the request + a secret, pre-shared key. Doing so prevents MITM attacks from changing the parameters.

IIRC, Amazon does this (among many others).

Re:Pin is Australia’s first all-in-one payment API by jbrendel on Thursday June 07, 2012 @01:03PM (#4080063)
Exactly. Have a look here for some information on how to do this: http://www.thebuzzmedia.com/designing-a-secure-rest-api-with...
Re:Pin is Australia’s first all-in-one payment API by Bjoern on Friday June 08, 2012 @01:43AM (#4082875)
This article also inspired me to lockdown my own API I designed, its really good advice. The question is only, they wanted to provide a very simple interface, what is the right trade-off security vs. developer UI?