Re: Block User from Ratflector?
|
The problem to solve?is that I see callsigns only appear to get interrogated after connection if the auth_users flag is set... Meaning you have configured for passwords. This is probably not what you want. Seeing as the only time at the beginning of the connection the callsign is interrogated, I would probably rewrite the "auth_user" method to always pull callsigns and only check the password if the auth flag is enabled. You'd also have to modify the "auth_exchange" method to allow for usernames (callsigns) and not worry about passwords not being sent in this case.
It's definitely doable -- I think this could work -- I don't see this breaking the server/client contract...
On Sun, Jan 9, 2022 at 9:25 PM Dave Slotter, W3DJS via <slotter= [email protected]> wrote: There is Python source code for this program available to be modified... In the Python source code file, "d-rats_repeater.py", there is a class called "Repeater" and it has a method called "auth_user" which is where the username / password checking is done, but it would be a very simple matter to check against the callsigns (called usernames here) and block them from connecting in the first place.
I'm surprised this was never implemented. But perhaps nobody became that annoying back then to require it?
On Sun, Jan 9, 2022 at 5:17 PM Dan Ozment < dan@...> wrote: Thanks, Daryl.? I've got them listed in igooreregex as you described above.? I also included their call sign in the ignoreregex field.? Like this -?\[QST\] \[CQCQCQ\] CT1EBQ CT1EDG.? Then I created folders for QST, CQCQCQ, and each call sign. I just hate having to ask all of our local users to do that.? Wish I could get them to stop spamming my ratflector.?
I will take Dave's suggestion and send them a polite email.? Let's see if that works.
Also, thanks for the suggestion on adding a password.? I've wondered how that worked.? I've kicked around the idea of changing the port we listen on to something other than 9000.
|
Dave Slotter, W3DJS