Date: Tue, 7 May 2019 13:46:15 -0700 From: Conrad Meyer <cem@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: Deprecating crypto algorithms in the kernel Message-ID: <CAG6CVpUAGxt-3qNjMJsw_1H%2BVfO1P-1sEaXQ33s15LaVSuuF=g@mail.gmail.com> In-Reply-To: <CANCZdfoYzE3b7ZPsxeFWyPyZeTbaMer=O7aHFGKoRGAEXzLcpQ@mail.gmail.com> References: <41ed59c2-f06c-710b-0e77-3b78add85ca3@FreeBSD.org> <CANCZdfoYzE3b7ZPsxeFWyPyZeTbaMer=O7aHFGKoRGAEXzLcpQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 7, 2019 at 1:37 PM Warner Losh <imp@bsdimp.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpUAGxt-3qNjMJsw_1H%2BVfO1P-1sEaXQ33s15LaVSuuF=g>