On Tue, May 31, 2016 at 11:37 AM, William A Rowe Jr
wrote:
> It seems the behavior introduced in 2.4.5 is causing a lot
> of confusion for users attempting to disable peer checking.
>
> I would suggest that CheckPeerCN should NOT default to "on" any longer.
> The only valid use case is for the us
On 05/31/2016 06:37 PM, William A Rowe Jr wrote:
> It seems the behavior introduced in 2.4.5 is causing a lot
> of confusion for users attempting to disable peer checking.
>
> Right now, nothing needs to be done to do deep inspection
> (altsubjectname plus common name). Neither directive is
>
It seems the behavior introduced in 2.4.5 is causing a lot
of confusion for users attempting to disable peer checking.
Right now, nothing needs to be done to do deep inspection
(altsubjectname plus common name). Neither directive is
required, both default to on.
Disabling checking is a pain in t
On Tue, May 31, 2016 at 7:35 AM, William A Rowe Jr
wrote:
> On May 29, 2016 01:02, "Jie Gao" wrote:
> >
> > Hi All
> >
> > I wonder if anybody is looking at this issue. At the moment, the build
> cores even at the end of generating a Makefile.
> >
> > If not, I would like to get my hands dirty i
On Tue, 2016-05-31 at 11:15 +0300, Ivan Zahariev wrote:
> Hello,
>
> I got no feedback. Am I posting this suggestion at the right mailing
> list?
Sorry, I see your original post marked for attention in my mail
folder, but languishing hitherto unattended. Just now opened your
link in a browser to
Hello,
I got no feedback. Am I posting this suggestion at the right mailing list?
Best regards.
--Ivan
On 19.5.2016 г. 10:40 ч., Ivan Zahariev wrote:
Hi all,
I'd like to propose a new configuration setting for "mod_fcgid". The
source code changes to review follow:
* The whole patch compa