next »

[desertcities]

I have a few hosts and one of them is Pair.com.  I've been with them for years.  On 3 separate occassions they deleted my Calendar script saying that a Brazilian bot exploited the calendar program and was sending spam.  

This included the latest 3.21 with the security patch too.  So, this is very disappointing as I've been using Matt's scripts for years.  I'm one of the old boys who ran some of the big BBSs years ago.

I don't know what else to do.  Anything that could fool this bot?  Can one change the filenames and folders to fool these bots?

I was looking at other calendar programs and really, I just love Calendar Script so much better.  The only close second was Web Calendar Pro (php) but I feel so much more at home using Matt's script.

Any suggestions?

Thank you.

Mark

[DanO]

** On 3 separate occassions they deleted my Calendar script saying that a Brazilian bot exploited the calendar program and was sending spam. **

CalendarScript has no builtin email functions. Unless you've modified the script in some way to include them, there is no possible way CalendarScript could be responsible for emails being sent.

If you or anyone else has specific evidence that CalendarScript 3.21 is vulnerable to attack, I suggest you email Matt (CalendarScripts' author) with the specific details of the attack so exploits can be looked into.

JMO

Dan O.
(not CalendarScript's author).

------------------

[rwhirn]

I've had a situation come up today where my hosting company has disabled my calendarscript because it was using 100% of resources and brought the server down.

I'm not sure what caused it, but looking through the log files I see a couple bots, particularly geniebot, which is hitting claendar pages going back to the 1920s! It seems like it may be getting in a loop when it keeps going to the previous year on the month banner. Has anybody else had this problem?

The obvious solution is to put \cgi-bin\ in the robots.txt file which I have just done, but I'm thinking of putting in some code to keep calendarscript from going more than X years forward or back.

------------------