alpha
Login
or
Join now
snowfields.name
/
atheme
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
[READ-ONLY] Mirror of https://github.com/VibeDevelopers/atheme. Modified fork of atheme IRC Services
www.vibetalk.net/
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
atheme
/
modules
/
crypto
/
legacy
/
at
master
11 files
Aaron Jones
Update my e-mail address
5y ago
a67197d2
Makefile
Update my e-mail address
5 years ago
anope-enc-sha256.c
Update my e-mail address
5 years ago
base64.c
Update my e-mail address
5 years ago
crypt3-des.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
crypt3-md5.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
ircservices.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
rawhash.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
rawmd5.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
rawsha1.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
rawsha2-256.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago
rawsha2-512.c
modules/crypto/: move legacy modules to subdirectory This does not rename the modules themselves; you still load them with the standard modules/crypto/ prefix. This is just to tidy up the source tree. This also removes the modules/crypto/posix compatibility module. Please see the Password Hashing Modules section of dist/atheme.conf.example if you still use this module on v7.2 or older, for migration instructions. Finally, document the ./configure options necessary to have each module built, and elaborate on the distinction between pbkdf2 and pbkdf2v2.
6 years ago