From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30032 invoked from network); 5 Jun 2020 01:56:37 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 5 Jun 2020 01:56:37 -0000 Received: (qmail 3627 invoked by alias); 5 Jun 2020 01:56:30 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24903 Received: (qmail 9005 invoked by uid 1010); 5 Jun 2020 01:56:30 -0000 X-Qmail-Scanner-Diagnostics: from wout5-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25828. spamassassin: 3.4.4. Clear:RC:0(64.147.123.21):SA:0(-2.6/5.0):. Processed in 0.716166 secs); 05 Jun 2020 01:56:30 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudegvddggeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfgjfhfogggtgfesthhqtddtredtjeenucfhrhhomhepffgrnhhi vghlucfuhhgrhhgrfhcuoegurdhssegurghnihgvlhdrshhhrghhrghfrdhnrghmvgeqne cuggftrfgrthhtvghrnhephfdtteefheevuedthedutdeifeegteettdejtdffheduieei jeelteetkeduteehnecukfhppeejledrudejiedrfeelrdeileenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurdhssegurghnihgvlhdrshhh rghhrghfrdhnrghmvg X-ME-Proxy: Date: Fri, 5 Jun 2020 01:55:51 +0000 From: Daniel Shahaf To: Oliver Kiddle Cc: Paul Ruane , zsh-users@zsh.org Subject: Re: Cryptsetup completion Message-ID: <20200605015551.341c5622@tarpaulin.shahaf.local2> In-Reply-To: <56544-1591271448.415496@8V8i.speh.Bt-A> References: <20200603005555.304cca04@tarpaulin.shahaf.local2> <56544-1591271448.415496@8V8i.speh.Bt-A> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oliver Kiddle wrote on Thu, 04 Jun 2020 13:50 +0200: > Paul Ruane wrote: > > The new patch--in correct format :)--is here: =20 >=20 > Thanks >=20 > > +++ b/Completion/Linux/Type/_crypto_ciphers =20 >=20 > These are just the cyphers handled by the Linux kernel, right? Is this > naming perhaps too generic? _linux_ciphers perhaps? +1 > We wouldn't want > them to be used in other cases where something else such as openssl > ciphers are wanted. Does anyone know for what other commands these might > be relevant? If there are none, then I would contradict Daniel about > factoring them out. For the record, my rationale was simply that a function that completes "'cipher' elements of /proc/crypto" seemed like it would be inherently reusable. Nevertheless, I'm not aware of a specific place where it would be reused, and I wouldn't mind one way or the other whether it should be factored out or not. Separate issue: cryptsetup(8) says: . --cipher, -c =E2=80=A6 The current default in the distributed sources is "aes-cbc-essiv:sha256" for plain dm-crypt and "aes-xts-plain64" for LUKS. =E2=80=A6 . So it seems _linux_ciphers should not be used directly as _the_ completion function for arguments to the -c option. Cheers, Daniel