Hi,
On Wed, Sep 03, 2014 at 10:41:34PM -0400, Arne Schwabe wrote:
> Newer OpenVPN versions (I don't recall if -master or 2.3.x) have this
> information in the status report. For older version you have to record
> the ID when a client is connected.
In master:
commit 662ce6acc065bddf6490b3494725b8
Hi,
Attached a patch for a change suggested by Jann Horn, to remove the
quadratic complexity from openvpn_base64_decode().
The suggestion was originally sent to the security list, because
quadratic complexity can potentially lead to a denial-of-service attack
vector. In the current OpenVPN codeba
On 03/09/14 18:23, dav...@redhat.com wrote:
> From: David Sommerseth
>
> Commit 9449e6a9eba30c9ed054f57d630a88c9f087080f introduced the
> openvpn_popen() function to support retrieving passwords via systemd.
>
> It was discovered that the child processes openvpn fork()ed would
> be lingering aro
Am 03.09.14 22:36, schrieb 張 世杰:
> Hi Gert,
>
> Thanks for your reply, it's my mistake
> Now my question is how to record the client id every time when a client
> connected
> Is there a hook in server which will be triggered when a new client connect?
>
> Currently in my application, I parse the r
Hi Gert,
Thanks for your reply, it's my mistake
Now my question is how to record the client id every time when a client
connected
Is there a hook in server which will be triggered when a new client connect?
Currently in my application, I parse the result of status 2 to get the IP:port
for killi