Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/sys/opencrypto/files.opencrypto

26 lines
847 B
Plaintext
Raw Normal View History

swcr -> swcrypto
2005-11-25 19:41:31 +03:00
# $NetBSD: files.opencrypto,v 1.17 2005/11/25 16:41:31 thorpej Exp $
Commit initial NetBSD port of the OpenCrypto Framework (OCF). This code is derived from Sam Leffler's FreeBSD port of OCF, which is in turn a port of Angelos Keromytis's OpenBSD work. Credit to Sam and Angelos, any blame for the NetBSD port to me.
2003-07-26 01:12:39 +04:00
#
#
nuke trailing whitespace
2005-02-27 01:31:44 +03:00
# Opencrypto framework.
Split opencrypto configuration into an attribute, usable by inkernel clients, and a pseudo-device for userspace access. The attribute is named `opencrypto'. The pseudo-device is renamed to "crypto", which has a dependency on "opencrypto". The sys/conf/majors entry and pseudo-device attach entrypoint are updated to match the new pseudo-device name. Fast IPsec (sys/netipsec/files.ipsec) now lists a dependency on the "opencrypto" attribute. Drivers for crypto accelerators (ubsec, hifn775x) also pull in opencrypto, as providers of opencrypto transforms.
2003-12-31 19:44:26 +03:00
# Devices that provide crypto transforms via opencrypto, or subsystems
# that use the opencrypto framework, should list opencrypto as a dependency
# to pull in the framework.
Move the opencrypto defpseudo into files.opencrypto.
2003-08-24 23:21:11 +04:00
- De-couple the software crypto implementation from the rest of the framework. There is no need to waste the space if you are only using algoritms provided by hardware accelerators. To get the software implementations, add "pseudo-device swcr" to your kernel config. - Lazily initialize the opencrypto framework when crypto drivers (either hardware or swcr) register themselves with the framework.
2005-11-25 19:16:46 +03:00
define opencrypto
file opencrypto/criov.c opencrypto
Commit initial NetBSD port of the OpenCrypto Framework (OCF). This code is derived from Sam Leffler's FreeBSD port of OCF, which is in turn a port of Angelos Keromytis's OpenBSD work. Credit to Sam and Angelos, any blame for the NetBSD port to me.
2003-07-26 01:12:39 +04:00
file opencrypto/xform.c opencrypto
Split opencrypto configuration into an attribute, usable by inkernel clients, and a pseudo-device for userspace access. The attribute is named `opencrypto'. The pseudo-device is renamed to "crypto", which has a dependency on "opencrypto". The sys/conf/majors entry and pseudo-device attach entrypoint are updated to match the new pseudo-device name. Fast IPsec (sys/netipsec/files.ipsec) now lists a dependency on the "opencrypto" attribute. Drivers for crypto accelerators (ubsec, hifn775x) also pull in opencrypto, as providers of opencrypto transforms.
2003-12-31 19:44:26 +03:00
file opencrypto/crypto.c opencrypto
Cleanup traces of previous standalone m_apply()/m_getptr().
2003-07-27 07:34:39 +04:00
- De-couple the software crypto implementation from the rest of the framework. There is no need to waste the space if you are only using algoritms provided by hardware accelerators. To get the software implementations, add "pseudo-device swcr" to your kernel config. - Lazily initialize the opencrypto framework when crypto drivers (either hardware or swcr) register themselves with the framework.
2005-11-25 19:16:46 +03:00
# Pseudo-device that provides software implementations of various cryptographic
# algorithms.
swcr -> swcrypto
2005-11-25 19:41:31 +03:00
defpseudo swcrypto: opencrypto,
- De-couple the software crypto implementation from the rest of the framework. There is no need to waste the space if you are only using algoritms provided by hardware accelerators. To get the software implementations, add "pseudo-device swcr" to your kernel config. - Lazily initialize the opencrypto framework when crypto drivers (either hardware or swcr) register themselves with the framework.
2005-11-25 19:16:46 +03:00
blowfish, des, cast128, rijndael, ripemd160, sha2, skipjack
swcr -> swcrypto
2005-11-25 19:41:31 +03:00
file opencrypto/cryptosoft.c swcrypto
file opencrypto/deflate.c swcrypto # wrapper around zlib
Split opencrypto configuration into an attribute, usable by inkernel clients, and a pseudo-device for userspace access. The attribute is named `opencrypto'. The pseudo-device is renamed to "crypto", which has a dependency on "opencrypto". The sys/conf/majors entry and pseudo-device attach entrypoint are updated to match the new pseudo-device name. Fast IPsec (sys/netipsec/files.ipsec) now lists a dependency on the "opencrypto" attribute. Drivers for crypto accelerators (ubsec, hifn775x) also pull in opencrypto, as providers of opencrypto transforms.
2003-12-31 19:44:26 +03:00
# Pseudo-device for userspace access to opencrypto
# (and thus crypto hardware accelerators).
- De-couple the software crypto implementation from the rest of the framework. There is no need to waste the space if you are only using algoritms provided by hardware accelerators. To get the software implementations, add "pseudo-device swcr" to your kernel config. - Lazily initialize the opencrypto framework when crypto drivers (either hardware or swcr) register themselves with the framework.
2005-11-25 19:16:46 +03:00
defpseudo crypto: opencrypto
Split opencrypto configuration into an attribute, usable by inkernel clients, and a pseudo-device for userspace access. The attribute is named `opencrypto'. The pseudo-device is renamed to "crypto", which has a dependency on "opencrypto". The sys/conf/majors entry and pseudo-device attach entrypoint are updated to match the new pseudo-device name. Fast IPsec (sys/netipsec/files.ipsec) now lists a dependency on the "opencrypto" attribute. Drivers for crypto accelerators (ubsec, hifn775x) also pull in opencrypto, as providers of opencrypto transforms.
2003-12-31 19:44:26 +03:00
file opencrypto/cryptodev.c crypto