|
|
8.
|
|
|
Select which pages you would like to use the HTTPS <abbr title="Secure Sockets Layer">SSL</abbr>/<abbr title="Transport Layer Security">TLS</abbr> protocol. An HTTPS page view encrypts bi-directional traffic securely (to avoid unauthorised tampering and interception by third-parties) but also imposes a performance cost on the server. To use HTTPS you must have an SSL/TLS certificate installed on your server, and have the website files accessible via both HTTPS and HTTP variants of the base-URL.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SSL_PAGE_SELECT
|
|
|
9.
|
|
|
The lookup module links to a number of external web tools that can find information about IP addresses. These tools are:\n - Reverse-DNS lookup - this will find try and find a domain name attached to the IP address\n - DNS lookup - this will find try and find a domain name attached to the IP address, and then the IP address attached to the domain name: with a second IP address, further analysis might be performed\n - WHOIS query - this will try and find a domain name attached to the IP address, and then try to find real-world details about the registered owner of that domain name\n - Ping - this will see if the computer with the IP address responds to ‘pings’; servers often will, but desktop computers rarely will\n - Tracert - this will find the network route between the server that provides this web tool, and the server of the IP address; it provides an impression of the locality and connectivity of the associated computer\n - Geo-lookup - this will try and find the geographical location of the IP address; it can be widely inaccurate however: for example, in the past UK AOL users have been shown as being located in the US
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_INVESTIGATE_USER
|
|
|
10.
|
|
|
If you have a dedicated server which is configured with an SSL/TLS certificate, tied into your domain, and if the server is configured to use the same file system for HTTPS as for HTTP, then you may choose to make certain pages work via HTTPS. Before you may select which pages to use, you must enable the "HTTPS support" option from the "General" subsection of the "Security/Usergroup configuration" section of the configuration.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_SSL
|
|
|
11.
|
|
|
Security
|
|
|
|
|
Sigurnost
|
|
Translated and reviewed by
Miro Glavić
|
|
|
|
Located in
[strings]SECURITY
|
|
|
12.
|
|
|
HTTPS (<abbr title="Secure Sockets Layer">SSL</abbr>/<abbr title="Transport Layer Security">TLS</abbr>) support is disabled.<br />If it is desired for certain website pages to load under HTTPS, then the support may be turned on in the <a href="{1}">configuration</a>.<br /><br />Please be advised that you will need an SSL/TLS certificate, that you will need a properly configured server, and that HTTPS support imposes a (very) small performance impact in this software's URL-generation code.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]HTTPS_DISABLED
|
|
|
13.
|
|
|
Security logging
|
| Context: |
|
[strings]SECURITY_LOGGING
|
|
|
|
|
Sigurnosno prijavljivanje
|
|
Translated and reviewed by
Miro Glavić
|
|
|
|
Located in
[strings]SECURITY_LOGGING
|
|
|
14.
|
|
|
Failed logins
|
|
|
|
|
Neuspjele prijave
|
|
Translated and reviewed by
Miro Glavić
|
|
|
|
Located in
[strings]FAILED_LOGINS
|
|
|
15.
|
|
|
Security alerts
|
|
|
|
|
Sigurnosna upozorenja
|
|
Translated and reviewed by
Miro Glavić
|
|
|
|
Located in
[strings]SECURITY_ALERTS
|
|
|
16.
|
|
|
View security alert ({1})
|
|
|
|
|
Pogledaj sigurnosno upozorenje ({1})
|
|
Translated and reviewed by
Miro Glavić
|
|
|
|
Located in
[strings]VIEW_ALERT
|
|
|
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
|
