Skip to content

/ server

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

Jump to bottom

Consider brute-force protection on the Server-to-Server Sharing Endpoint #478

Open
LukasReschke opened this issue Jul 20, 2016 · 0 comments
Open

Consider brute-force protection on the Server-to-Server Sharing Endpoint #478

LukasReschke opened this issue Jul 20, 2016 · 0 comments
Labels
1. to develop enhancement feature: sharing security
Projects
Security Hardenings

Comments

@LukasReschke
Copy link
Member

@LukasReschke LukasReschke commented Jul 20, 2016 •
edited by rullzer

This is a little bit a trickier one, having brute-force protection there as well would be nice. However, the way S2S is implemented right now may lead to people locking out servers by intention.

Needs some more thoughts as well as status messages so that the other Nextcloud partiall throttles. Related to #437
@MorrisJobke MorrisJobke mentioned this issue May 22, 2017
Merged
@nextcloud-bot nextcloud-bot added the stale label Jun 20, 2018
@nextcloud-bot nextcloud-bot mentioned this issue Nov 7, 2018
Closed
@nextcloud-bot nextcloud-bot mentioned this issue Nov 29, 2018
Closed
@skjnldsv skjnldsv added the 1. to develop label Jun 12, 2019
@nextcloud-stale nextcloud-stale bot removed the stale label Jun 12, 2019
@mathiasconradt mathiasconradt mentioned this issue Feb 6, 2021
Open
@gisforgirard gisforgirard mentioned this issue Feb 19, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1. to develop enhancement feature: sharing security
Projects
Security Hardenings
  
Backlog
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@LukasReschke @skjnldsv @nextcloud-bot