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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Obfuscating email address on privacy statement page?Obfuscating email address on privacy statement page?
Previous
 
Next
New Post
3/22/2007 9:11 AM
 
Anyone have documented a good way of obfucating harvestable email addresses in DNN such as on the privacy statement page?  Seems it would be trivial to grab a slew of these via Google.

Shawn
 
New Post
3/22/2007 6:22 PM
 
  from the Secure Module Development.doc

DotNetNuke provides a function, CloakText, that hides sensitive data by generating javascript that spiders pass over, but that still correctly renders output. The core function, FormatEmail utilizes this and concatenates the output with a the html to create a hyperlink

Response.Write (FormatEmail(“somemail@somewhere.com”))


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/22/2007 7:27 PM
 
cathal wrote
  from the Secure Module Development.doc

DotNetNuke provides a function, CloakText, that hides sensitive data by generating javascript that spiders pass over, but that still correctly renders output. The core function, FormatEmail utilizes this and concatenates the output with a the html to create a hyperlink

Response.Write (FormatEmail(“somemail@somewhere.com”))



cathal,

Thanks for the reply.  I'll look into using FormatEmail to see how easy/hard it makes the harvesting.  Assuming that this is the preferred mechanism, why isn't this already being done on a default DNN install's privacy page?  Even this site has a clearly harvestable email address (at least from a RegEx perspective).  Couple this with the power of Google and the ability to identify just about every single Privacy page on any DNN site in the world by seeking the /ctl/privacy/ tag existing in the URL, it seems that it would be a common problem for site admins.  Perhaps that's why dotnetnuke.com's email address is admin1 (at) dotnetnuke (dot) com instead of regular old admin?  ;)

Anyway, please don't take what I'm saying negatively, I'm all for doing whatever I can to help the situation, I'm just surprised that this hasn't been raised yet as a pretty serious problem.

Cheers!

Shawn
 
New Post
3/22/2007 11:45 PM
 

it's on my list of to-do items, but it's low priority (and also slightly complicated by the use of localised text). FYI many spam harvesters simply try lists of common user names and the domain name itself rather than harvest via websites(as it's easier to watch name servers than spend money on bandwidth searches).

There were some changes checked in for token replacement in 4.5, this should make this task easier, so i intend to do it shortly, but I don't think I'll get it done for the 4.5 release itself.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/23/2007 9:20 AM
 
Cathal,

Thanks much for the reply, but more importantly thanks for all your work on this platform!

Cheers!

Shawn
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Obfuscating email address on privacy statement page?Obfuscating email address on privacy statement page?


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