|
@@ -10,6 +10,12 @@ Using a database key [provided by staff](sections/tools/misc/database_key.php) a
|
10
|
10
|
|
11
|
11
|
The rest of gazelle must be aware that some of the data it fetches from the DB is encrypted, and must have a fallback if that data is unavailable (the key is not in memory). You will see plenty of `if (!apc_exists('DBKEY')) {` in this codebase.
|
12
|
12
|
|
|
13
|
+#### Authorized Login Locations
|
|
14
|
+
|
|
15
|
+Whenever a login occurs from a location (determined by ASN) that hasn't logged into that account before, an email is sent to the account owner requesting that they authorize that location before the login will go through.
|
|
16
|
+
|
|
17
|
+This prevents most attacks that would be otherwise successful, as it requires an attacker to access the site from the same locations the actual user uses to login.
|
|
18
|
+
|
13
|
19
|
#### Expunge Requests
|
14
|
20
|
|
15
|
21
|
Users are able to view the data kept on them and [issue requests for the deletion of old information](sections/delete) to staff through a simple interface.
|