|
1.
|
|
|
The software monitors all web requests for potential security violations and thoroughly logs all suspicious activity. In addition, failed logins are logged, so that you can see if users are trying to illicitly access the accounts of members.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_SECURITY_LOGGING
|
|
2.
|
|
|
Absorb usergroup-permissions
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ABSORB_PERMISSIONS
|
|
3.
|
|
|
The following usergroups do not have any specific-permissions associated with them and thus should absorb from the appropriate usergroup: <strong>{1}</strong>. Be careful with this interface: you should never absorb from administrative usergroups unless you are sure it is something you wish to do.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]USERGROUPS_WITH_NO_PERMISSIONS
|
|
4.
|
|
|
The absorb usergroup-permissions screen allows you to quickly get new usergroups set up with appropriate permissions, by absorbing some from an existing usergroup. Users of OCF (the inbuilt forum system) do not have access to this, as it is automated for them.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_ABSORB_PERMISSIONS
|
|
5.
|
|
|
Permissions are <strong>taken</strong> from this usergroup.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]PERMISSIONS_FROM
|
|
6.
|
|
|
Permissions are <strong>placed</strong> into this usergroup (after first deleting what may be currently there currently).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]PERMISSIONS_TO
|
|
7.
|
|
|
SSL/TLS (HTTPS) configuration
|
Context: |
|
[strings]SSL_CONFIGURATION
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SSL_CONFIGURATION
|
|
8.
|
|
|
Select which pages you would like to use the HTTPS <acronym title="Secure Sockets Layer">SSL</acronym>/<acronym title="Transport Layer Security">TLS</acronym> 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
|