Opencrypto patch/driver code upload

Hi All, I've a patch to opencrypto and I have a crypto driver that I would like to present for inclusion with the freebsd 7 release. Could you give me some pointers on getting that done? The opencrypto patch is relavent for FreeBSD 8 and 9 also... Some questions for the driver release:

Re: FreeBSD 7.1 opencrypto -- kern.cryptodevallowsoft

openssl speed -evp des-ede3-cbc -engine cryptodev works! thanks Brian. looking for that patch now... 2009/5/19 Patrick Lamaizière patf...@davenulle.org: Le Tue, 19 May 2009 14:25:24 +0100, Brendan Kennedy brendan.kenn...@gmail.com: Agreed! The driver doesn't seem to be getting executed

Re: FreeBSD 7.1 opencrypto -- kern.cryptodevallowsoft

to extract useful statistics out of the driver's kernel data structures. ~BAS On Mon, 2009-05-18 at 11:21 +0100, Brendan Kennedy wrote: Hi Brian, Patrick, Thanks for your responses. I agree that it looks like a bug! I'm a bit of a newb to FreeBSD. Where should I go to log this? I ran

Re: FreeBSD 7.1 opencrypto -- kern.cryptodevallowsoft

...@noc.cfi.pgh.pa.us: On Tue, 2009-05-12 at 19:14 +0100, Brendan Kennedy wrote: Hi All, I'm trying to test a hardware crypto driver, but want to run my tests through the software driver first (and possibly use the software driver to validate results). I have set the following in my GENERIC conf

FreeBSD 7.1 opencrypto -- kern.cryptodevallowsoft

Hi All, I'm trying to test a hardware crypto driver, but want to run my tests through the software driver first (and possibly use the software driver to validate results). I have set the following in my GENERIC conf file: device crypto device enc options IPSEC I have

[FreeBSD 6.2] _IOWR macro

Hi All, I am using the _IOWR macro in a piece of code. Although my structure gets copied to the kernel ok (the states etc are preserved), if I write back to that structure, the changes are not seen in user space. Is there a known bug with this macro for 6.2 and is it fixed in a later release?

Openssl port upgrade (FreeBSD 6.2)

Hi All, I ran the openssl updgrade (to OpenSSL 0.9.8d), but it seems the original openssl libs are still being used for SSH session creation and other system crypto functionality. What are the final steps needed to allow all user space programs to use the upgraded OpenSSL? Is there a good guide

disable use of opencrypto for ssh login

Hi All, I am using FreeBSD 6.2. What are the steps I would need to perform in order to for opencrypto not to be used during SSH session setup (even if there is a working crypto module available underneath it)? Regards, Brendan ___