Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protect public links password page #57

Closed
PVince81 opened this issue Jan 11, 2019 · 5 comments · Fixed by #90
Closed

Protect public links password page #57

PVince81 opened this issue Jan 11, 2019 · 5 comments · Fixed by #90
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@PVince81
Copy link
Contributor

@karakayasemi @pmaier1

From owncloud/core#33542

@PVince81 PVince81 added the enhancement New feature or request label Jan 11, 2019
@PVince81 PVince81 added this to the backlog milestone Jan 11, 2019
@karakayasemi
Copy link
Contributor

karakayasemi commented Jan 13, 2019

We already can count failed share access attempts by using share.linkaccess event.

I tried to emit an event before the password check of the public link and listen to it in brute_force_protection app. Throwing an exception in this event callback is enough for blocking brute force attempt.

If is it okay to add new events to the core for pre-post public link password check, I can start to implement this feature.
@PVince81, @DeepDiver1975 what are your thoughts?

@karakayasemi karakayasemi self-assigned this Jan 13, 2019
@PVince81
Copy link
Contributor Author

@karakayasemi sounds good. I thought we already had such events.

@pmaier1
Copy link
Contributor

pmaier1 commented Jan 14, 2019

Yeah, sounds good, nice feature addition!

@PVince81
Copy link
Contributor Author

PVince81 commented Feb 8, 2019

was the core PR the only one needed or does the app require modifications as well ? @karakayasemi

@karakayasemi
Copy link
Contributor

karakayasemi commented Feb 8, 2019

No, the core PR was prerequisite for the desired feature. Now, we can count failed share access attempts by using share.linkaccess event and block attacker by using newly added share.beforelinkauth event.

In the failed login, we have a blocking policy based on uid+ip combination.
In here I guess we should use share_id+ip combination. For this purpose, I am planning to create a new table similar to this https://github.com/owncloud/brute_force_protection/blob/master/appinfo/Migrations/Version20180802194631.php#L26 and only change uid column to share_id. Another option is changing the current bfp_failed_logins table's uid column to a more generic one and use it for both features.

Also, the admin panel needs modification to configure the new feature's policy. Have you any suggestions about the blocking policy, admin configuration parameters etc. @pmaier1 @PVince81 @RavenousCtulhu?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants