Implement ReCaptcha registration flow #900
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#900
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nex/feat/recaptcha"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements the
m.login.recaptcha
flow, which allows servers to gate their registration behind a captcha, preventing automated signups.@ -185,3 +185,4 @@
&& config.registration_token.is_none()
&& config.registration_token_file.is_none()
&& !(config.recaptcha_site_key.is_some() && config.recaptcha_private_site_key.is_some())
{
Might or might not still be worth having a note when recaptcha is set? Up to you
yeah, might add a warning in since I still consider no-verification (token/email) "insecure", but it's not as insecure as "no confirmation at all".
Regardless, there's a warning just below anyway:
I think this is sufficient
@ -557,2 +557,4 @@
pub registration_token_file: Option<PathBuf>,
/// The public site key for reCaptcha. If this is provided, reCaptcha
/// becomes required during registration, **even if token registration is
So users need either to solve the captcha or give the token, but not both?
They need to do both if both are configured. If enabled, token is required first, and then captcha.
Perhaps clarify that, I misunderstood a bit
@ -558,1 +558,4 @@
/// The public site key for reCaptcha. If this is provided, reCaptcha
/// becomes required during registration, **even if token registration is
/// enabled**.
FWIW this might be used for new auth's signup flow too, once that's implemented