.NET 3.0 Workflow tracking service encryption

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The workflow tracking service appears to be using the
MD5CryptoServiceProvider when hashing. This generates an exception on a
FIPS-enabled machine as this algorithm is not FIPS-compliant. Is the
algorithm selection configurable, or are there plans to modify this service
to use a FIPS-compliant algorithm? Thanks.
 
I would consider going to connect.microsoft.com and joining the .NET 3.0
connection. You can then post your bug/suggestion where the group coding
..NET 3.0 are likely to have it pop up on their radar.

Out of curiousity (ignorance), what does FIPS have to do with this?

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************
 
Cowboy (Gregory A. Beamer) said:
I would consider going to connect.microsoft.com and joining the .NET 3.0
connection. You can then post your bug/suggestion where the group coding
.NET 3.0 are likely to have it pop up on their radar.

Out of curiousity (ignorance), what does FIPS have to do with this?
Click to expand...

FIPS - Federal Information Processing Standard.

Certain applications (e.g. those used by any department of the Federal Govt)
may be required to only use FIPS-approved crypto. There's a Windows setting
to disable all non-FIPs-approved crypto, including MD5.

-cd
 
Back
Top