4571 Posts in 1382 Topics by 1376 members
|
Page:
1
|
Go to End | |
| Author | Topic: | 1430 Views |
-
Suspicious File Alerts : cache problem?
10 May 2010 at 11:51am Last edited: 10 May 2010 11:52am
Installed SilverStripe to try out the acript in a sub-domain, and I'm getting these Suspicious File Alerts from LFD in WHM every hour.
lfd on host.myhostname.com: Suspicious File Alert
Time: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_forms_ReadonlyTransformation.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_core_model_fieldtypes_ForeignKey.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_core_model_fieldtypes_SSDatetime.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_forms_CheckboxSetField.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_security_MemberLoginForm.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_parsers_BBCodeParser.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_core_i18n.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_widgets_WidgetArea.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_email_QueuedEmailDispatchTask.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenTime: Mon May 10 09:02:29 2010 +1000
File: /tmp/silverstripe-cache-home-username-public_html-cms/manifestClassParse-_home_username_public_html_cms_sapphire_parsers_TextParser.php
Reason: Script, file extension
Owner: nobody:nobody
Action: No action takenLooks like something to do with cache. Is a cache folder missing or something?
Thanks
-
Re: Suspicious File Alerts : cache problem?
10 May 2010 at 3:32pm
Looks like you have some sort of software checking for (potentially) malicious files in your tmp directory. There isn't anything wrong as such - SilverStripe creates these files to speed up execution - but if you can't turn off the warnings you can manually set the SilverStripe cache directory with:
define('TEMP_FOLDER', 'some-web-writeable-temp-folder');
-
Re: Suspicious File Alerts : cache problem?
10 May 2010 at 4:16pm Last edited: 10 May 2010 4:17pm
Thanks Hamish
Thanks for the tip. Yes, we're using ConfigServer Security & Firewall http://www.configserver.com/cp/csf.html on WHM, which impacts all hosting accounts.
So, just to confirm, we change:
if(!defined('TEMP_FOLDER')) {
define('TEMP_FOLDER', getTempFolder());
}to
if(!defined('TEMP_FOLDER')) {
define('TEMP_FOLDER', '/full/path/to/the/temp/directory');
}Is that right?
Thanks again
Michael
-
Re: Suspicious File Alerts : cache problem?
10 May 2010 at 6:20pm
Would work, but better not to hack the core and use Environment Management instead. Just create a _ss_environment.php to sit in your SS root folder and put the line there.
| 1430 Views | ||
|
Page:
1
|
Go to Top |
