From: Milan Broz <gmazyland@gmail.com>
To: Kent Yoder <shpedoikal@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Secret data from stdin
Date: Wed, 15 Aug 2012 17:44:01 +0200 [thread overview]
Message-ID: <502BC3C1.3020602@gmail.com> (raw)
In-Reply-To: <CAM0nabGz9rNoScQMYywXN17sN56mEwtXejUD7LOhW4MwEB1Rww@mail.gmail.com>
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
next prev parent reply other threads:[~2012-08-15 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 22:19 [dm-crypt] Secret data from stdin Kent Yoder
2012-08-14 22:50 ` Arno Wagner
2012-08-15 15:12 ` Kent Yoder
2012-08-15 15:44 ` Milan Broz [this message]
2012-08-15 22:34 ` Arno Wagner
2012-08-15 22:38 ` Arno Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502BC3C1.3020602@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=shpedoikal@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.