Skip to content
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

Bans on real ips #46

Open
GeorgeGR opened this issue Jun 25, 2014 · 10 comments
Open

Bans on real ips #46

GeorgeGR opened this issue Jun 25, 2014 · 10 comments

Comments

@GeorgeGR
Copy link

Hello,

i would like to request a module for inspircd.
I would like to disable the banning of ips. I mean this:

mode #channel +b *!*@1.2.3.4 or *!*@1.2.3.4/32 to be dissalowed and only made available the cloaked ips.

Thank you

@WindowsUser
Copy link
Contributor

I just wonder why you would want this, since auto-cloaking (not vhosts) does not strictly completely hide someone's IP.

@TurkDesk
Copy link

they do hide at least, but by the IP's bening match when they are banned, it's little leak to find out ips, a little option to match/not much the IP's or work only cloak or IP too option would be handy.

@WindowsUser
Copy link
Contributor

If IPs are cloaked, ordinary channel operators would not have any means of knowing someone's real IP address in order to set bans, unless they managed to decrypt the cloaking my m_cloaking.so, which is possible anyways.

The only way an ordinary channel operator could find out someone's IP address otherwise is to try to brute-force by setting a lot of bans. There are literally billions of IPv4 addresses and billions of billions of billions of billions of IPv6 addresses, making such brute-forcing impractical.

A module to implement this would be easy, but I just don't see the need for it.

@DjSlash
Copy link

DjSlash commented Jun 26, 2014

I believe people already stated they don't see the use for this and thus not wanting to waste time on it. Only suggestion I would make is to write it yourself.

@satmd
Copy link
Contributor

satmd commented Jun 26, 2014

It does make sense when ircops help a chanop to provide a specific iprange to ban from that channel while not banning it from the complete net.

or for a channel which users all come from a specific subnet, it could be +iI 1.2.3.0/24

@GeorgeGR
Copy link
Author

Well i wouldnt ask such a module if there was no reason or if i could write it on my own. There is an issue that Attila is aware of and hence i requested this module

@HelixSpiral
Copy link
Contributor

Having unbanable IPs would effectively prevent banning on anyone connecting that has an ip that doesn't resolve to some sort of a host.

Yes. This may prevent users determining the IP of a user through trial and error ban/unban. But that is a much smaller risk than having unbanable bots connecting and spamming.

@GeorgeGR
Copy link
Author

we have cloaking so only ircops can see ips. ircops never set bans on real ips and all ops set bans on cloaked. also ips dont resolve as far as i know

@HelixSpiral
Copy link
Contributor

X.X.X.X -> <cloaked>.res.rr.com or something similar

But not all IPs will do that. So if you remove the ability to ban just the IP you have no way to ban the user.

@SadieCat
Copy link
Member

@shawn-smith IPs which do not have RDNS can be cloaked too albeit in a different way.

@inspircd inspircd deleted a comment from SoniEx2 Sep 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

7 participants