Vote to release httpd-2.4.37 has PASSED.
See www.apachelounge.com/viewtopic.php?p=37467
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Hi,
On Mon, Oct 22, 2018 at 4:39 PM Sanjay Kumar Sahu
wrote:
>
> I want to create a new thread in Apache for following issue. Please create.
You've just done it by sending this new message to the list (as
opposed to replying to an existing one).
>
> Currently we are facing Kerberos authenticati
HI,
I want to create a new thread in Apache for following issue. Please create.
Currently we are facing Kerberos authentication issue in our RHEL7 server
running with Apache/2.4 upon changing Keytab with Crypto type=AES256.
Previously it's Crypto type=all. Please check following with the details
Hi,
On Mon, Oct 22, 2018 at 3:58 PM Sanjay Kumar Sahu
wrote:
>
> Currently we are facing critical Apache/Kerberos authentication issue in our
> RHEL7 server running with Apache/2.4 upon changing Keytab with Crypto
> type=AES256. Previously it's Crypto type=all. Please check following with the
please create new thread for your issue
Pada Senin, 22 Oktober 2018 20.56.05 WIB, Sanjay Kumar Sahu
menulis:
HI All !
Currently we are facing critical Apache/Kerberos authentication issue in our
RHEL7 server running with Apache/2.4 upon changing Keytab with Crypto
type=AES256. Prev
HI All !
Currently we are facing critical Apache/Kerberos authentication issue in
our RHEL7 server running with Apache/2.4 upon changing Keytab with Crypto
type=AES256. Previously it's Crypto type=all. Please check following with
the details.
We are using mod_auth_kerb on Red Hat Enterprise Linux
HI All !
Currently we are facing critical Apache/Kerberos authentication issue in
our RHEL7 server running with Apache/2.4 upon changing Keytab with Crypto
type=AES256. Previously it's Crypto type=all. Please check following with
the details.
We are using mod_auth_kerb on Red Hat Enterprise Linux
Hi Dominik,
On Mon, Oct 22, 2018 at 1:49 PM Dominik Stillhard
wrote:
>
> I've tested the configuration you proposed.
> Unfortunately the problem is not solved by using hostnames.
Yes, sorry, I was looking at 2.5/trunk code, while 2.4.x is missing
one commit (http://svn.apache.org/r1818726).
With
Hi Yann,
I've tested the configuration you proposed.
Unfortunately the problem is not solved by using hostnames.
I still cannot see an SNI-Extension with wireshark:
Secure Sockets Layer
TLSv1 Record Layer: Handshake Protocol: Client Hello
Content Type: Handshake (22)
Version: