From nobody Tue Feb 01 19:06:06 2022 X-Original-To: freebsd-amd64@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 0B058197BC44 for ; Tue, 1 Feb 2022 19:06:23 +0000 (UTC) (envelope-from georg@bege.email) Received: from mail.unix.io (mail.unix.io [IPv6:2001:470:1f09:68::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JpDtQ0vQBz4fwt for ; Tue, 1 Feb 2022 19:06:21 +0000 (UTC) (envelope-from georg@bege.email) Received: from mail.unix.io (localhost [127.0.0.1]) by mail.unix.io (Postfix) with ESMTP id 570CC39F9F for ; Tue, 1 Feb 2022 19:06:11 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bege.email; h=message-id :date:mime-version:to:from:subject:content-type :content-transfer-encoding; s=mail141202; bh=lwfTjtlwEcYPoXb5LNc 6pX9IigI=; b=D0CMypfQONl21zBvmpCNUJOZW1wgrRSivtnIWczIpLU183zub/f 1qRWERbF2jmTJqobAAlbJvo1O0Y2Vzvx/QOrlOAV5IodAT/mYVrnOwhV0yJLmmk7 5g8C0iufgyQvxPNzhwX6NcRQH456Jvqs6pUs50TGE5k93Wqm2skjV4+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bege.email; h=message-id :date:mime-version:to:from:subject:content-type :content-transfer-encoding; q=dns; s=mail141202; b=GDuU+7oLoGumu JtrSrnlGVecc6VL6YmogEXfYhVX1V2vCkku1dpw1h5ihwa0apzeNgQczFMJqRZNY 78FqQ+y4+t13Qna3dHhpBUAlC8+q/cdPoA5ndS2q1WrjRZ4xmaX1fojyrArKKbEt Q7ebIQUurSFH4bcqOF0m7gezcJ4+40= Received: from [192.168.171.2] (p5dcee799.dip0.t-ipconnect.de [93.206.231.153]) (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 did not present a certificate) by mail.unix.io (Postfix) with ESMTPSA id AC80C39F1F for ; Tue, 1 Feb 2022 19:06:10 +0000 (GMT) Message-ID: <54f1aaaa-d4ed-1273-df9d-27cae3c1dc5f@bege.email> Date: Tue, 1 Feb 2022 20:06:06 +0100 List-Id: Porting FreeBSD to the AMD64 platform List-Archive: https://lists.freebsd.org/archives/freebsd-amd64 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-amd64@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Content-Language: en-US To: freebsd-amd64@FreeBSD.org From: Georg Bege Subject: geli keyfile arguments / gpt partitions Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4JpDtQ0vQBz4fwt X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bege.email header.s=mail141202 header.b=D0CMypfQ; dmarc=none; spf=pass (mx1.freebsd.org: domain of georg@bege.email designates 2001:470:1f09:68::2 as permitted sender) smtp.mailfrom=georg@bege.email X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bege.email:s=mail141202]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-amd64@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[bege.email]; DKIM_TRACE(0.00)[bege.email:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-amd64]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[93.206.231.153:received] X-ThisMailContainsUnwantedMimeParts: N Hello mailing list, Im trying to realize a specific encrypted setup on my FreeBSD machine at home. For now I've a raidz2 pool, which did contain root - however it doesnt boot anylonger. I have a dedicated SATA disk with UEFI boot code and /boot data, so this works and I can bootup. What I wanted to do now is now encrypt the devices of the pool, which should work in general because I can boot the kernel and thus the kernel should be able to decrypt the required disk devices. My issue is now that if I find anything on google etc, all examples want me to put the keyfile on /boot and then provide it as an argument like: geli__keyfile0_name="/boot/encrypted.key" This is something I dont want to do, instead I'd prefer that I put the keyfile data on a single gpt partition of an usb stick of my choice - I can reach this device whenever I boot up... however it seems I can not provide a /dev/... device just like this as an argument. I dont even know if the kernel is able to read raw data from a gpt partition... but well why not? It should be possible? Has anyone a clue how to archive this or which arguments I need to provide? regards, Georg