Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Upgrading DNN P...Upgrading DNN P...DNN 5.5.1 upgrade does not comply with MS security patch recommendationsDNN 5.5.1 upgrade does not comply with MS security patch recommendations
Previous
 
Next
New Post
9/23/2010 12:22 PM
 
Jan Olsmar


www.olsmar.com/
Joined: 9/19/2005
Posts: 1354
I should have done that before I wrote the post ;)
 
New Post
9/23/2010 12:30 PM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
Just to confirm what previous people have said -the mode is unimportant, either RemoteOnly or On is fine (in theory Off is also fine as the oracle padding issue relies on differing http status exceptions, but Off is a bad practice in general). The approriate fix is to ensure that all http status exceptions are redirected to the same page - hence only the defaultRedirect part is mandatory. In addition, we added a timing loop in the DotNetNuke errorpage.aspx similar to Microsofts - if anything as this page accesses a number of core functions and downloads content, it's already sufficently difficult to track function time, making this page arguably better than the simple error.aspx page Microsoft suggested.

When Scott say's RemoteOnly is not enough he meant that hackers didn't rely on seeing the exception message, it's only the http exception status that they need.

Finally, we've been in discussion with Microsoft (including Scott Guthrie, his team and various people in Microsoft' security team) since last Friday and are well aware of all aspects of this issue including parts that Microsoft have not made public yet. This was how we were able to take our properties offline on Friday and have approriate fixes in place before Scott's public blog.
Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
9/23/2010 12:33 PM
 
CT

Joined: 10/2/2006
Posts: 92
Alex,

In his blog post at

http://weblogs.asp.net/scottgu/archiv...

Scott Guthrie explicitly explained "On" not "RemoteOnly". He explicitly provided the text for web.config as

 <customErrors mode="On" redirectMode="ResponseRewrite" defaultRedirect="~/error.aspx" />

However as you yourself have confirmed with the following text provided by you, the DNN upgrade re-writes the web.config as

<customErrors mode="RemoteOnly" redirectMode="ResponseRewrite" defaultRedirect="~/errorpage.aspx" />

Apart from the unimportant difference in "errorpage.aspx" versus "error.aspx" for the error page, the critical distinction here is that emphasized by Scott Gu and demonstrated in his web.config with the difference between "On" and "RemoteOnly" as I have stated repeatedly several times now throughout this thread.



CT
 
New Post
9/23/2010 12:48 PM
 
Alex Shirley


Joined: 1/30/2006
Posts: 5038
CT please see Cathal's last reply for an answer. Thanks.

Alex Shirley
 
New Post
9/23/2010 1:23 PM
 
CT

Joined: 10/2/2006
Posts: 92
There are several completely different issues/questions here:

1) The technical question: which is the precisely correct recommended version of attributes for the web.config element <customErrors>?

2) Are the recommendations of the "manufacturer" Microsoft and the "reseller" DotNetNuke consistent with each other as stated publicly by official representatives of each?

3) Whose recommendation should be followed: the "manufacturer" Microsoft or the "reseller" DotNetNuke?

The APPEARANCE of public recommendations that are consistent with each other between manufacturer and reseller remain critical to assuring confidence in the reseller. When the reseller does not appear to comply with the public recommendations of the manufacturer, it raises concerns.
CT
 
 Page 2 of 4
Previous1234Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...DNN 5.5.1 upgrade does not comply with MS security patch recommendationsDNN 5.5.1 upgrade does not comply with MS security patch recommendations


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