undefined | Better HN

0 pointsantirez13y ago0 comments

I think that actually some kind of get-request-seed request for each request is needed before every call for maximum security. The server will create an entry in the database with an expire set to a given time (for instance 5 minutes, so that flooding the server with get-request-seed will not fill it).

When the request "seed" is used, it gets removed from the list of active seeds, so it can not be used again.

There is still a man in the middle attack:

1) The attacker intercepts our request, send it to the server, and reply to the real client with an error code. 2) This will force the real client to send the request again, this time the attacker will not interfere with the request.

The result is that the request was performed two times instead of one.

0 comments

1 comments · 1 top-level

wolfeidau13y ago

After some consideration I would probably err on the side of caution and either use something like IPSEC AH (Authenticated Header), or build a session key exchange protocol using something akin to it's two phase approach, or even just perform HTTPS based request to exchange session keys.

This session key could then be incorporated into each of the HMAC signatures and would be refreshed on a regular basis similar to how IPSEC does it.

I have used AH in the passed for log data which required the receiver to verify the source for auditing purposes, but this was quite some time ago, these days most systems just either use SSL or IPSEC with ESP.

Reinventing the wheel is probably not the best idea in this case.

Will add a note on this to my blog post for completeness.

For more information on IPsec see http://en.wikipedia.org/wiki/IPsec

j / k navigate · click thread line to collapse