Module reference counting for shash is incorrect: when
a new shash transformation is created the refcount is not
increased as it should.
Signed-off-by: Adrian-Ken Rueegsegger
---
crypto/shash.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/crypto/shash.c b/crypto
Hi,
I would like to add that you can even handle the TLS/DTLS/SSL packet formation
in the kernel as well if you provide an algorithms that does just that. Right
now, most user just use the kernel for the hashing and cipher parts. There is
no reason that the current framework cannot handle proce
Pierre Habouzit wrote:
>
> So let me rephrase that to be sure we've understood each other. What you
> suggest is to have an IKE-like daemon dealing with the keys and all the
> handshakes, and that the kernel would only deal with the symmetric
> ciphers used on the data path. Is that right ?
Eithe
On Fri, Jan 30, 2009 at 03:25:06AM +, Herbert Xu wrote:
> Pierre Habouzit wrote:
> >
> > My endgame is simple, I'd like to see an in-kernel SSL/TLS
> > implementation in Linux happen. There are many reasons to want that,
> > ranging from performance reasons (waking the userland each time you
>
