Date: Tue, 26 Aug 2014 06:23:12 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Baldwin <jhb@freebsd.org> Cc: current@freebsd.org, "Michael W. Lucas" <mwlucas@michaelwlucas.com> Subject: Re: gbde destroy doesn't match man page? Message-ID: <98222.1409034192@critter.freebsd.dk> In-Reply-To: <2945485.ZemF81RAkB@ralph.baldwin.cx> References: <20140820215522.GA92455@bewilderbeast.blackhelicopters.org> <23149.1408789002@critter.freebsd.dk> <2945485.ZemF81RAkB@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <2945485.ZemF81RAkB@ralph.baldwin.cx>, John Baldwin writes: >On Saturday, August 23, 2014 10:16:42 AM Poul-Henning Kamp wrote: >> -------- >> In message <20140820215522.GA92455@bewilderbeast.blackhelicopters.org>, >> "Michae >> l W. Lucas" writes: >> >Playing with GBDE for my FreeBSD disk book, on: >> > >> ># uname -a >> >FreeBSD storm 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r269010: Wed Jul 23 >> >11:13:17 EDT 2014 mwlucas@storm:/usr/obj/usr/src/sys/GENERIC amd64 >> > >> >According to the man page, I should be able to destroy all copies of >> >the key with gbde destroy <device> -n -1. It's in the examples. When I >> >> >try it I get: >> I think that is an oversight in the code. > >Can you expand on this? I.e. what should the code do if it is fixed? Hmm, now that I think about it, -n doesn't make sense because any one of the four keys can open the volume as needed to blow away the masterkey. The manual page should just be fixed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98222.1409034192>