mirror of
https://github.com/mCaptcha/mCaptcha.git
synced 2026-02-11 10:05:41 +00:00
rename pow section in settings to captcha and add options to configure
suggested difficulty factors for use in CAPTCHA configurations estimates The current CAPTCHA configuration panel requires the user to provide difficulty factor <--> visitor threshold mapping, which can be tedious if the user isn't familiar with those parameters. Also, it could lead to ineffective limiting from mCaptcha's side, should it be configured improperly. So an estimate computed from well known statistics like peak, avg and broke-my-site traffic could go a long way.
This commit is contained in:
@@ -21,7 +21,7 @@ domain = "localhost"
|
||||
proxy_has_tls = false
|
||||
#url_prefix = ""
|
||||
|
||||
[pow]
|
||||
[captcha]
|
||||
# Please set a unique value, your mCaptcha instance's security depends on this being
|
||||
# unique
|
||||
salt = "asdl;kjfhjawehfpa;osdkjasdvjaksndfpoanjdfainsdfaijdsfajlkjdsaf;ajsdfweroire"
|
||||
@@ -29,6 +29,12 @@ salt = "asdl;kjfhjawehfpa;osdkjasdvjaksndfpoanjdfainsdfaijdsfajlkjdsaf;ajsdfwero
|
||||
# leave untouched if you don't know what you are doing
|
||||
gc = 30
|
||||
|
||||
[captcha.default_difficulty_strategy]
|
||||
avg_traffic_difficulty = 50000 # almost instant solution
|
||||
peak_sustainable_traffic_difficulty = 3000000 # roughly 1.5s
|
||||
broke_my_site_traffic_difficulty = 5000000 # greater than 3.5s
|
||||
duration = 30 # cooldown period in seconds
|
||||
|
||||
[database]
|
||||
# This section deals with the database location and how to access it
|
||||
# Please note that at the moment, we have support for only postgresqa.
|
||||
|
||||
Reference in New Issue
Block a user