|
|
17.
|
|
|
A comma-separated list (no spaces) of the file types which may be uploaded by users. Leave blank if you want to just apply core security restrictions, and nothing further.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CONFIG_OPTION_valid_types
|
|
|
18.
|
|
|
A comma-separated list (no spaces) of the file types which are valid images for inline display.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]CONFIG_OPTION_valid_images
|
|
|
19.
|
|
|
You may tick-off (check-off) alerts that you wish to erase from the record. Typically this is useful if you have confirmed the alerts to be false alarms and do not want to see them again in the future.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SECURITY_PAGE_CLEANUP
|
|
|
20.
|
|
|
Any web request can be classified as either a ‘GET’ request or a ‘POST’ request. ‘GET’ requests are carried out purely via a URL, whilst ‘POST’ requests include additional data. The following data was posted when the security alert was raised…
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]POST_DATA_EXPLANATION
|
|
|
21.
|
|
|
Security logging
|
| Context: |
|
[strings]MODULE_TRANS_NAME_admin_security
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]MODULE_TRANS_NAME_admin_security
|
|
|
22.
|
|
|
SSL/TLS (HTTPS) configuration
|
| Context: |
|
[strings]MODULE_TRANS_NAME_admin_ssl
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]MODULE_TRANS_NAME_admin_ssl
|
|
|
23.
|
|
|
Hacker/evil-bot: {1}
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]HACKER_DETECTED
|
