From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from seg-node-chi-01.trustwave.com (seg-node-chi-01.trustwave.com [204.13.200.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 5 Jul 2016 20:08:39 +0200 (CEST) From: Tapas Sarangi Date: Tue, 5 Jul 2016 17:53:33 +0000 Message-ID: Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_D3A15E4B24A2tsarangitrustwavecom_" MIME-Version: 1.0 Subject: [dm-crypt] dm-crypt.ko external kernel module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "dm-crypt@saout.de" --_000_D3A15E4B24A2tsarangitrustwavecom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Is there a way to build external kernel module dm-crypt.ko that is not incl= uded by default in the kernel configs ? Is there any instruction on where t= o get the source tarball etc... ? Thanks for any help. -Tapas ________________________________ This transmission may contain information that is privileged, confidential,= and/or exempt from disclosure under applicable law. If you are not the int= ended recipient, you are hereby notified that any disclosure, copying, dist= ribution, or use of the information contained herein (including any relianc= e thereon) is strictly prohibited. If you received this transmission in err= or, please immediately contact the sender and destroy the material in its e= ntirety, whether in electronic or hard copy format. --_000_D3A15E4B24A2tsarangitrustwavecom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <0F4816CC523018438660B7C767570FA6@namprd07.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Hi,

Is there a way to build external kernel module dm-crypt.ko that is not= included by default in the kernel configs ? Is there any instruction on wh= ere to get the source tarball etc… ?

Thanks for any help.
-Tapas





This transmission may contain information that is privileged, confidential,= and/or exempt from disclosure under applicable law. If you are not the int= ended recipient, you are hereby notified that any disclosure, copying, dist= ribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. = If you received this transmission in error, please immediately contact the = sender and destroy the material in its entirety, whether in electronic or h= ard copy format.
 --_000_D3A15E4B24A2tsarangitrustwavecom_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 5 Jul 2016 23:04:02 +0200 (CEST) Received: by mail-wm0-x243.google.com with SMTP id c82so31348360wme.3 for ; Tue, 05 Jul 2016 14:04:02 -0700 (PDT) References: From: Milan Broz Message-ID: <40d55a0f-b675-f947-c205-78d1bbbcec86@gmail.com> Date: Tue, 5 Jul 2016 23:03:59 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] dm-crypt.ko external kernel module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tapas Sarangi Cc: dm-crypt On 07/05/2016 07:53 PM, Tapas Sarangi wrote: > Is there a way to build external kernel module dm-crypt.ko that is > not included by default in the kernel configs ? Is there any > instruction on where to get the source tarball etc=85 ? While is possible (in some configurations) to build kernel module separately with the help of simple makefile and some kernel headers, it is not the way= dmcrypt should be used. The reason is that code is directly dependent on internal kernel structures and also requires some other config options (like device-mapper infrastruct= ure, kernel crypto API and particular kernel block layer settings). The dmcrypt is included in the mainline kernel, there is no need for separa= te source tarball, just use mainline kernel source (drivers/md/dmcrypt.c is the module core). Your distro must have these sources available if they are distributing bina= ries (it is GPL code), so you can always compile modules from it. Milan From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from seg-node-elk-03.trustwave.com (seg-node-elk-03.trustwave.com [204.13.202.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 5 Jul 2016 23:24:44 +0200 (CEST) From: Tapas Sarangi Date: Tue, 5 Jul 2016 21:07:27 +0000 Message-ID: References: <40d55a0f-b675-f947-c205-78d1bbbcec86@gmail.com> In-Reply-To: <40d55a0f-b675-f947-c205-78d1bbbcec86@gmail.com> Content-Language: en-US Content-Type: text/plain; charset="Windows-1252" Content-ID: <7CE9935C97B59940A85279CB87736D74@namprd07.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dm-crypt] dm-crypt.ko external kernel module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milan Broz Cc: dm-crypt Hi Milan, Thanks for your response. The distro I am using does not have CONFIG_DM_CRYPT enabled. I am aware of the Kernel compilation methods for standalone external modules and looking at your comment, it seems to be the only way for me now. Yes, I am also aware that DM_CRYPT will be build again a specific kernel in order to be usable. Thanks again. -Tapas On 7/5/16, 4:03 PM, "Milan Broz" wrote: >On 07/05/2016 07:53 PM, Tapas Sarangi wrote: >> Is there a way to build external kernel module dm-crypt.ko that is >> not included by default in the kernel configs ? Is there any >> instruction on where to get the source tarball etc=8A ? > >While is possible (in some configurations) to build kernel module >separately >with the help of simple makefile and some kernel headers, it is not the >way dmcrypt >should be used. > >The reason is that code is directly dependent on internal kernel >structures >and also requires some other config options (like device-mapper >infrastructure, >kernel crypto API and particular kernel block layer settings). > >The dmcrypt is included in the mainline kernel, there is no need for >separate >source tarball, just use mainline kernel source (drivers/md/dmcrypt.c is >the module core). > >Your distro must have these sources available if they are distributing >binaries >(it is GPL code), so you can always compile modules from it. > >Milan ________________________________ This transmission may contain information that is privileged, confidential,= and/or exempt from disclosure under applicable law. If you are not the int= ended recipient, you are hereby notified that any disclosure, copying, dist= ribution, or use of the information contained herein (including any relianc= e thereon) is strictly prohibited. If you received this transmission in err= or, please immediately contact the sender and destroy the material in its e= ntirety, whether in electronic or hard copy format.