From owner-freebsd-current@freebsd.org Fri Mar 20 21:03:16 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8CD28273043 for ; Fri, 20 Mar 2020 21:03:16 +0000 (UTC) (envelope-from SRS0=mxbq=5F=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48kbpW46D3z4R6y for ; Fri, 20 Mar 2020 21:03:15 +0000 (UTC) (envelope-from SRS0=mxbq=5F=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 16BEB28422; Fri, 20 Mar 2020 22:03:13 +0100 (CET) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 135F428417; Fri, 20 Mar 2020 22:03:12 +0100 (CET) Subject: Re: TLS certificates for NFS-over-TLS floating client To: Rick Macklem , "freebsd-current@FreeBSD.org" References: <20200319191605.GJ4213@funkthat.com> <20200320192923.GK4213@funkthat.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5c77aeed-568f-b85c-286e-8b7f3207c952@quip.cz> Date: Fri, 20 Mar 2020 22:03:12 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <20200320192923.GK4213@funkthat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 48kbpW46D3z4R6y X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=mxbq=5F=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=mxbq=5F=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [4.03 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.83)[ip: (0.30), ipnet: 94.124.104.0/21(0.15), asn: 42000(3.63), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.998,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(1.00)[1.000,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=mxbq=5F=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=mxbq=5F=quip.cz=000.fbsd@elsa.codelab.cz]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 21:03:16 -0000 John-Mark Gurney wrote on 2020/03/20 20:29: > Rick Macklem wrote this message on Thu, Mar 19, 2020 at 23:41 +0000: [...] >>> Without a problem statement or what you're trying to accomplish, it's >>> hard to say if it is. >> The problem I was/am trying to solve was a way for NFS clients without a >> fixed IP/DNS name could have a certificate to allow access to the NFS server. >> As suggested by others, having a site local CA created by the NFS admin. seemed > > Yes, I totally agree w/ this as the best solution. It also allows > private hostnames to be used w/o leaking outside the org.. > > It'd be nice to have better tooling around the CA though. I still > haven't found any good tools that make a CA simple to use for small > installs... (and by simple, I mean single init command, and single > command to issue a cert or generate a key/cert pair, all of them are > like, make all thesse directories, edit these files, and run these > comlicated commands) security/easy-rsa is very close to this. # easyrsa init-pki # easyrsa build-ca # easyrsa build-server-full # easyrsa build-client-full # easyrsa build-client-full # easyrsa build-client-full or # easyrsa build-client-full nopass And usually # easyrsa gen-dh With "build-ca" you will create key and certificate for you private CA With "build-server-full" you will create key and certificate for your server With "build-client-full" you will create key and certificate for clients It also supports "revoke" and "gen-crl" to revoke compromised certificate and update CRL. Yes, it could be made a bit simpler and run init-pki in the background if build-ca is run for the first time so you can save one step. I don't say easy-rsa is the best choice. I am able to use full openssl commands or write my own tools / scripts around it I choose easy-rsa on machines where somebody else needs to work with certs. [...] Kind regards Miroslav Lachman