Closed edmund-huber closed 4 years ago
Implementation notes:
xinetd's banner_fail
feature might be a good fit for this.
note: Advertising an STS policy on this plaintext server which matches one on the server running on 6697 may let clients with newer software automagically use 6697 without needing to do anything manual (depending on the duration time and how often they connect after getting the initial policy, of course). Depends on having a non-self-signed cert on 6697 and possibly pushing a CAP LS reply line after dumping that MOTD to the user (if the 6667 software isn't a full ircd)
I'm going to implement this in oragono, but I have mixed feelings about deploying it to darwin, because I feel like opening port 6667 inherently makes the server more vulnerable to passive monitoring (e.g., if some client connects and immediately tries to send a SASL PLAIN auth blob).
This is a wontfix.
Some MOTD like:
Then it hangs up.