From owner-freebsd-questions@FreeBSD.ORG Fri May 15 16:19:04 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37E2A106566C for ; Fri, 15 May 2009 16:19:04 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id EFBEE8FC08 for ; Fri, 15 May 2009 16:19:03 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (54.158.192-77.rev.gaoland.net [77.192.158.54]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 80B5B63352C; Fri, 15 May 2009 18:19:02 +0200 (CEST) Received: from baby-jane.lamaiziere.net (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id E1CA4B873; Fri, 15 May 2009 18:19:06 +0200 (CEST) Date: Fri, 15 May 2009 18:19:05 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: Brendan Kennedy Message-ID: <20090515181905.5b469715@baby-jane.lamaiziere.net> In-Reply-To: References: Organization: /dave/nulle X-Mailer: Claws Mail 3.7.1 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.1 opencrypto --> kern.cryptodevallowsoft X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 16:19:04 -0000 Le Tue, 12 May 2009 19:14:38 +0100, Brendan Kennedy : > Hi All, Hello, > FreeBSD_26# sysctl -a | grep crypto > kern.cryptodevallowsoft: 1 > > However, when I try a test, I get the following: > > FreeBSD_26# /usr/src/tools/tools/crypto/cryptotest -va 3des > cipher 3des keylen 24 > CIOCGSESSION: Invalid argument > FreeBSD_26# /usr/src/tools/tools/crypto/cryptotest -va des > cipher des keylen 8 > CIOCGSESSION: Invalid argument > > It seems the software crypto device is not available. Do I need to do > any other steps to enable it? Is there another config option that > makes sure it is build as part of Opencrypto framework? Do I need to > build some other software driver instead? Cryptodev fails because it checks that the requested crypto driver provides hardware crypto. function "checkforsoftware" in cryptodev.c And it does not take care about the sysctl kern.cryptodevallowsoft. Looks like a bug and not a feature. OpenBSD's cryptodev seems to take care about the sysctl and i think you can use the cryptosoft driver with it. Regards.