#11611: obfs2/obfs3 AES counter initialization is incorrect.
---------------------------+-----------------
Reporter: yawning | Owner: asn
Type: defect | Status: new
Priority: normal | Milestone:
Component: Obfsproxy | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
---------------------------+-----------------
Comment (by asn):
Hm, thanks for catching this.
PyCrypto increments the counter by one for each use, right? If yes, I
don't see a big problem with switching `allow_wraparound` to `True`.
OTOH, maybe for other protocols, where the IV is not derived from the
protocol, the current behavior of bailing on wraparound is more sane.
--
Ticket URL:
<https://trac.torproject.org:443/projects/tor/ticket/11611#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
