Hello,
The following patch against trunk adds a directive AuthBasicUserFromSSL
(On/Off) to mod_auth_basic.
Setting this to On would skip authentication if r-user is set by mod_ssl.
This is needed when using client certificates for authentication, because in
this case you don't get any password
[EMAIL PROTECTED] wrote:
May I use this occasion to ask if there's still a chance of getting a
backport of SNI accepted for 2.2.x?
For me, +1. For the LAMPs guys, +1m. For the phishing
victims, +10m.
Ok, the
Paul wrote:
It is important enough, the problem is we don't want to a back port to
cause regression or other sidee effects, and to me that is the scariest
thing about the SNI patch(es).
There might be a compromise position here: As long as the
SNI patch causes no problem to other services,
Den Tuesday 19 August 2008 08:16:08 skrev Kaspar Brand:
Ruediger Pluem wrote:
At the moment we have 9 entries in the CHANGES file for 2.2.10 and
there are 5 more proposals in the STATUS file that are missing only
one vote. I think if get these done we also have enough stuff from
pure
On Wed, 20 Aug 2008 12:06:33 +0200
Oden Eriksson [EMAIL PROTECTED] wrote:
FYI: This patch is applied in Mandriva Linux.
Any feedback? Bug reports coming from their users?
If you'd said Debuntu or Deadrat+family, we might infer a user
community big enough to rely on (FSreasonableVO rely).
Not
I like the idea of using --with-SNI and labeling it as experimental.
Maybe leave it of by default though?
~ Jorge
On Wed, Aug 20, 2008 at 1:10 PM, Nick Kew [EMAIL PROTECTED] wrote:
On Wed, 20 Aug 2008 12:06:33 +0200
Oden Eriksson [EMAIL PROTECTED] wrote:
FYI: This patch is applied in
On Wed, Aug 20, 2008 at 02:08:02PM +0200, Jorge Schrauwen wrote:
I like the idea of using --with-SNI and labeling it as experimental.
Yeah, good way to move forward.
Maybe leave it of by default though?
absolutely. It would seem rather odd to turn on experimental by default.
vh
Mads Toftum
On Aug 18, 2008, at 5:18 AM, Joe Orton wrote:
So generally pconf is the right pool to use, along with a cleanup
registered against that pool which sets the callbacks to NULL.
Yes, with the cleanup it no longer hangs. What about stashing a pool
reference in a global, is that a red flag?
-Ursprüngliche Nachricht-
Von: Sander Temme
Gesendet: Mittwoch, 20. August 2008 16:37
An: dev@httpd.apache.org
Cc: Joe Orton
Betreff: Re: [PATCH] Dynamic locking upcalls in mod_ssl
Index: modules/ssl/ssl_util.c
A little while ago, Basant Kukreja published mod_sed under the
Apache license. He's now also written a blog entry that could
become the basis for a tutorial into how mod_sed is much more
than a mere string-or-regexp search-and-replace filter:
Nick Kew wrote:
A little while ago, Basant Kukreja published mod_sed under the
Apache license. He's now also written a blog entry that could
become the basis for a tutorial into how mod_sed is much more
than a mere string-or-regexp search-and-replace filter:
On Aug 20, 2008, at 7:10 AM, Nick Kew wrote:
It might be worth a --with-SNI configuration option, which
would label it as an experimental feature.
+1, given that it'd be off by default. Anyone care to craft some
autofoo?
S.
--
Sander Temme
[EMAIL PROTECTED]
PGP FP: 51B4 8727 466A 0BC3
On Aug 20, 2008, at 11:56 AM, Plüm, Rüdiger, VF-Group wrote:
You should set dynlockpool to NULL here as well. In case it is used
afterwards
things segfault and are easier to detected than when an invalid
pointer is used.
This should basicly address your question regarding the reference on
13 matches
Mail list logo