Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN and FIPS complianceDNN and FIPS compliance
Previous
 
Next
New Post
4/16/2012 5:41 PM
 
Please help. We are tasked to deploy our portals and custom modules (DNN 5.2.2 Professional) under a FIPS enabled web server.Currently I am trying to test this using my laptop (Windows 7 / IIS) with "System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing" enabled.My web.config has the following for "machine key..etc" When I access my portal it fails with "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms". However DNN 'host, admin' pages work fine. Some of our custom pages that use custom module fail. These pages use XML files to populate the links on the page etc.The Event Log seems to point to the method "System.Security.Cryptography.MD5CryptoServiceProvider..ctor".My basic research seems to suggest that MD5 is not FIPS compliant.Can someone point us in the right direction.Basically what should we do to bring up a DNN app under a FIPS enabled Server?Is there a way to tell DNN installation not to use MD5 and use only compliant algorithms?Thanks a lot in advance for your help
 
New Post
4/16/2012 8:53 PM
 
MD5 is not allowed in a FIPS environment - if your custom modules use it then you will need to update them. There are a few places in DotNetNuke where it's optionally used such as the the filebased caching provider where the solution is to use an alternative (in this case the webbased caching provider is ideal) but in general DotNetNuke works in FIPS environments. Note: at present in 6.1.x releases there is a FIPS issue with the client resource manager that we are working to resolve.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
4/17/2012 11:45 AM
 
Cathal,

Appreciate your prompt reply very much.
Please let me know how I can force DNN to use "Web based caching" instead of "File Based". Is this a host/admin setting or a web.config change? If web.config then what exactly the change that I should make?

How can one tell if a custom module uses file based caching? The code behinds of our modules are pretty simple and straighforward and do not refer to / invoke any algorithms Explicitly.

Once again thanks a lot for your timely help.
 
New Post
4/17/2012 5:25 PM
 
for switching caching methods you'll need an appropriate caching provider. DNN Community just comes with file based caching, there are other caching providers in PE and in the Store.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/17/2012 5:58 PM
 
The caching providers are only needed if you are running in a webfarm - CE only contains the file based one which is not FIPS compliant (it contained the broadcast poller which was FIPS compliant but was deprecated due to known performance problems). You can code your own or download/buy an alternative, or if you are a PE/EE customer use the webbased caching provider.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN and FIPS complianceDNN and FIPS compliance


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out