[Security issue]: Password bruteforcing about send HOT 4 OPEN

Would be pretty cool. The only thing im not sure about is:
- Make the file expire instantly after X failed attempts
This would make it possible for someone to delete someone else shared files

from send.

Would be pretty cool. The only thing im not sure about is: - Make the file expire instantly after X failed attempts This would make it possible for someone to delete someone else shared files

You have a good point actually.
But as I've stated in the final note, all of these features would preferably have to be entirely optional, and not enforced by default.

So if a user explicitly wants to enable such a feature, they should be aware of the possible implications and/or drawbacks for doing so.

In any case, I just listed a few ideas that came into mind while writing up about the issue, so I'm sure there are better alternatives :)

from send.

I disagree with enforcing password policies.

Fail2ban sounds like a better implementation.

from send.

I disagree with enforcing password policies.

Again, no enforcing.

Everything listed under the suggested features should be optional features.
Meaning the user decides whether or not to enforce a password policy for their files.

It should NOT be the default.

from send.