Let me guess you have a '128 bit' SGC certificate on your
server? If you do then change your cipher suite to not offer EXPORT56 for
example:
SSLCipherSuite !EXPORT56:ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
This results in most people with older client
> In addition, a large proportion of our customers have little or no
> previous IT experience and cannot be expected to apply patches no
matter
> how trivial it may seem to us!
We had some top-notch technical people spend more than three months,
setting up an isolated web/client environment to du
Simply send them to http://windowsupdate.microsoft.com, and talk them
through it if you have to.
Things could get worse for them if they don't anyway.
-
John Airey
Internet systems support officer, ITCSD, Royal National Institute of the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0)
On Fri, 17 May 2002 13:51:15 +0100
"Jeff" <[EMAIL PROTECTED]> wrote:
> MS IE 5.00 was a flawed release, that MS very quickly (4 weeks) replaced
> with 5.01, mainly for security reasons. You should be able to get any
> reasonable users (corporate or otherwise) to upgrade asap. MSIE 5.00 has
> som
Charles Darwin knew a fraction of what scientists know today, he'd never
have written the Origin of the Species.
> -Original Message-
> From: Jeff [mailto:[EMAIL PROTECTED]]
> Sent: 17 May 2002 13:51
> To: [EMAIL PROTECTED]
> Subject: RE: IE 5.00 - 5.01 SSL Connection F
MS IE 5.00 was a flawed release, that MS very quickly (4 weeks) replaced
with 5.01, mainly for security reasons. You should be able to get any
reasonable users (corporate or otherwise) to upgrade asap. MSIE 5.00 has
some serious bugs when using SSL and cacheing, so you may be able to
tweak all yo
