Am Dienstag, den 08.03.2005, 00:08 -0500 schrieb Kyle Moffett:
> Did you include support for the new key/keyring infrastructure
> introduced
> a couple versions ago by David Howells? It allows userspace to create
> and
> manage various sorts of "keys" in kernelspace. If you create and
>
On Tue, 2005-03-08 at 08:24 -0500, Joshua Jackson wrote:
> On Monday 07 March 2005 4:49 pm, Evgeniy Polyakov wrote:
> >
> > Unfortunately acrypto patch is more than 200kb, so neither mail list
> > will accept it, so I've sent it in such form :)
> >
>
> As per the FAQ, very large patches are often
On Tue, 2005-03-08 at 08:24 -0500, Joshua Jackson wrote:
On Monday 07 March 2005 4:49 pm, Evgeniy Polyakov wrote:
Unfortunately acrypto patch is more than 200kb, so neither mail list
will accept it, so I've sent it in such form :)
As per the FAQ, very large patches are often best
Am Dienstag, den 08.03.2005, 00:08 -0500 schrieb Kyle Moffett:
Did you include support for the new key/keyring infrastructure
introduced
a couple versions ago by David Howells? It allows userspace to create
and
manage various sorts of keys in kernelspace. If you create and
register
a
On Tue, 8 Mar 2005 09:46:30 -0500
Kyle Moffett <[EMAIL PROTECTED]> wrote:
> On Mar 08, 2005, at 08:07, Evgeniy Polyakov wrote:
> > On Tue, 8 Mar 2005 07:22:01 -0500 Kyle Moffett <[EMAIL PROTECTED]>
> > wrote:
> >> I'm not exactly familiar with asynchronous block device, but I'm
> >> guessing
On Mar 08, 2005, at 08:07, Evgeniy Polyakov wrote:
On Tue, 8 Mar 2005 07:22:01 -0500 Kyle Moffett <[EMAIL PROTECTED]>
wrote:
I'm not exactly familiar with asynchronous block device, but I'm
guessing that it would need to get its crypto keys from the user
somehow, no? If so, then the best way of
On Monday 07 March 2005 4:49 pm, Evgeniy Polyakov wrote:
>
> Unfortunately acrypto patch is more than 200kb, so neither mail list
> will accept it, so I've sent it in such form :)
>
As per the FAQ, very large patches are often best submitted as a URL. In case
you don't have a place to host it,
On Tue, 8 Mar 2005 07:22:01 -0500
Kyle Moffett <[EMAIL PROTECTED]> wrote:
> On Mar 08, 2005, at 04:37, Evgeniy Polyakov wrote:
> >>
> >> Did you include support for the new key/keyring infrastructure
> >> introduced a couple versions ago by David Howells? It allows
> >> user-space to create and
On Mar 08, 2005, at 04:37, Evgeniy Polyakov wrote:
Did you include support for the new key/keyring infrastructure
introduced a couple versions ago by David Howells? It allows
user-space to create and manage various sorts of "keys" in
kernel-space. If you create and register a few keytypes for
On Mon, Mar 07, 2005 at 11:37:32PM +0300, Evgeniy Polyakov wrote:
>
> I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
Thanks for your work. I'll be reviewing your approach as well as others
over the next week or so.
Cheers,
--
Visit Openswan at http://www.openswan.org/
On Tue, 8 Mar 2005 00:08:35 -0500
Kyle Moffett <[EMAIL PROTECTED]> wrote:
> On Mar 07, 2005, at 15:37, Evgeniy Polyakov wrote:
> > I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
> > It supports following features:
> > - multiple asynchronous crypto device queues
> > -
On Tue, 8 Mar 2005 00:08:35 -0500
Kyle Moffett [EMAIL PROTECTED] wrote:
On Mar 07, 2005, at 15:37, Evgeniy Polyakov wrote:
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
It supports following features:
- multiple asynchronous crypto device queues
- crypto session
On Mon, Mar 07, 2005 at 11:37:32PM +0300, Evgeniy Polyakov wrote:
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
Thanks for your work. I'll be reviewing your approach as well as others
over the next week or so.
Cheers,
--
Visit Openswan at http://www.openswan.org/
On Mar 08, 2005, at 04:37, Evgeniy Polyakov wrote:
Did you include support for the new key/keyring infrastructure
introduced a couple versions ago by David Howells? It allows
user-space to create and manage various sorts of keys in
kernel-space. If you create and register a few keytypes for
On Tue, 8 Mar 2005 07:22:01 -0500
Kyle Moffett [EMAIL PROTECTED] wrote:
On Mar 08, 2005, at 04:37, Evgeniy Polyakov wrote:
Did you include support for the new key/keyring infrastructure
introduced a couple versions ago by David Howells? It allows
user-space to create and manage various
On Monday 07 March 2005 4:49 pm, Evgeniy Polyakov wrote:
Unfortunately acrypto patch is more than 200kb, so neither mail list
will accept it, so I've sent it in such form :)
As per the FAQ, very large patches are often best submitted as a URL. In case
you don't have a place to host it, you
On Tue, 8 Mar 2005 09:46:30 -0500
Kyle Moffett [EMAIL PROTECTED] wrote:
On Mar 08, 2005, at 08:07, Evgeniy Polyakov wrote:
On Tue, 8 Mar 2005 07:22:01 -0500 Kyle Moffett [EMAIL PROTECTED]
wrote:
I'm not exactly familiar with asynchronous block device, but I'm
guessing that it would need
On Mar 07, 2005, at 15:37, Evgeniy Polyakov wrote:
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
It supports following features:
- multiple asynchronous crypto device queues
- crypto session routing
- crypto session binding
- modular load balancing
- crypto session
On Mon, 2005-03-07 at 23:37 +0300, Evgeniy Polyakov wrote:
> I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
Thanks Evgeniy for your work! Even though, it's great what's inside, I'm
afraid it will be judged by the form of its presentation. A patch should
be something
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
It supports following features:
- multiple asynchronous crypto device queues
- crypto session routing
- crypto session binding
- modular load balancing
- crypto session batching genetically implemented by design
- crypto
acrypto has
> not been considered by the maintainers to be merged soon, so patch
> splitting doesn't make sense anyway at the moment.
Unfortunately acrypto patch is more than 200kb, so neither mail list
will accept it, so I've sent it in such form :)
Actually the most interesting is the first e-ma
anyway at the moment.
Unfortunately acrypto patch is more than 200kb, so neither mail list
will accept it, so I've sent it in such form :)
Actually the most interesting is the first e-mail with subject line
[0/many] Acrypto - asynchronous crypto layer for linux kernel 2.6 which
has description
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
It supports following features:
- multiple asynchronous crypto device queues
- crypto session routing
- crypto session binding
- modular load balancing
- crypto session batching genetically implemented by design
- crypto
On Mon, 2005-03-07 at 23:37 +0300, Evgeniy Polyakov wrote:
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
Thanks Evgeniy for your work! Even though, it's great what's inside, I'm
afraid it will be judged by the form of its presentation. A patch should
be something
On Mar 07, 2005, at 15:37, Evgeniy Polyakov wrote:
I'm pleased to announce asynchronous crypto layer for Linux kernel 2.6.
It supports following features:
- multiple asynchronous crypto device queues
- crypto session routing
- crypto session binding
- modular load balancing
- crypto session
25 matches
Mail list logo
