Re: crypto(9) choose another driver if we cannot open a session on it

2008-12-12 Thread Patrick Lamaizière
Le Wed, 10 Dec 2008 14:50:51 -0800, Sam Leffler a écrit : Hello, > > Which code exactly? Yes I'm curious :-) > > > > I'm thinking about how to remove the need for a device to support > > all the algorithms when we open a session. By using a fake "crypto > > virtual device" to open and dispatch c

Re: crypto(9) choose another driver if we cannot open a session on it

2008-12-10 Thread Sam Leffler
Patrick Lamaizière wrote: Le Mon, 8 Dec 2008 21:21:55 +0100, Philip Paeps <[EMAIL PROTECTED]> a écrit : Hello, On 2008-12-07 22:45:51 (+0100), Patrick Lamaizière <[EMAIL PROTECTED]> wrote: I wrote a small patch to allow the crypto framework to choose another cryptographic driver if we

Re: crypto(9) choose another driver if we cannot open a session on it

2008-12-10 Thread Patrick Lamaizière
Le Mon, 8 Dec 2008 21:21:55 +0100, Philip Paeps <[EMAIL PROTECTED]> a écrit : Hello, > On 2008-12-07 22:45:51 (+0100), Patrick Lamaizière > <[EMAIL PROTECTED]> wrote: > > I wrote a small patch to allow the crypto framework to choose > > another cryptographic driver if we cannot open a session on

Re: crypto(9) choose another driver if we cannot open a session on it

2008-12-08 Thread Philip Paeps
On 2008-12-07 22:45:51 (+0100), Patrick Lamaizière <[EMAIL PROTECTED]> wrote: > I wrote a small patch to allow the crypto framework to choose another > cryptographic driver if we cannot open a session on the driver. Very cool. :-) I've been hacking on this too, mainly to get rid of the code dupli

crypto(9) choose another driver if we cannot open a session on it

2008-12-07 Thread Patrick Lamaizière
Hello, I wrote a small patch to allow the crypto framework to choose another cryptographic driver if we cannot open a session on the driver. The current version selects the driver that handles all the requested algorithms and with the less count of active sessions. But this is not enough, by exam