Some page is leaking info about who just installed Drupal. I did a complete reinstall of one of my test sites and immediately got two people trying to register (probably spammers). Registration is blocked - requires u=1 to approve.

Incidentally the page to report problems. http://drupal.org/support, like this is blocked if you aren't logged on - not very user friendly - at least tell people to logon.

Comments

killes@www.drop.org’s picture

You probably published the URLs to your test site somewhere in advance.

http://drupal.org/support is not blocked at all.

I think this is "won't fix".

yktdan’s picture

drupal.org/support is not blocked, but the links on it to report problems are blocked. I know that I have to logon to get get access, but most new users won't know why they can't report a problem. so /support should have some additional words on it that tell people to create and account and logon to report problems.

The test site in question has been around for a long time and not easily found. What struck me as strange is that I got three attempts in rapid succession to blowing it away and reinstalling it. The spiders don't react that quickly to new content (which in this case was not new at all). The site has essentially no content to index. I know that sites report back to Drupal when they get installed and that Drupal keeps that information somewhere, but I don't know where. But that information should not be available to the general public, but apparently is.

killes@www.drop.org’s picture

ok, adding some text to the "access denied" page is probably an improvement.

Your site only reports back to drupal.org if you check the appropriate checkbox.

It does so to request update information. I do not think it actually calls back during installation.

If the site was available before the install, you should check your logs for registration attempts before the reinstall. I guess you'll find many.

Any site around for some time will be found. You just need to collaborate with somebody who uses gmail...

dsquaredb’s picture

Issue summary: View changes
Status: Active » Closed (fixed)

Closing this issue since it has been inactive for quite a while.