Project

General

Profile

Actions

Bug #17454

closed

Encrypting email addresses could be better

Added by AinulindalĀ« over 17 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Communication
Target version:
-
Start date:
2007-07-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I know there is a function to encrypt email addresses:
config.spamProtectEmailAddresses

With two other functions, there is no mailto anymore in the webpage, and the @ can be replaced by (at) and the "." by (dot) for example.

But I think it can be improved, because with this system the source looks like this:
<a href="javascript:linkTo_UnCryptMailto('jxfiql7zxiwxXzxiwx+co');" >name(at)domain(dot)com</a>

An intelligent spamming robot will be able to replace the (at) and the (dot) by their corresponding character, so the email is not protected enough. And on the webpage the address appear strange with those (dot) and (at) stuff.

Before using typo3 I used drupal. In drupal there is also a spam protection system, but the display of the email address is given to the javascript function as well. This has two main advantages :
- the address appear correctly in the webpage. in my example we will see :
- but the address appear nowhere (really nowhere) in the source code.

On my drupal website I have something like this :
<h3>mail address</h3><script type="text/javascript" language="javascript">eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69
%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a
%62%6f%6e%69%66%61%63%65%2e%72%6f%63%61%40%77%61%6e%61%64%6f%6f
%2e%66%72%22%3e%62%6f%6e%69%66%61%63%65%2e%72%6f%63%61%40%77%61
%6e%61%64%6f%6f%2e%66%72%3c%2f%61%3e%27%29%3b'))</script>

So as you can see, the email is not in the source. I think this is a better protection system...

You can look at the webpage here:
http://www.mindenice.fr/entreprise/clairazur.html

Thanks

(issue imported from #M5937)

Actions #1

Updated by Michael Stucki over 17 years ago

Did you see that there is a possibility to append other text than just (at) and (dot)? For example, your email addresses could look like this:

info@<span style="display:none;">who-needs-spam.</span>yourserver<span style="display:none;">i-dont.</span>.com

Of course this will have no effect if the Spam robot understands CSS or filters out tags, but on the other hand it would also be possible for them to parse JavaScript code.

However, I have the strong feeling that the protection is working well and see no need to change this. But if you think we need a JavaScript implementation, go ahead and write an extension for that...

- michael

Actions #2

Updated by Christian Kuhn over 15 years ago

Resolved, no change required. Another spam protect solution should be done in an extension. It could later be implemented in core if finds widely acceptance.

Actions #3

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF