From owner-freebsd-arch@freebsd.org Tue May 7 20:46:35 2019 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0199915938B4 for ; Tue, 7 May 2019 20:46:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 57D6A74610 for ; Tue, 7 May 2019 20:46:34 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1B74E15938B1; Tue, 7 May 2019 20:46:34 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB9E215938AF for ; Tue, 7 May 2019 20:46:33 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it1-f179.google.com (mail-it1-f179.google.com [209.85.166.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8837B7460D for ; Tue, 7 May 2019 20:46:33 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it1-f179.google.com with SMTP id u186so356437ith.0 for ; Tue, 07 May 2019 13:46:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=CUukZ7Xxg5S3C28o+HL9LGu0MaR8u8u4mIEfWSG1SAw=; b=nO747Y1daMelxFaANg5OouE8Dm00OYFRltCqdFirT+inCb7VsiprJBRFD6y7OMbtNK FiGXzgLjfaNPhmh3ruHZPRaaU7lBp1TFGjY61i+GPG+FbMUI63M+TMG5r8nfREk6cVFw bpcl33f6QAZoePLKe/8c/BFd16tVp/1VmZ9cOAIjfPf9Za1XRU22Gvopk6WJ8wm8O1r9 KX/RiqS+d9ZFL4EtE3AUIxVNSGD/r4OK+2FzXpHMvvQcu4GFiWbXqIoLvvvFjMacPc4h 5Xcry28YxXq7cZFLUnlkj+NsNDdsfYXQ6aU1ytb/K+inw4Cqz8yi7nbecmHYkQ3HLHij 7wJQ== X-Gm-Message-State: APjAAAVLl9gFRuvoHv6jNu8wPmQqup/WhrhJuM3VeEEaJfLEwuLQnphK 4HSqN1c8D7T9Gj46D6/2wDlFAO0F X-Google-Smtp-Source: APXvYqwkOCQYjkL74zD6zzrRmTUCSg4AST0Bq+1GNLN+rEzlHPELGIcjYDucf0SgfSKqncgZaV3ApQ== X-Received: by 2002:a24:2b50:: with SMTP id h77mr330381ita.63.1557261986878; Tue, 07 May 2019 13:46:26 -0700 (PDT) Received: from mail-it1-f169.google.com (mail-it1-f169.google.com. [209.85.166.169]) by smtp.gmail.com with ESMTPSA id j8sm79045itk.0.2019.05.07.13.46.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 May 2019 13:46:26 -0700 (PDT) Received: by mail-it1-f169.google.com with SMTP id q132so423380itc.5 for ; Tue, 07 May 2019 13:46:26 -0700 (PDT) X-Received: by 2002:a05:660c:130f:: with SMTP id f15mr321584itb.166.1557261986390; Tue, 07 May 2019 13:46:26 -0700 (PDT) MIME-Version: 1.0 References: <41ed59c2-f06c-710b-0e77-3b78add85ca3@FreeBSD.org> In-Reply-To: Reply-To: cem@freebsd.org From: Conrad Meyer Date: Tue, 7 May 2019 13:46:15 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Deprecating crypto algorithms in the kernel To: Warner Losh Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 8837B7460D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 May 2019 20:46:35 -0000 On Tue, May 7, 2019 at 1:37 PM Warner Losh wrote: > This freaked me out when I saw it, since I have GELI volumes going back a > about a decade. However, checking into it showed no cause for concern. > > The default was changed in this commit: > > pjd | Thu Sep 23 11:58:36 2010 +0000 | r213070 > Add support for AES-XTS. This will be the default now. > > All my GELI volumes are AES-XTS (though some pre-date this change, I may > have converted somehow along the way). Camilla support was added in 2007, > and that's not on the chopping block, but wasn't made the default. > > So all GELI volumes created in the last 8 years aren't affected (plus or > minus for time to get into a release) and even older ones likely are still > supported. So I expect the practical impact of this to be minimal. Prior to AES-XTS, the default was "aes" (some non-XTS AES mode), since geli was initially committed in 2005. So all GELI volumes created, ever, that did not explicitly override the default encryption algorithm with a weak cipher should be using some AES-based encryption mode. None of those are on the chopping block, or even trending towards deprecation. Best, Conrad