From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBoP3QqD11qY for ; Wed, 15 Aug 2012 17:44:05 +0200 (CEST) Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 15 Aug 2012 17:44:05 +0200 (CEST) Received: by eekc50 with SMTP id c50so528065eek.37 for ; Wed, 15 Aug 2012 08:44:05 -0700 (PDT) Message-ID: <502BC3C1.3020602@gmail.com> Date: Wed, 15 Aug 2012 17:44:01 +0200 From: Milan Broz MIME-Version: 1.0 References: <20120814225021.GA18290@tansi.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Secret data from stdin List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kent Yoder Cc: dm-crypt@saout.de On 08/15/2012 05:12 PM, Kent Yoder wrote: > Yep, I am out of date here. What do you think about a code change > that woudl print a big fat warning if non-ascii bytes are detected on > stdin? Not changing the behavior (we don't want to break people who > might be already doing this), but just a warning. No please. Anything what prints any information about passphrase to screen, log etc. is not acceptable, it provides info which should not be seen anywhere. I know that \n handling is problematic, but there is huge amount of scripts using this redirection. We cannot simply change it. (At least not for current CLI commands.) Milan