Project

General

Profile

Actions
Copy link

Bug #13077

closed

remote-cert-tls client set in configuration regardless of Client Certificate Key Usage Validation option (after server restart only!)

Added by Michael Ruder over 2 years ago. Updated over 2 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
amd64

Description

Regardless of the newly introduced setting "Client Certificate Key Usage Validation", the remote-cert-tls client ends up in the configuration if the OpenVPN server instance is restarted (via Status=>OpenVPN or other means).

However when saving the configuration from VPN=>OpenVPN (after changing anything, for instance only the log level) the line is not there, unless the option is ticked.

Someone else noticed this, but it was turned down as the root cause probably was not identified there: #13056

Tested with pfSense 2.6.0 on AMD64.

Related issues

Has duplicate Regression #13056: OpenVPN ``remote_cert_tls`` option does not behave correctly when enabled and later disabledResolvedViktor Gurov

Actions
Actions
Copy link
 #1

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Rejected

There is no code that treats that option differently in the way you describe and I cannot reproduce this as stated. You have something else in your configuration or setup causing this, not a bug. Keep the discussion on the forum until/unless something actionable can be identified and reproduced there.

Actions
Copy link
 #2

Updated by Viktor Gurov over 2 years ago

  • Has duplicate Regression #13056: OpenVPN ``remote_cert_tls`` option does not behave correctly when enabled and later disabled added
Actions
Copy link
 #3

Updated by Viktor Gurov over 2 years ago

  • Status changed from Rejected to Duplicate

Duplicate of #13056

Actions
Copy link

Also available in: Atom PDF