Just to close the loop, the 'username-as-common-name' server configuration
parameter sets the log to do this.
Original Message Follows
From: "Alexander Littell"
To: openvpn-devel@lists.sourceforge.net
Subject: [Openvpn-devel] OpenVPN Status Log
List
On Fri, 05 Jan 2007 00:38:44 +0300, Alexander Littell
wrote:
Thanks for the input, Tony. I'm sure that solution scales very well. ;-)
I'm puzzled...
Was that an irony or am I missled by English vs Russian language
differences?
Tony.
Thanks for the input, Tony. I'm sure that solution scales very well. ;-)
Original Message Follows
From: Tony
To: openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] OpenVPN Status Log
List-Post: openvpn-devel@lists.sourceforge.net
Date: Thu, 04 Jan 2007 12:40:35 +030
Alexander Littell wrote:
How difficult would it be to program the openvpn-status.log to show
usernames instead of common names? Or maybe both. Any thoughts on how to
do this?
I could be wrong, but I would guess that most OpenVPN administrators are
using username/password pairs instead of ce
On Wed, 03 Jan 2007 16:29:20 +0300, Alexander Littell
wrote:
I would guess that most OpenVPN administrators are using
username/password pairs instead of certificates to authenticate their
clients. Well, I do anyway.
Not me!
I use hardware-tokens-based (PKCS#11) authentication.
Tony.
How difficult would it be to program the openvpn-status.log to show
usernames instead of common names? Or maybe both. Any thoughts on how to
do this?
I could be wrong, but I would guess that most OpenVPN administrators are
using username/password pairs instead of certificates to authenticate
