ClearOS Bug Tracker

Main | My View | View Issues | Change Log | Roadmap | Repositories
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0013611ClearOSapp-openvpn - OpenVPNpublic2017-03-09 11:502020-03-27 08:23
ReporterNickH 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version7.3.0 
Target VersionFixed in Version 
Summary0013611: App-openvpn provides no way of disabling certificates
DescriptionOpenVPN provides a certificate security model such that the server never looks at the client certificate or private key when authenticating. Some users disable user/pass access so OpenVPN can run as a service in Windows, so the client automatically connects to ClearOS when it boots up. In this condition, the only way to disable client access us to configure openvpn to use a CRL. ClearOS needs to provide support for this, both in the Certificates app so deleting a certificate makes an entry in the CRL, and in app-users so deleting a user deletes the certificates and creates the entry in the CRL. The basic clients.conf also needs modifying to use the CRL.

There is more discussion and links to openVPN in the following thread: https://www.clearos.com/clearfoundation/social/community/openvpn-deleted-user-still-able-to-connect# [^]
TagsNo tags attached.
Attached Files

- Relationships
related to 0022221closed Add API call to revoke certificates on user deletion 

-  Notes
(0008511)
user2
2018-11-05 20:35

 Since this requires a command line hack, set this to "feature".

Note: the "Certificate Manager" app already provides API hooks for revoking certificates. However, the user engine does not take advantage of this feature when a user is deleted.
(0013671)
NickH (developer)
2020-03-27 08:23

 Migrated to https://gitlab.com/clearos/clearfoundation/app-openvpn/-/issues/22 [^]

- Issue History
Date Modified Username Field Change
2017-03-09 11:50 NickH New Issue
2017-03-09 12:51 user2 Assigned To => user2
2017-03-09 12:51 user2 Status new => confirmed
2018-11-05 20:35 user2 Note Added: 0008511
2018-11-05 20:35 user2 Severity major => feature
2018-11-05 20:36 user2 Relationship added related to 0022221
2018-12-14 12:10 user2 Status confirmed => assigned
2018-12-14 12:10 user2 Assigned To user2 => tracker
2020-03-27 08:23 NickH Note Added: 0013671
2020-03-27 08:23 NickH Status assigned => closed
2020-03-27 08:23 NickH Assigned To tracker =>
2020-03-27 08:23 NickH Resolution open => suspended