summaryrefslogtreecommitdiff
path: root/conf/inspircd.censor.example
diff options
context:
space:
mode:
authorbrain <brain@e03df62e-2008-0410-955e-edbf42e46eb7>2006-12-05 18:17:23 +0000
committerbrain <brain@e03df62e-2008-0410-955e-edbf42e46eb7>2006-12-05 18:17:23 +0000
commit9591819654a80241874e9ce85c40e162d8c5ccbb (patch)
treedac9057df928f428a8f21b77a4fc7f879fe7d877 /conf/inspircd.censor.example
parent54beb35ef189b58dee7851a60fdb0f7b2430855f (diff)
Seperate out sha256 into m_sha256.so. API is identical to MD5 except where the class names are MD5 for MD5, these are SHA256... duh ;)
Now we're left with a dialemma - is m_opersha256.cpp now pointless? Does anyone use both sha256 and md5 together? Should we just rename this to m_oper_hash, and have them pick their encryption in the config? :P git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@5858 e03df62e-2008-0410-955e-edbf42e46eb7
Diffstat (limited to 'conf/inspircd.censor.example')
0 files changed, 0 insertions, 0 deletions