From 7f00015727fab50e37de46aa90d218b31c852c87 Mon Sep 17 00:00:00 2001 From: brain Date: Mon, 9 Apr 2007 16:42:09 +0000 Subject: Add config to support disabling of HMAC, and tidy up to detect if the other side hasnt got it enabled and we did, or if we enabled it and dont have sha256 (that would be an oops) git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@6776 e03df62e-2008-0410-955e-edbf42e46eb7 --- docs/inspircd.conf.example | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'docs/inspircd.conf.example') diff --git a/docs/inspircd.conf.example b/docs/inspircd.conf.example index aee35722e..b26ee7ef2 100644 --- a/docs/inspircd.conf.example +++ b/docs/inspircd.conf.example @@ -822,6 +822,18 @@ # invites annother user. If you consider this to be # # unnecessary noise, explicitly set this to no. # # # +# disablehmac - If you are linking your InspIRCd to older versions # +# then you can specify this option and set it to # +# yes. 1.1.6 and above support HMAC and challenge- # +# response for password authentication. These can # +# greatly enhance security of your server to server # +# connections when you are not using SSL (as is the # +# case with a lot of larger networks). Linking to # +# older versions of InspIRCd should not *usually* be # +# a problem, but if you have problems with HMAC # +# authentication, this option can be used to turn it # +# off. # +# # -- cgit v1.2.3