From owner-freebsd-hackers@freebsd.org Tue Sep 8 22:23:02 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63E1EA00132 for ; Tue, 8 Sep 2015 22:23:02 +0000 (UTC) (envelope-from analysiser@gmail.com) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30ABC12F9 for ; Tue, 8 Sep 2015 22:23:02 +0000 (UTC) (envelope-from analysiser@gmail.com) Received: by padhk3 with SMTP id hk3so50831930pad.3 for ; Tue, 08 Sep 2015 15:23:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=yXy2w4UVUPyqEiYn3GgYWFlMEcwjgpPh0Ku6UTmFDGY=; b=pmviE51ii3N+CQJrW6/a1i2qyJuLrPeTm/GhnZF9n30beMV6bVL+4WYBKKbGHESuMl b6KC/BMjj0VVlbiERAFZEijWo8QDZNKG/P3c1Q3hROKfMm/kmrsnjMuS2GblJwmgBcap KEnV8MvpK04lICBbiZqh44tnTUAuAGIMVblZwQ901t27s/0DXCgb0ZdlWjqudjXXBo45 B43YKwAihLEvSH2XorNX4fH14Aq7GrfJVDE5prlCDhsuCl1THQhAUMYW/po/4jYr8asF WuwU2dtkX3Wgwu+rJTjzy8OBqKAimdJSCEF+IkWkjwOggLfm5fuTtjkE7wCBVyzadWS3 LGGA== X-Received: by 10.68.184.197 with SMTP id ew5mr63254774pbc.145.1441750981391; Tue, 08 Sep 2015 15:23:01 -0700 (PDT) Received: from a45e60cc77bb.amazon.com (54-240-196-186.amazon.com. [54.240.196.186]) by smtp.gmail.com with ESMTPSA id ft14sm4616131pdb.13.2015.09.08.15.23.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Sep 2015 15:23:00 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Passphraseless Disk Encryption Options? From: Analysiser In-Reply-To: Date: Tue, 8 Sep 2015 15:22:59 -0700 Cc: Xin LI , Hackers freeBSD Message-Id: <74385D4D-48C7-4B5B-BF94-B99806C667EE@gmail.com> References: <8B7FEE2E-500E-49CF-AC5E-A2FA3054B152@gmail.com> <55EF4B65.8030905@delphij.net> To: Igor Mozolevsky X-Mailer: Apple Mail (2.2104) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2015 22:23:02 -0000 Hi Igor, I=E2=80=99m trying to protect my startup disk=E2=80=99s data from being = tampered with by someone who has physically access to the disk. He might = put it on some other machine, add some malicious code or check the logs = stored in /var, and then put it back my machine, when the machine is = stayed in some public untrusted environment. When I regain the machine = from a public untrusted environment and boot the disk, some malicious = code might running and try to contaminate my own network or other = machines, or monitor my activities with the machine.=20 I hope I explained clearer this time :) Xiao > On Sep 8, 2015, at 3:09 PM, Igor Mozolevsky = wrote: >=20 >=20 >=20 > On 8 September 2015 at 22:50, Analysiser > wrote: > Hi all, >=20 > Thank you so much for all the insights here! I think I is my bad not = to clarify the situation very well but still I found a lot of things I = could try from the replies. In my case I could not do remote passphrase = and and USB boot and/or USB hold key/passphrase since the device might = not always have internet access and no ports (internally or externally = are exposed). >=20 > I think your suggestions in separating the root filesystem and user = space applications and data and perform encryption only on user portion = is a more reasonable practice given the time scale on the project I=E2=80=99= m working on. Thanks again! >=20 > I still have some more detailed questions I=E2=80=99m seeking for an = answer related to the full startup disk encryption: >=20 >=20 > >=20 > I think you're worrying about the problem from the wrong end- what is = it that you're attempting to protect, I'm still unsure of that?.. >=20 >=20 > --=20 > Igor M.=20