On 23/06/15 19:39, Gert Doering wrote:
> As far as the feature itself is concerned, I'm not voicing an opinion
> (as I've never seen a deployment without client certs, so don't
> understand the implications)
I have - it's very useful in particular circumstances. But the few
people like me who use
Hi,
On Tue, Jun 23, 2015 at 09:26:54AM +0200, Steffan Karger wrote:
> In 2.3:
> * Add soon-to-be-deprecated message to --client-cert-not-required man
> page entry.
>
> In 2.4:
> * add --verify-client-cert (none|optional|required)
> * add a clear deprecation message when client-cert-not-requir
Hi,
On 22-06-15 23:20, Jason Haar wrote:
> On 23/06/15 03:50, Jan Just Keijser wrote:
>> 1) do we think it's valuable to add something like this (currently NO
>> cert checks are done when 'client-cert-not-required' is used) ?
>
> sounds like what you really want is for this to be renamed
> "--ve
Hi,
On 22/06/15 23:20, Jason Haar wrote:
On 23/06/15 03:50, Jan Just Keijser wrote:
1) do we think it's valuable to add something like this (currently NO
cert checks are done when 'client-cert-not-required' is used) ?
sounds like what you really want is for this to be renamed
"--verify-client-
On 23/06/15 03:50, Jan Just Keijser wrote:
> 1) do we think it's valuable to add something like this (currently NO
> cert checks are done when 'client-cert-not-required' is used) ?
sounds like what you really want is for this to be renamed
"--verify-client-cert (none|optional|required)" - with th
hi all,
just found out that when you use 'client-cert-not-required' that the
client certificate is not checked at all, even if one is presented. I'm
not sure if that's by design but I think it would be handy to check the
client certificate if presented by the client.
This allows an admin to s
