From nobody Fri Feb 10 11:25:03 2023 X-Original-To: freebsd-security@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PCrxm40q1z3pptW for ; Fri, 10 Feb 2023 11:25:16 +0000 (UTC) (envelope-from oshogbo.vx@gmail.com) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PCrxm2LJWz3spg; Fri, 10 Feb 2023 11:25:16 +0000 (UTC) (envelope-from oshogbo.vx@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wr1-f41.google.com with SMTP id bu23so4733164wrb.8; Fri, 10 Feb 2023 03:25:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qYS1/JW5r17Dz8YkfgsaocjpyWo7Vwfm0oY56DroBZ8=; b=dWvmWw8BrXevONlSxXY+u+BU1ekyM8JOn5tiIIGhS06mCr7B9v/pY308t2/acH9+Sx 4bwcPjw/lHxZJ7kcLGD0in0+zK1ivpai95VDkiEsn3fCdra/0FPDczlWzKB+8Mbl2XZn edw0LORJB/3Z1t8eNJPzBe6TYMRUw9E4DxuVLdvU89PEYBQynru345BsLUAV10uOiaIw nNj7nD9K/1KBTwsreOO6oVcyCLkfGpKQBbvKTkVG9wtM4BqueGZU+lc0m/wpWO5d4Aoi abLKUwAavriJQry6X5BrqZ65A0VkarH3b9v6tmHcZGPIp23qTzhDY+fWqYK0RlbVbQba b7rQ== X-Gm-Message-State: AO0yUKXPwTL4z6ZEqSjIHybJw12rsHRUfSZRjq9am2OcJvw6xcZWOfWk N4bgF6Ud6iWb30I3qiC9HseOFApoucCJI62+/Fkjw+ON6kzgWg== X-Google-Smtp-Source: AK7set+j3LRS8pE0B99inqkmNLdi24mQyc4UWYS6FzXD3cdMC0b1LwR7dY5K/mULTGuvZL8gpvNblX5TE4h9HiWRDLE= X-Received: by 2002:adf:df11:0:b0:2c4:8bd:60dc with SMTP id y17-20020adfdf11000000b002c408bd60dcmr183869wrl.634.1676028314757; Fri, 10 Feb 2023 03:25:14 -0800 (PST) List-Id: Security issues List-Archive: https://lists.freebsd.org/archives/freebsd-security List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org MIME-Version: 1.0 References: <20230208190833.1DF6F8824@freefall.freebsd.org> In-Reply-To: From: Mariusz Zaborski Date: Fri, 10 Feb 2023 12:25:03 +0100 Message-ID: Subject: Re: FreeBSD Security Advisory FreeBSD-SA-23:01.geli To: Mel Pilgrim Cc: freebsd-security@freebsd.org, FreeBSD Security Advisories Content-Type: multipart/alternative; boundary="00000000000055af1205f456c0c7" X-Rspamd-Queue-Id: 4PCrxm2LJWz3spg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000055af1205f456c0c7 Content-Type: text/plain; charset="UTF-8" To test decryption in dry mode (can be used on the decrypted device): echo -n | geli attach -C -p -k - dev If it succeeds you want to re-encrypt your devices. On Fri, 10 Feb 2023 at 02:48, Mel Pilgrim wrote: > On 2023-02-08 11:08, FreeBSD Security Advisories wrote: > > > ============================================================================= > > FreeBSD-SA-23:01.geli Security > Advisory > > The FreeBSD > Project > > > > Topic: GELI silently omits the keyfile if read from stdin > > How do I test my existing devices to see if the master key needs to be > encrypted? > > Does the solution change if the keyfiles don't require passwords? I use > GELI keyfiles without passwords for unattended reboots. > > --00000000000055af1205f456c0c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
To test decryption in dry mode (can be used on the decrypt= ed device):
echo -n | geli attach -C -p -k - dev

If it succeeds y= ou want to re-encrypt your devices.

On Fri, 10 Feb 2023 at 02:48, Mel Pilgri= m <li= st_freebsd@bluerosetech.com> wrote:
On 2023-02-08 11:08, FreeBSD Security Advisories= wrote:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
> FreeBSD-SA-23:01.geli=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0Security Advisory
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The Free= BSD Project
>
> Topic:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 GELI silently omits the keyfi= le if read from stdin

How do I test my existing devices to see if the master key needs to be
encrypted?

Does the solution change if the keyfiles don't require passwords?=C2=A0= I use
GELI keyfiles without passwords for unattended reboots.

--00000000000055af1205f456c0c7--