mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #94] Create a brute force login protection module set #75
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @jasonmunro on GitHub (Jun 28, 2016).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/94
Originally assigned to: @Danelif on GitHub.
lots of great ideas on this here:
https://www.owasp.org/index.php/Blocking_Brute_Force_Attacks
@marclaporte commented on GitHub (May 7, 2024):
@Danelif please advise.
@Danelif commented on GitHub (May 7, 2024):
Alright
@Danelif commented on GitHub (May 7, 2024):
I have read this article carefully https://www.owasp.org/index.php/Blocking_Brute_Force_Attacks and found it very relevant. But some techniques are not included in it.
If we want to create brute-force login protection, consider including the (2-3) FA technique (2-3 Factor Authentication). The user might provide a unique OTP sent to his email address or mobile phone once the username/password is correct.
Also, The limitation of attempting to log in can be considered from a single IP address. If the limit is reached we can suggest the user to recover it password by emailing an OTP to the email in our database.
@marclaporte commented on GitHub (May 7, 2024):
@Danelif Thank you, please look at how it is done in Tiki to get some more good ideas.
@Danelif commented on GitHub (May 16, 2024):
@marclaporte In tiki 2FA is done using Google2FA php library. Good idea indeed. Instead of using OTP, in Tiki, we use TOTP. But the only problem is that there is not much documentation and usage I wonder why?
@marclaporte commented on GitHub (May 17, 2024):
Some docs:
TOTP uses time, so the code changes every 30 seconds.
@Danelif commented on GitHub (Jul 10, 2024):
@marclaporte I have seen how 2FA works in tiki. It could be great to to the same in cypht
@marclaporte commented on GitHub (Jul 10, 2024):
ok, please proceed as a medium priority. High priority is fixing bugs before adding new features.