Age | Commit message (Collapse) | Author | |
---|---|---|---|
2006-12-05 | More tweakage | brain | |
git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@5865 e03df62e-2008-0410-955e-edbf42e46eb7 | |||
2006-12-05 | . | brain | |
git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@5864 e03df62e-2008-0410-955e-edbf42e46eb7 | |||
2006-12-05 | Seperate out sha256 into m_sha256.so. API is identical to MD5 except where ↵ | brain | |
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 |