Am 28.06.16 um 23:36 schrieb Steffan Karger: > Pushes AES-256-GCM when a connection client advertises IV_NCP=2, and > supports serving connections to clients with different data channel > cipher configuration simultaneously. > > v2: > * Update manpage > * Add Changes.rst entry > > v3: > * Do not regenerate keys if the client sends a second pull request > * Don't postpone key generation if client has no IV_NCP support > > v4: > * rebase on client-side NCP v4 > ACK from me aswell.
Arne
