On Dec 1, 2010, at 7:30 AM, J.Lance Wilkinson wrote:
> In hindsight, the fact these messages were not prefixed by typical
> Apache error log tokens like like [timestamp] [severity] [client]
> should have been the tipoff here.
That is true, log messages from the server (through
J.Lance Wilkinson wrote:
Sander Temme wrote:
On Nov 30, 2010, at 8:37 PM, J.Lance Wilkinson wrote:
But my httpd log files present an unexpected error each and every
time a browser visits an SSL encrypted page (2 examples cited):
So there is no discernible negative impact on the client?
Sander Temme wrote:
On Nov 30, 2010, at 8:37 PM, J.Lance Wilkinson wrote:
But my httpd log files present an unexpected error each and every time a
browser visits an SSL encrypted page (2 examples cited):
So there is no discernible negative impact on the client?
Correct. At the mom
On Nov 30, 2010, at 8:37 PM, J.Lance Wilkinson wrote:
> But my httpd log files present an unexpected error each and every time a
> browser visits an SSL encrypted page (2 examples cited):
So there is no discernible negative impact on the client?
> User interface error
> unable to load Private K
My organization recently switched its SSL Certificate vendor and the new
supplier (COMODO) insists (reasonably) that we use 2048-bit Private and Public
keys.
So I take a running Apache installation, HTTPD v2.2.6, with mod_ssl v2.2.6 and
openssl v0.9.8g running on Solaris 10, currently using a T
