On Mon, Aug 23, 2010 at 11:37:40AM -0400, Miloslav Trmac wrote:
I can see almost no overlap between the two sets of requirements. Probably
the only common use case is handling session keys (e.g. keys used in a
kerberos ticket), which should be stored in the kernel for the duration of
the
help
--
JFCh jchad...@redhat.com
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
- Herbert Xu herb...@gondor.hengli.com.au wrote:
On Mon, Aug 23, 2010 at 11:37:40AM -0400, Miloslav Trmac wrote:
I can see almost no overlap between the two sets of requirements.
Probably the only common use case is handling session keys (e.g. keys
used in a kerberos ticket), which
On Mon, Sep 6, 2010 at 11:50, Miloslav Trmac m...@redhat.com wrote:
- Herbert Xu herb...@gondor.hengli.com.au wrote:
On Mon, Aug 23, 2010 at 11:37:40AM -0400, Miloslav Trmac wrote:
I have seriously considered the keyring API, and this is what I came
up with - but I'd love to be shown a
On Mon, Sep 6, 2010 at 15:13, Nikos Mavrogiannopoulos
n.mavrogiannopou...@gmail.com wrote:
On 09/06/2010 08:00 PM, Kyle Moffett wrote:
The kernel keyring service is basically a system-wide data storage
service. /dev/crypto needs a quick way to refer to short-lived,
usually process-local,
- Kyle Moffett k...@moffetthome.net wrote:
On Mon, Sep 6, 2010 at 11:50, Miloslav Trmac m...@redhat.com wrote:
- Herbert Xu herb...@gondor.hengli.com.au wrote:
On Mon, Aug 23, 2010 at 11:37:40AM -0400, Miloslav Trmac wrote:
I have seriously considered the keyring API, and this is
Nikos Mavrogiannopoulos n...@gnutls.org wrote:
Hello,
I was checking the crypto_xor() function and it is for some reason
limited to 32 bit integers. Why not make it depend on the architecture
by replacing the u32 with unsigned long? That way 64bit machines should
perform xor with less
On Mon, Sep 6, 2010 at 17:11, Nikos Mavrogiannopoulos
n.mavrogiannopou...@gmail.com wrote:
I suppose you mean the reference to the internal representation of the
key. This might be valid for few seconds until the required operation is
over.
This is not really what I would call storage. The
Below is a patch to update the broken web addresses, in crypto/*
that I could locate. Some are just simple typos that needed to be
fixed, and some had a change in location altogether..
let me know if any of them need to be changed and such.
Signed-off-by: Justin P. Mattock
