-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
(Add) Ip blocking system #3136
(Add) Ip blocking system #3136
Conversation
{ | ||
Schema::create('blocked_ips', function (Blueprint $table): void { | ||
$table->id(); | ||
$table->unsignedInteger('user_id'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should block ranges instead of IPs directly. Blocked IPs aren't always associated with a user, so the user_id should be nullable as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the user_id here is not related to a blocked member but is just to show what staff member initiated the block on said IP.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, that makes sense. Ranges would still be useful however if easy enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wildcards would be nice also. xxx.xxx.xxx.* for instance, to block the /24
Co-authored-by: Roardom <78790963+Roardom@users.noreply.github.com>
No description provided.