So
> what's the logic behind 4096?"
>
> Regards,
> Ning
> On Friday, March 16, 2018, 10:30:45 AM PDT, Selva Nair
> wrote:
>
>
> Hi,
>
> Apologies in advance if I'm misreading the intent of this patch.
>
> On Fri, Mar 16, 2018 at 12:40 PM, Ning
riday, March 16, 2018, 10:30:45 AM PDT, Selva Nair
wrote:
Hi,
Apologies in advance if I'm misreading the intent of this patch.
On Fri, Mar 16, 2018 at 12:40 PM, Ning Wei via Openvpn-devel
wrote:
> Increase TLS_CHANNEL_BUF_SIZE to 4096. When the build is enabled with
> ENABLE_PKCS
Thank you for reminding this. The reason that I have resent was there was a
typo in the commit comment.
Best regards,Ning
On Friday, March 16, 2018, 9:46:07 AM PDT, Gert Doering
wrote:
Hi,
On Fri, Mar 16, 2018 at 09:40:59AM -0700, Ning Wei via Openvpn-devel wrote:
> Incre
Increase TLS_CHANNEL_BUF_SIZE to 4096. When the build is enabled with
ENABLE_PKCS11, the password field can be 4096. The old size of
TLS_CHANNEL_BUF_SIZE was 2048, which is not enough.
Signed-off-by: Ning Wei
---
src/openvpn/common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
Increase TLS_CHANNEL_BUF_SIZE to 4096. When the build is enabled with
ENABLE_PKCS11, the password field can be 4096. The old size of
TLS_CHANNEL_BUF_SIZE was 2048, which is not enough.
Signed-off-by: Ning Wei
---
src/openvpn/common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
