diff options
| author | Jason Wright <jason@cvs.openbsd.org> | 2002-11-21 19:42:40 +0000 |
|---|---|---|
| committer | Jason Wright <jason@cvs.openbsd.org> | 2002-11-21 19:42:40 +0000 |
| commit | 35134f980321cb9228500cc2eddad675ca631097 (patch) | |
| tree | 7b4bac0e7ec4b9b615c95143a555507c8510db27 /share/man/man9/crypto.9 | |
| parent | df234af540aa3148a946aaf2c7cb99d0d430622c (diff) | |
From angelos; document new registration API
Diffstat (limited to 'share/man/man9/crypto.9')
| -rw-r--r-- | share/man/man9/crypto.9 | 19 |
1 files changed, 8 insertions, 11 deletions
diff --git a/share/man/man9/crypto.9 b/share/man/man9/crypto.9 index ecb0e2176aa..d26a2707615 100644 --- a/share/man/man9/crypto.9 +++ b/share/man/man9/crypto.9 @@ -1,4 +1,4 @@ -.\" $OpenBSD: crypto.9,v 1.19 2002/07/16 06:31:57 angelos Exp $ +.\" $OpenBSD: crypto.9,v 1.20 2002/11/21 19:42:39 jason Exp $ .\" .\" The author of this man page is Angelos D. Keromytis (angelos@cis.upenn.edu) .\" @@ -26,9 +26,9 @@ .Ft int32_t .Fn crypto_get_driverid "u_int8_t" .Ft int -.Fn crypto_register "u_int32_t" "int" "u_int16_t" "u_int32_t" "int (*)(u_int32_t *, struct cryptoini *)" "int (*)(u_int64_t)" "int (*)(struct cryptop *)" +.Fn crypto_register "u_int32_t" "int *" "int (*)(u_int32_t *, struct cryptoini *)" "int (*)(u_int64_t)" "int (*)(struct cryptop *)" .Ft int -.Fn crypto_kregister "u_int32_t" "int" "u_int32_t" "int (*)(struct cryptkop *)" +.Fn crypto_kregister "u_int32_t" "int *" "int (*)(struct cryptkop *)" .Ft int .Fn crypto_unregister "u_int32_t" "int" .Ft void @@ -440,14 +440,11 @@ as an argument (normally 0, but software-only drivers should specify .Dv CRYPTOCAP_F_SOFTWARE Ns ). For each algorithm the driver supports, it must then call .Fn crypto_register . -The first two arguments are the driver and algorithm identifiers. -The next two arguments specify the largest possible operator length (in bits, -important for public key operations) and flags (e.g., whether an hardware RNG is -available) for this algorithm. -The last three arguments must be provided in the first call to -.Fn crypto_register -and are ignored in all subsequent calls. -They are pointers to three +The first argument is the driver identifier. +The second argument is an array of +.Dv CRYPTO_ALGORITHM_MAX + 1 +elements, indicating which algorithms are supported. +The last three arguments are pointers to three driver-provided functions that the framework may call to establish new cryptographic context with the driver, free already established context, and ask for a request to be processed (encrypt, decrypt, |