-
Notifications
You must be signed in to change notification settings - Fork 5
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
Public share protect #111
Public share protect #111
Conversation
fc4bf2f
to
cdbabfd
Compare
cdbabfd
to
b4651f2
Compare
Codecov Report
@@ Coverage Diff @@
## master #111 +/- ##
============================================
+ Coverage 70.00% 73.78% +3.78%
- Complexity 38 54 +16
============================================
Files 11 13 +2
Lines 170 267 +97
============================================
+ Hits 119 197 +78
- Misses 51 70 +19
Continue to review full report at Codecov.
|
@karakayasemi can you please explain what your PR fixes? I wrote an acceptance test to check if public link shares are brute force protected but it seems they are not. |
@haribhandari07 public link share protection is using the same settings with login protection. The default configuration is ban the ip after 3 unsuccessful attempts. The ban period can be configured via settings. I can see 3 attempts in your tests, if you make it 4 or if you reduce fail tolerance you can see the effect of the PR. |
Updated tests have been added to #90 |
Description
This PR adds acceptance test to check if public link share is protected from brute force attacks.
Related PR
#90