Re: IQ Handling vulnerabilities
Thijs Alkemade <[email protected]>
| Newsgroups | gmane.ietf.xmpp |
|---|---|
| Message-ID | <[email protected]> |
On 10 feb. 2014, at 18:15, Joe Hildebrand (jhildebr) <[email protected]> wrote: > On 2/7/14 8:13 AM, "Joe Hildebrand (jhildebr)" <[email protected]> wrote: > >> I have a couple of ludicrous s2s attacks on mind, but more important I >> think is doing what >> >> Mobile/terse. DYAC. > > Yes, well that was even more terse than normal. I was going to say > something about generating less-guessable IDs that don't eat up much > entropy. For example: > > start = sha1(crytpo_rand()) > start+1 = sha1(start) > > would probably do nicely. Uhm. Maybe this email is missing a line again, but if you use those values as 'id's directly, they will not be unpredictable at all, as anyone who receives an <iq/> can generate the rest of the chain. However, if you make sure the 'id' values are only half the hashes, it should be unpredictable unless an attacker is willing to spend an insane amount of work. So: start = sha1(crytpo_rand()) start+1 = sha1(start) ... id1 = start[0:10] id2 = start+1[0:10] … Thijs _______________________________________________ xmpp mailing list [email protected] https://www.ietf.org/mailman/listinfo/xmpp
signature.asc
(application/pgp-signature, 841 B)
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJS+SewAAoJELRGwhIrI4PEDt4QAMRBMkD3NN/mUck965IN83fR GsuNLActUYxxOjz3EOpNZYwfp7d/U0KeoZH+EdiyDHRmjsTRqAy8oMZ+twJ/YFq2 cW7ffCBUu+NCLy5SL/rdWS92b9RuU+p6fZLXLVgSFxeGroxK5FGCofJyHt/xtDPp 6cFr/pI+Trkm5q62pHl08XV9AJ2Zfxq8PY1KN+R8KEgEUQBjBeLUoe0McYgCTaJs 1/+xlD/MUuOFBHelAVA0rp+U65WGkCyPWWpGK0mNpaTql/nnHV6Vb6RGYnc6fQUm OvjQLE7wLJoUYzRk5IAuuj56YjyYKdXRhBWMpDElW86O5l9Ty+6x5tckrRpCHxCP k7jLeMYK5capa/rR4IH0edMsDR05vIjb30TzglR/rLabt8WcZo80kpElBAUetXGp lFZ42llrdXVdCOe8MpRUn6YnxgpmgHgflw51fSRBLsWjdXNzM+Hl+dK9Y4cWiOZ0 /T5kHvX7Iz9zwqQVHPGdqo7MoTbBQcCGphXFCwGfaOlFzW3Hfw3EeHr1MI5FUhb1 ZQ0s4AvNmwlpEJpsg+YTgjmeRk07AgAXE9G2NmjOP979awa4yjLouo/FpdbKIVdb jJULMQKe68cEatkSQvYpofJf5xaPVejEcnWq8/tGEhFT3CX6hPSHmxStcmKDEkHo TDkRg+oLdboTyDtgRTqd =Ntxy -----END PGP SIGNATURE-----