Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ. As of October 27th, please open all new issues in the Red Hat Customer Portal .
We currently have an internal IRC server that we use day to day. It may be best if this moved on to the forge as a forge service. Perhaps with enhanced security features.
Description
We currently have an internal IRC server that we use day to day. It may be best if this moved on to the forge as a forge service. Perhaps with enhanced security features.
I've deployed a modified version of ngircd to the forge. It accepts ssl connections on port 6667 and authenticates users against Crowd. It restricts nicks used so that they must at least begin with the user id. This allows the same user to log in multiple times with different nicks but still other folks some level of protection against impersonations.
What's needed now is implementing some kind of channel security so that some channels can be restricted to user in a given crowd group.
Hiram Chirino added a comment - 05/May/09 03:09 PM I've deployed a modified version of ngircd to the forge. It accepts ssl connections on port 6667 and authenticates users against Crowd. It restricts nicks used so that they must at least begin with the user id. This allows the same user to log in multiple times with different nicks but still other folks some level of protection against impersonations.
What's needed now is implementing some kind of channel security so that some channels can be restricted to user in a given crowd group.
Hiram Chirino added a comment - 20/May/09 12:37 PM Forge IRC is now in production and only allowing employees to login so per channel security is not that big an issue.
New Feature
Resolved
Major
IRC Server
What's needed now is implementing some kind of channel security so that some channels can be restricted to user in a given crowd group.