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 ...Block PowerDNN ScannerBlock PowerDNN Scanner
Previous
 
Next
New Post
5/21/2008 11:14 PM
 

Dear all:

You can block the DNN security scanner from PowerDNN in order to prevent anybody from using it to reveal information about your DNN implementation.

It is very easy, the only catch is that you must be able to make changes to IIS on the server.  The solution is to block the address for the PowerDNN site, it is 216.58.236.42 (this is public, easily obtained information).  I just did this and attempted a scan, the scanner immediately shows "Could not verify website as a DotNetNuke Website.

Hope this helps those with concerns about this tool until the dust settles about the true vulnerabilities (if any) and possible patches.

Carlos

 

 
New Post
5/21/2008 11:19 PM
 

Ah, that's a great idea.  Thanks for the information Carlos!

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
5/22/2008 9:41 AM
 

Yeap, most hosts have also blocked the tool as well. Its original intent was sound but as with all good things, some bad eggs ruin it for the bunch. Most hosts will allow you to block this if you just contact them.

 
New Post
5/22/2008 10:12 AM
 

I removed all xx.xx.xx.txt files from /portals/_default directory (you can do this using online the file manager in Host menu) and now the scanner reports

"There are no security vulnerabilities in your website."

This will also help against any other's attempt to get your DNN version from using the same mechanism.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/22/2008 10:38 AM
 

A case could be made for removing the .txt files - and the old .SqlDataprovider files once they have ben run in the Install/Upgrade as they have no further use.  If a user needs to "rebuild" their site from scratch then they could "upload" the files from a fresh package.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Block PowerDNN ScannerBlock PowerDNN Scanner


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