Ну и кто самый честный, самый умный и самый небоящийся скажет:
Что, сервис вам этот помешал? Конкуренция?.. Али просто мозгов мало и решили через укорачивание ссылки лохов посрубать?
Пздц, народ. Я фигею... Решишь что-то для народа бесплатно сделать - так и то насрут.
Идут разборки с хостером.
12.12.2008.
UPD: Хех... Ну вот и всё. Нет больше hash.su как сервиса укорачивания ссылок, спасибо добрым людям. На сколько я понял - что бы я ни делал, если поступит ещё 1-2 жалобы, то сайт опять прибъют. Чтож, выход один - забогатеть и поставить свой сервак, дабы не зависеть от прихоти хостера. Но пока что на сервер у меня денег нет и неизвестно когда будут, так что, господа, извольте откланяться. Жаль, что сервис сей даже до своего годовалого юбилея не дожил. Переписка с хостером ниже.
P.S. Впрочем, сайты на поддоменах продолжают работать. Как пример — пастебин: http://code.hash.su (алиас). Возможно, позже перенесу его на главную, дабы урл покороче был.
23.12.2008 email.
|
[Первое письмо]
Hello,
We've received reports regarding your URL redirection site 'hash.su'
being used by malicious parties to engage in unlawful behavior by
providing URL redirection to fraudulent sites (ie. spam, phishing, etc).
Spammers, phishers, etc. often use URL redirectors such as yours in order
to obfuscate the true origin of their directed sites, hiding their
activities from clear view. The URLs in question (that need to be
removed) include:
hash.su/razvratzvezd
hash.su/pornoarhiv
As a temporary measure, I have disabled the site until you have a chance
to review/modify your code to enable preventative measures and prevent
this sort of usage in the future. We recommend the following:
- Create some sort of checking system to filter out suspicious URL
redirections before they are created. For example, you could flag URL
creation based on IP addresses originating from countries and IP ranges
where fraudulent activity is common (ie. Vietnam, Nigeria, Romania,
Brazil) and check those links before they become available. You might
also require the use of a CAPTCHA in order to prevent automated
bots/tools from creating links.
- Check destination sites to ensure that they are not likely to be
fraudulent. For current phishing sites we recommend the use of the
Phishtank database (http://www.phishtank.com/), though you might also
want to search for common terms found on spam/phishing sites (ie.
"Viagra", "Bank", etc) and flag those links for review before they are
approved.
- Before finishing a redirect, provide a link so that those who are
redirected can quickly and easily report the site for illegal activity.
- Flag accesses based on 'HTTP REFERER' if no referrer is found. These
are often links contained in emails, which are often fraudulent phishing
redirects.
We ask that you leave the site disabled until you make substantive
changes as described above and we have approved its re-enablement. If you
have any questions in the meantime, please let us know.
Karl
|
[Мой ответ]
Hello, Karl.
You wrote 12 dec 2008, 19:52:05:
> Hello,
> We've received reports regarding your URL redirection site 'hash.su'
> being used by malicious parties to engage in unlawful behavior by
> providing URL redirection to fraudulent sites (ie. spam, phishing, etc).
> Spammers, phishers, etc. often use URL redirectors such as yours in order
> to obfuscate the true origin of their directed sites, hiding their
> activities from clear view.
Great friday's news. Really.
> The URLs in question (that need to be removed) include:
> hash.su/razvratzvezd
> hash.su/pornoarhiv
Funny. It's russian words. :)
> As a temporary measure, I have disabled the site until you have a chance
> to review/modify your code to enable preventative measures and prevent
> this sort of usage in the future. We recommend the following:
> - Create some sort of checking system to filter out suspicious URL
> redirections before they are created. For example, you could flag URL
> creation based on IP addresses originating from countries and IP ranges
> where fraudulent activity is common (ie. Vietnam, Nigeria, Romania,
> Brazil)
"where fraudulent activity is common"
Do you mean "Russian Federation", too?.. :)
I think, such sort of a censore is unacceptable. (I'm surprised to hear
this from a resident of a country of such liberal laws)
> and check those links before they become available.
Check manually for non-spam/non-fraud? Are you kiddind? :)
> You might also require the use of a CAPTCHA in order to prevent automated
> bots/tools from creating links.
It's already implemented.
> - Check destination sites to ensure that they are not likely to be
> fraudulent. For current phishing sites we recommend the use of the
> Phishtank database (http://www.phishtank.com/),
It's already implemented.
I'm using PEAR::Net_DNSBL_SURBL class:
"This class acts as interface to the SURBL - Spam URI Realtime Blocklists.
Services_SURBL looks up an supplied URI if it's listed in a Spam URI
Realtime Blocklists."
https://pear.php.net/reference/Net_DNSBL-1.2.1/Net_DNSBL/Net_DNSBL_SURBL.html
> though you might also want to search for common terms found on
> spam/phishing sites (ie. "Viagra", "Bank", etc) and flag those
> links for review before they are approved.
Yeah. I wanted to do this at first, but then...
What's wrong with "Bank" word?.. For example, it's similar
to russian word "banka"(jar).
About "Viagra": Url's like
somefunportal.com/when_viagra_makes_us_laugh/ will be banned?..
I think, this type of filtering will do more harm, than help.
> - Before finishing a redirect, provide a link so that those who are
> redirected can quickly and easily report the site for illegal activity.
Report to me?..
Mmm... Ok 5secs countdown and 2 links: destination and "Report as
fraud/spam". It'll be OK?..
> - Flag accesses based on 'HTTP REFERER' if no referrer is found. These
> are often links contained in emails, which are often fraudulent phishing
> redirects.
Mmm... That's a good recommendation. If user has no http_referer, than he/she will
not be redirected. But I'll show him the destination link.
> We ask that you leave the site disabled until you make substantive
> changes as described above and we have approved its re-enablement. If you
> have any questions in the meantime, please let us know.
> Karl
So... In the end of this letter, the results:
a) I can make "report-link" when users are "in redirection".
b) I can stop auto-redirection if redirecting user has no HTTP_REFERER.
c) All of your other recommendations are already implemented or unacceptable..
Will this be enough?..
|
[Окончание]
Hello,
On Fri, 12 Dec 2008, you wrote:
> Do you mean "Russian Federation", too?.. :)
> I think, such sort of a censore is unacceptable. (I'm surprised to hear
> this from a resident of a country of such liberal laws)
Ultimately, you need to make changes that will cease the use of your
domain for spamming. You ultimately need to find what works for you to
prevent abuse. If the abuse continues, we cannot continue to host the
domain.
> > and check those links before they become available.
> Check manually for non-spam/non-fraud? Are you kiddind? :)
If you're going to have a website which can be abused in this manner, you
need to take whatever measures possible to prevent it from being abused
-- if you're not willing to do this, you need to shut down the site.
> Yeah. I wanted to do this at first, but then...
> What's wrong with "Bank" word?.. For example, it's similar
> to russian word "banka"(jar).
> About "Viagra": Url's like
> somefunportal.com/when_viagra_makes_us_laugh/ will be banned?..
> I think, this type of filtering will do more harm, than help.
Again, ultimately we are concerned with one thing: stopping the abuse on
your site. If you are unwilling to secure it to prevent abuse, we can't
host it.
> > Karl
> So... In the end of this letter, the results:
> a) I can make "report-link" when users are "in redirection".
> b) I can stop auto-redirection if redirecting user has no HTTP_REFERER.
> c) All of your other recommendations are already implemented or
> unacceptable..
>
> Will this be enough?..
It is enough if it stops the abuse. If we receive further complaints of
abuse you may have to implement further measures to secure the site --
whether ones we've already suggested, or new solutions of your own
conception -- or we may need to disable the site entirely.
Karl
|
|