Am 13.03.20 um 17:59 schrieb Lev Stipakov:
> From: Lev Stipakov
>
> With NCP and deferred auth, we perform cipher negotiation and
> generate data channel keys on incoming push request, assuming that auth
> succeeded. With async push, when auth succeeds in between push requests,
> we send push rep
Is it possible to get an estimate on a timeline for this fix being released?
Duo has a few customers that have been impacted by this and, while we have
provided them with workarounds in the meantime, they are asking for updates on
when this will be fixed. I also expect more customers will be imp
I forgot to add trac ticket to the commit message, so maybe @cron2
could do it, assuming v2 won't be needed.
Trac ticket with (lots of) context:
https://community.openvpn.net/openvpn/ticket/1259
pe 13. maalisk. 2020 klo 18.59 Lev Stipakov (lstipa...@gmail.com) kirjoitti:
>
> From: Lev Stipakov
>
From: Lev Stipakov
With NCP and deferred auth, we perform cipher negotiation and
generate data channel keys on incoming push request, assuming that auth
succeeded. With async push, when auth succeeds in between push requests,
we send push reply immediately.
The code which generates data channel
