Hi all, Please see below a bug report submitted to the Debian BTS.
found 698027 1:7.2.2.dfsg.2-9 tags 698027 + confirmed forwarded 698027 b...@ircd-hybrid.org severity 698027 minor thanks On Sun, Jan 13, 2013 at 02:52:55AM +0000, Mark Cunningham wrote: > SSL support isn't included by default however the server does not fail to > launch if ssl options are included in config > > When I tested it, connect blocks were simply dismissed if they included config > options such as cryptlink flag or encrypted = yes; > Meaning, if a connect block had one of these options and you were to do > /sconnect connectblockname in order to connect to the server, > the server would come back with connect block not found. > > Suggested action: > Upon option that would require ssl support being found in the config file, the > server should fail to start, indicate which option it is failing on and link > to > the /usr/share/doc/ircd-hybrid file that explains about ssl support. > > This may be a drastic approach as people may have configs with ssl options > running at the moment and this update will stop the server from running. > > At the very least, output a clear message to the log files about ssl support > and connect block being ignored with them. Without it, there are no clear > indications what would cause a connect block not to be recognised. I can confirm that this issue arises at least with flags = ssl on a listener, and I agree that the options you suggest make sense. I'm copying in upstream also as this isn't a Debian-specific problem. Thanks, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
