Am 05.05.15 um 17:47 schrieb Steffan Karger:
> As reported in trac tickets #304, #358 and #359 (and possibly more), the
> usage and interpretation of --tls-cipher (and --show-tls) is tricky. This
> patch extends the man page to explain those a bit better and point out
> that --tls-cipher is an
Am 05.05.15 um 17:47 schrieb Steffan Karger:
> As reported in trac tickets #304, #358 and #359 (and possibly more), the
> usage and interpretation of --tls-cipher (and --show-tls) is tricky. This
> patch extends the man page to explain those a bit better and point out
> that --tls-cipher is an
As reported in trac tickets #304, #358 and #359 (and possibly more), the
usage and interpretation of --tls-cipher (and --show-tls) is tricky. This
patch extends the man page to explain those a bit better and point out
that --tls-cipher is an expert feature (i.e. easy to get wrong). Also add
a
Forgot to mention that this patch is again the 2.3 branch. I'll send
another one for Git "master".
> From: Samuli Seppänen
>
> On UTF-8 systems groff interprets unescaped dashes as hyphens and escaped
> dashes
> as minus signs. Unescaped dashes can cause problems when
On Sat, 2015-05-02 at 01:54 +0300, Alon Bar-Lev wrote:
> what is specified explicitly in PKCS#11 spec must be applied by
> providers, there is no room for interpretation in this specific case.
>
> > From the OpenVPN point of view, actually there's a cheap trick which
> > can let us call it
From: Samuli Seppänen
On UTF-8 systems groff interprets unescaped dashes as hyphens and escaped dashes
as minus signs. Unescaped dashes can cause problems when searching for or
copying and pasting options. This patch ensures that dashes in command-line
options are escaped and
Hi,
Here's the summary of the previous IRC meeting.
---
COMMUNITY MEETING
Place: #openvpn-devel on irc.freenode.net
List-Post: openvpn-devel@lists.sourceforge.net
Date: Monday 4th May 2015
Time: 20:00 CEST (18:00 UTC)
Planned meeting topics for this meeting were here: