From owner-freebsd-security@FreeBSD.ORG Tue Feb 24 13:09:46 2015 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 18F7C92D for ; Tue, 24 Feb 2015 13:09:46 +0000 (UTC) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (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 A7E76679 for ; Tue, 24 Feb 2015 13:09:45 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id ex7so4726061wid.0 for ; Tue, 24 Feb 2015 05:09:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=HMqQXi8lr8w9crmf9LPVXPCi0beMMj17Yf4z1E65O9o=; b=ovCYmFDn0gZ86WTDOJ2i/L27raLzJU6LDn+cn6yhBe+RNBco4IGFXItIZvA5qY5xbB 4MdGTwLaOJw3xgO1K15lJbq0GrUl1tbMCpjJRp/JYQtkTaVeD5dRkRVO+KBD0wtkSueZ wKbz8hUxCBTw++gTWFgu81EoSF9h2PRWqQT8I5xjhM4c1uD1tHNDI11dexk4ImKAE1jo yLbMfPhSCp5OkWdeyTZ/9WvvBc2mgqU+4OHjPlMbN6KcP0Vgo2M1SZdyP4zK9cLgKhAE OXRrB3i8M62TtaBXWu0VWSCTA2P3O5l80ixofL9VYj3MuFVG2JbEDkv+vGIquRacrgQ2 ax9w== X-Received: by 10.180.187.97 with SMTP id fr1mr15529392wic.1.1424783383927; Tue, 24 Feb 2015 05:09:43 -0800 (PST) Received: from gumby.homeunix.com (4e5670d9.skybroadband.com. [78.86.112.217]) by mx.google.com with ESMTPSA id eb10sm20493797wib.13.2015.02.24.05.09.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 05:09:43 -0800 (PST) Date: Tue, 24 Feb 2015 13:09:41 +0000 From: RW To: freebsd-security@freebsd.org Subject: Re: [Cryptography] trojans in the firmware Message-ID: <20150224130941.5b0998bc@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 13:09:46 -0000 On Mon, 23 Feb 2015 12:45:02 +1300 Peter Gutmann wrote: > Henry Baker writes: > > >BTW, what's the point of AES encryption on this pre-p0wned device? > >More security theatre? > > Almost. Its sole use is for very fast "drive erasure", i.e. you > change the key and the data on it becomes inaccessible. Have a look > at this presentation: > > http://www.snia.org/sites/default/education/tutorials/2012/spring/security/MichaelWillett_Implementing%20Stored-Data_Encryption_2.pdf > > which describes what Samsung (and others) are doing, in particular > slide 18. The decryption key (DEK) is stored in the drive, and is > unlocked using a password (and "authentication key", AK). So to > decrypt the drive you extract the encrypted DEK, brute-force the > password (AK), and you're in. This is how practically all disk encryption works. Whether or not it's secure depends on the strength of the password + key-file.