From: Eric Wong <e@80x24.org> To: meta@public-inbox.org Subject: [PATCH 3/4] lei q: disallow "\n" in argv[] elements Date: Wed, 10 Nov 2021 10:28:37 +0000 [thread overview] Message-ID: <20211110102837.41770-1-e@80x24.org> (raw) In-Reply-To: <20211110102511.40960-1-e@80x24.org> I don't expect this to be hit in real-world use via normal interactive shells. However, somebody could accidentally add "\n" in languages (e.g. Perl, C) where it's easy to pass "\n" in argv[]. --- lib/PublicInbox/LeiQuery.pm | 1 + t/lei.t | 3 +++ 2 files changed, 4 insertions(+) diff --git a/lib/PublicInbox/LeiQuery.pm b/lib/PublicInbox/LeiQuery.pm index 352ee60131aa..51ee3d9c83e4 100644 --- a/lib/PublicInbox/LeiQuery.pm +++ b/lib/PublicInbox/LeiQuery.pm @@ -141,6 +141,7 @@ no query allowed on command-line with --stdin PublicInbox::InputPipe::consume($self->{0}, \&qstr_add, $self); return; } + chomp(@argv) and $self->qerr("# trailing `\\n' removed"); $mset_opt{q_raw} = [ @argv ]; # copy $mset_opt{qstr} = $self->{lse}->query_argv_to_string($self->{lse}->git, \@argv); diff --git a/t/lei.t b/t/lei.t index f7de1b711a83..b10c9b59c72b 100644 --- a/t/lei.t +++ b/t/lei.t @@ -143,6 +143,9 @@ my $test_fail = sub { lei('-C', '/dev/null', 'q', 'whatever'); is($? >> 8, 1, 'chdir at beginning fails to /dev/null'); + lei_ok('q', "foo\n"); + like($lei_err, qr/trailing `\\n' removed/s, "noted `\\n' removal"); + for my $lk (qw(ei inbox)) { my $d = "$home/newline\n$lk"; mkdir $d;
next prev parent reply other threads:[~2021-11-10 10:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-10 10:25 [PATCH 0/4] "lei q" rawstr fallout + fixes Eric Wong 2021-11-10 10:28 ` Eric Wong [this message] 2021-11-10 10:28 ` [PATCH 4/4] lei q: make HTTP(S) query strings even less ugly Eric Wong 2021-11-10 10:28 ` [PATCH 1/4] ipc: note failing sub name Eric Wong 2021-11-10 10:28 ` [PATCH 2/4] lei up: infer rawstr from old searches via trailing "\n" Eric Wong
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 List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20211110102837.41770-1-e@80x24.org \ --to=e@80x24.org \ --cc=meta@public-inbox.org \ --subject='Re: [PATCH 3/4] lei q: disallow "\n" in argv[] elements' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).