On Sun, Jul 02, 2006 at 09:40:37AM -0700, David Miller wrote:
>
> You're using a blocking notifier because we have all of those
> semaphores and stuff to grab here anyways, right?
Yes, this is ultra-slow path (module loading/unloading, loading
an algorithm for the first time) so might as well use
On Sun, Jul 02, 2006 at 09:39:45AM -0700, David Miller wrote:
>
> So the templates are still using pure module references not object
> references? They won't have the same kind of refcounting issues
> the algorithms will have now?
Unlike algorithms, templates are not directly used by algorithms
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:25:01 +1000
> [CRYPTO] digest: Removed old HMAC implementation
>
> This patch removes the old HMAC implementation now that nobody uses it
> anymore.
>
> Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[E
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:24:35 +1000
> [SCTP]: Use HMAC template
>
> This patch converts SCTP to use the new HMAC template.
>
> Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
-
To unsubscribe from this list:
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:23:42 +1000
> [IPSEC]: Use HMAC template
>
> This patch converts IPsec to use the new HMAC template. The names of
> existing simple digest algorithms may still be used to refer to their
> HMAC composites.
>
> The same structure can b
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:23:09 +1000
> [CRYPTO] tcrypt: Use HMAC template
>
> This patch converts tcrypt to use the new HMAC template rather than the
> hard-coded version of HMAC.
>
> Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Signed-off-by: David S. Mill
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:22:42 +1000
> [CRYPTO] hmac: Add crypto template implementation
>
> This patch rewrites HMAC as a crypto template. This means that HMAC is no
> longer a hard-coded part of the API. It's now a template that generates
> standard digest
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:22:12 +1000
> [CRYPTO] digest: Added direct SG update and digest interface
>
> This patch allows digest algorithms to provide an SG update function
> as well as a direct digest function. If the SG update function is
> present, it will
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:21:44 +1000
> [CRYPTO] api: Added spawns
>
> Spawns lock a specific crypto algorithm in place. They can then be used
> with crypto_spawn_tfm to allocate a tfm for that algorithm. When the base
> algorithm of a spawn is deregistered,
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:21:20 +1000
> [CRYPTO] api: Allow algorithm lookup by type
>
> This patch also adds the infrastructure to pick an algorithm based on
> their type. For example, this allows you to select the encryption
> algorithm "aes", instead of any
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:20:54 +1000
> [CRYPTO] api: Add cryptomgr
>
> The cryptomgr module is a simple manager of crypto algorithm instances.
> It ensures that parameterised algorithms of the type tmpl(alg) (e.g.,
> cbc(aes)) are always created.
>
> This is
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:20:31 +1000
> [CRYPTO] api: Added event notification
>
> This patch adds a notifier chain for algorithm/template registration events.
> This will be used to register compound algorithms such as cbc(aes). In
> future this will also be
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:20:09 +1000
> [CRYPTO] api: Add template registration
>
> A crypto_template generates a crypto_alg object when given a set of
> parameters. this patch adds the basic data structure fo templates
> and code to handle their registration/
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:19:46 +1000
> [CRYPTO] api: Add crypto_alg reference counting
>
> Up until now we've relied on module reference counting to ensure that the
> crypto_alg structures don't disappear from under us. This was good enough
> as long as each
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 00:19:24 +1000
> [CRYPTO] api: Rename crypto_alg_get to crypto_mod_get
>
> The functions crypto_alg_get and crypto_alg_put operates on the crypto
> modules rather than the algorithms. Therefore it makes sense to call
> them crypto_mod_ge
Hi:
[CRYPTO] digest: Removed old HMAC implementation
This patch removes the old HMAC implementation now that nobody uses it
anymore.
Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: h
Hi:
[SCTP]: Use HMAC template
This patch converts SCTP to use the new HMAC template.
Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: htt
Hi:
[IPSEC]: Use HMAC template
This patch converts IPsec to use the new HMAC template. The names of
existing simple digest algorithms may still be used to refer to their
HMAC composites.
The same structure can be used by other MACs such as AES-XCBC-MAC.
Signed-off-by: Herbert Xu <[EMAIL PROTEC
Hi:
[CRYPTO] tcrypt: Use HMAC template
This patch converts tcrypt to use the new HMAC template rather than the
hard-coded version of HMAC.
Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home P
Hi:
[CRYPTO] hmac: Add crypto template implementation
This patch rewrites HMAC as a crypto template. This means that HMAC is no
longer a hard-coded part of the API. It's now a template that generates
standard digest algorithms like any other.
The old HMAC is preserved until all current users a
Hi:
[CRYPTO] digest: Added direct SG update and digest interface
This patch allows digest algorithms to provide an SG update function
as well as a direct digest function. If the SG update function is
present, it will be used instead of the normal update interface. That
is, the algorithm will be
Hi:
[CRYPTO] api: Added spawns
Spawns lock a specific crypto algorithm in place. They can then be used
with crypto_spawn_tfm to allocate a tfm for that algorithm. When the base
algorithm of a spawn is deregistered, all its spawns will be automatically
removed.
Signed-off-by: Herbert Xu <[EMAIL
Hi:
[CRYPTO] api: Allow algorithm lookup by type
This patch also adds the infrastructure to pick an algorithm based on
their type. For example, this allows you to select the encryption
algorithm "aes", instead of any algorithm registered under the name
"aes". For now this is only accessible int
Hi:
[CRYPTO] api: Add cryptomgr
The cryptomgr module is a simple manager of crypto algorithm instances.
It ensures that parameterised algorithms of the type tmpl(alg) (e.g.,
cbc(aes)) are always created.
This is meant to satisfy the needs for most users. For more complex
cases such as deeper co
Hi:
[CRYPTO] api: Added event notification
This patch adds a notifier chain for algorithm/template registration events.
This will be used to register compound algorithms such as cbc(aes). In
future this will also be passed onto user-space through netlink.
Signed-off-by: Herbert Xu <[EMAIL PROTE
Hi:
[CRYPTO] api: Add template registration
A crypto_template generates a crypto_alg object when given a set of
parameters. this patch adds the basic data structure fo templates
and code to handle their registration/deregistration.
Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Cheers,
--
Visi
Hi:
[CRYPTO] api: Add crypto_alg reference counting
Up until now we've relied on module reference counting to ensure that the
crypto_alg structures don't disappear from under us. This was good enough
as long as each crypto_alg came from exactly one module.
However, with parameterised crypto alg
Hi:
[CRYPTO] api: Rename crypto_alg_get to crypto_mod_get
The functions crypto_alg_get and crypto_alg_put operates on the crypto
modules rather than the algorithms. Therefore it makes sense to call
them crypto_mod_get and crypto_alg_put respectively.
This is needed because we need to have real
Hi:
This patch series adds support for parameterised algorithms. Put simply,
a parameterised algorithm (that is, a crypto template) is an object that
generates crypto algorithms given parameters.
For now the parameters are simply other crypto algorithms. However, in
future it can include intege
29 matches
Mail list logo
