From owner-freebsd-bugs@FreeBSD.ORG Sun Jun 24 12:50:10 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BFEAA106567C for ; Sun, 24 Jun 2012 12:50:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AA5C78FC12 for ; Sun, 24 Jun 2012 12:50:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5OCoAc2017225 for ; Sun, 24 Jun 2012 12:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5OCoA8n017224; Sun, 24 Jun 2012 12:50:10 GMT (envelope-from gnats) Date: Sun, 24 Jun 2012 12:50:10 GMT Message-Id: <201206241250.q5OCoA8n017224@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Patrick Lamaiziere Cc: Subject: Re: kern/166508: [glxsb] AES 256 encryption does not work with glxsb driver X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Patrick Lamaiziere List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2012 12:50:10 -0000 The following reply was made to PR kern/166508; it has been noted by GNATS. From: Patrick Lamaiziere To: bug-followup@FreeBSD.org, todd@toddblum.org Cc: Subject: Re: kern/166508: [glxsb] AES 256 encryption does not work with glxsb driver Date: Sun, 24 Jun 2012 14:33:52 +0200 Hello, This is a known issue and a problem within the crypto(9) framework. In the crypto framework we can only specify the algorithm (here aes) to use but not the size of the key. As glxsb only does aes-128, it fails when the crypto framework opens a session on it if the key size if different than 128. There is a CAVEAT section in the manual page of glxsb(4) for this : CAVEAT The crypto(9) framework will fail to open the crypto session on the device if the AES key's length is != 128 bits. This prevents the use of the glxsb device driver with AES keys of length != 128 bits. To make this to work, it need some changes in crypto(9). Sorry. (we can close this PR I guess, as it will not be solved) Regards.