View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006084 | unreal | ircd | public | 2022-04-06 02:54 | 2022-04-06 09:39 |
| Reporter | Valware | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| Product Version | 6.0.3 | ||||
| Summary | 0006084: Please allow '/AUTH'ing after connection handshake | ||||
| Description | Hi there! Request: Please could you add the ability for a user to be able to '/AUTH' after they have connected, instead of it being restricted to the authprompt module (before connect). This is for completeness, as an emulation of SASL is still a SASL in this respect, and clients should still be able to take full use of the SASL mechanism as a form of identification using including this compatibility layer, as it is a very useful command. Thanks for considering! Have a great week | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I think your suggestion (idea) is fine :) So then it comes down to how to do this, not just literally making it available post-connect, but also under the hood.... do we split authprompt up into two pieces (auth and authprompt), that does sound preferrable.. but only if it does not complicate things TOO much, and, yeah.. that kind of stuff. Don't really have time to think about that next couple of days though |
