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

m_sqlauth #158

Open
EllisField opened this issue Aug 8, 2018 · 3 comments
Open

m_sqlauth #158

EllisField opened this issue Aug 8, 2018 · 3 comments

Comments

@EllisField
Copy link

EllisField commented Aug 8, 2018

We have tried using https://github.com/inspircd/inspircd/blob/v2.0.26/src/modules/m_sqlauth.cpp but basically users are confused about having to use the Guest prefix to be able to connect when they don't want to register.

We want the module to work like this:

  • If database returns registration, require password.
  • If database returns no registration, do not require password or prefix, allow user to use the nickname as it is not registered.

Is it possible please that someone could help us with this request, I was thinking that just an option to the existing module could be added on whether to require the Guest prefix or not, rather than an entirely new module for very similar purpose, but ...

Alternatively, possibly the module can 'fix' it for the user and add the Guest prefix when the database returns no registration but the user did not use the Guest prefix. Either way, I do not think disconnecting users because they tried to connect using an unregistered nickname is correct ...

@genius3000
Copy link
Member

It sounds like you'd be better off using a services package (ex. Anope or Atheme). m_sqlauth 's purpose is to control connections to the server, which you sound to not really want.

@EllisField
Copy link
Author

EllisField commented Aug 8, 2018

@genius3000 the ability to allow Guests is already in the module, I just want to remove the requirement to have them prefixed with the Guest_ string. We don't run services as have no need; permanent channels only, web chat only etc. Installing that would definitely be an overkill for our needs, hence requesting this small change to the existing module.

@EllisField
Copy link
Author

Is anyone interested in doing this as a paid module (new module written to do what we need, not just modifying the existing one as suggested)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants