From owner-freebsd-hackers@FreeBSD.ORG  Wed Feb  1 17:51:33 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 670C0106566B
	for <freebsd-hackers@freebsd.org>; Wed,  1 Feb 2012 17:51:33 +0000 (UTC)
	(envelope-from PMahan@adaranet.com)
Received: from barracuda.adaranet.com (smtp.adaranet.com [72.5.229.2])
	by mx1.freebsd.org (Postfix) with ESMTP id 4AD758FC08
	for <freebsd-hackers@freebsd.org>; Wed,  1 Feb 2012 17:51:33 +0000 (UTC)
X-ASG-Debug-ID: 1328117732-586eaf4c0001-P5m3U7
Received: from SJ-EXCH-1.adaranet.com ([10.10.1.29]) by barracuda.adaranet.com
	with ESMTP id tIiwMRvAJLoAUAjz; Wed, 01 Feb 2012 09:35:32 -0800 (PST)
X-Barracuda-Envelope-From: PMahan@adaranet.com
Received: from SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523]) by
	SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523%14]) with mapi;
	Wed, 1 Feb 2012 09:35:32 -0800
From: Patrick Mahan <PMahan@adaranet.com>
X-Barracuda-BBL-IP: fe80::7042:d8c2:5973:c523
X-Barracuda-RBL-IP: fe80::7042:d8c2:5973:c523
To: aram baghomian <aram_baghomian@hotmail.com>, "freebsd-hackers@freebsd.org"
	<freebsd-hackers@freebsd.org>
Date: Wed, 1 Feb 2012 09:35:40 -0800
X-ASG-Orig-Subj: RE: crypto module
Thread-Topic: crypto module
Thread-Index: Aczg8qZrXLMYTKMJTyazOhuetNx3mAAFMtaw
Message-ID: <32AB5C9615CC494997D9ABB1DB12783C02D685B803@SJ-EXCH-1.adaranet.com>
References: <SNT140-W4888C9985D7F72B14B339AE7730@phx.gbl>
In-Reply-To: <SNT140-W4888C9985D7F72B14B339AE7730@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: UNKNOWN[10.10.1.29]
X-Barracuda-Start-Time: 1328117732
X-Barracuda-URL: http://172.16.10.203:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at adaranet.com
Cc: 
Subject: RE: crypto module
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2012 17:51:33 -0000

>-----Original Message-----
>From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-
>hackers@freebsd.org] On Behalf Of aram baghomian
>Sent: Wednesday, February 01, 2012 6:54 AM
>To: freebsd-hackers@freebsd.org
>Subject: crypto module
>
>
>
>
>
>Hi,
>
>I want to know which kernel modules keep the information about implemented
>algorithms
>in crypto.ko.
>for example in linux there is xfrm_algo modules that keep the information
>about
>these algorithms.
>
>

No, the algorithms are access via statically allocated structures
defined in sys/opencrypto/xform.c

Not that there couldn't be one written, but the xforms would need
to be dynamically done and have each crypto algorithm register
themselves.

Patrick
----------------------------------------------------
Patrick Mahan
Lead Technical Kernel Engineer
Adara Networks
Disclaimer: The opinions expressed here are solely the responsibility of th=
e author and are not to be
construed as an official opinion of Adara Networks.