jonathan
Fri Aug 26 12:26:06 CDT 2005
See also:
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.security.crypto&tid=d1dc1340-e004-4da9-97d7-a7d4ba5fd3c0&cat=en-us-technet-security&lang=en&cr=US&sloc=en-us&m=1&p=1
One of the reasons some of us are hoping for AES in Microsoft SSL is that
people (often competitors) are starting to knock (with good reason) Microsoft
SSL as being behind the curve. Almost all major SSL implementations
including those from Sun, OpenSSL and many other commercial SSL stacks for
Windows already include AES support. When people figure out that Microsoft
SSL lacks the AES algorithm, it usually comes as a surprise.
One of the other reasons some of us are hoping for AES in Microsoft SSL is
that it a FIPS 140 approved algorithm. Several years ago my company ended up
writing an AES library (that subsequently earned FIPS 140-2 validation)
because we couldn't wait for Microsoft to implement AES and get it approved.
Now that Microsoft finally has a FIPS-validated AES module, we're stuck
waiting for them to implement it in SSL so people who are stuck with 3DES as
their only FIPS-approved algorithm can move to something better.
(Feel free to kick me a private response at
"jonathan.lampe@standardnetworks.com" too.)
"FastEddie" wrote:
> All,
>
> Is there a way to make Windows 2003 IIS 6 support 256 bit TLS? As far as I
> have read, IIS6 does not support it. I really need this up and running ASAP!
> Do I need to use Apache to do this?
>
> If there is a way for IIS 6, please follow up with info and links if
> possible.
>
> Thanks,
>
> FastEddie
>
>
>