Hi, On Mon, Jun 13, 2016 at 11:17:49PM +0200, Steffan Karger wrote: > Pushes AES-256-GCM when a connecting 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 (to also > support clients that do not send a push request)
To me this looks generally OK.
I'll do 3/5 and 4/5 next, but would then ask for a v4 without the
merge/rebase/fix/rewort artefacts we already know about :-)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
