From: Brian Norris <computersforpeace@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org, Jan Viktorin <viktorin@rehivetech.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] send-email: fix uninitialized var warning for $smtp_auth
Date: Fri, 18 Sep 2015 15:42:42 -0700 [thread overview]
Message-ID: <20150918224242.GA45466@google.com> (raw)
In-Reply-To: <20150918222524.GA22410@flurp.local>
On Fri, Sep 18, 2015 at 06:25:24PM -0400, Eric Sunshine wrote:
> On Fri, Sep 18, 2015 at 03:12:50PM -0700, Brian Norris wrote:
> > --- a/git-send-email.perl
> > +++ b/git-send-email.perl
> > @@ -1136,7 +1136,7 @@ sub smtp_auth_maybe {
> >
> > # Check mechanism naming as defined in:
> > # https://tools.ietf.org/html/rfc4422#page-8
> > - if ($smtp_auth !~ /^(\b[A-Z0-9-_]{1,20}\s*)*$/) {
> > + if ($smtp_auth && $smtp_auth !~ /^(\b[A-Z0-9-_]{1,20}\s*)*$/) {
> > die "invalid smtp auth: '${smtp_auth}'";
> > }
>
> Thanks, makes sense. I wonder if moving the check to the point where
> $smtp_auth is actually used (despite the noisier diff) would be cleaner,
> like this:
>
> --- 8< ---
> diff --git a/git-send-email.perl b/git-send-email.perl
> index c5a3f76..2a5ceda 100755
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -1134,12 +1134,6 @@ sub smtp_auth_maybe {
> Authen::SASL->import(qw(Perl));
> };
>
> - # Check mechanism naming as defined in:
> - # https://tools.ietf.org/html/rfc4422#page-8
> - if ($smtp_auth !~ /^(\b[A-Z0-9-_]{1,20}\s*)*$/) {
> - die "invalid smtp auth: '${smtp_auth}'";
> - }
> -
> # TODO: Authentication may fail not because credentials were
> # invalid but due to other reasons, in which we should not
> # reject credentials.
> @@ -1154,6 +1148,12 @@ sub smtp_auth_maybe {
> my $cred = shift;
>
> if ($smtp_auth) {
> + # Check mechanism naming as defined in:
> + # https://tools.ietf.org/html/rfc4422#page-8
> + if ($smtp_auth !~ /^(\b[A-Z0-9-_]{1,20}\s*)*$/) {
> + die "invalid smtp auth: '${smtp_auth}'";
> + }
> +
> my $sasl = Authen::SASL->new(
> mechanism => $smtp_auth,
> callback => {
> --- 8< ---
By moving the patch into the sub-subroutine (is this a lambda? I'm not
too familiar with my perl), I think you change the order of the checks.
So, previously, initial password auth would happen after the
$smtp_auth format check. With your patch, it comes first.
My patch:
$ git send-email --smtp-auth="@" ...
...
Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
invalid smtp auth: '@' at ./git-send-email.perl line 1140.
Your patch:
$ git send-email --smtp-auth="@" ...
...
Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
Password for xxxx:
invalid smtp auth: '@' at ./git-send-email.perl line 1155.
Seems like the former is a little better, so you don't have to waste
time with your password too many times.
Regards,
Brian
next prev parent reply other threads:[~2015-09-18 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 22:12 [PATCH] send-email: fix uninitialized var warning for $smtp_auth Brian Norris
2015-09-18 22:25 ` Eric Sunshine
2015-09-18 22:42 ` Brian Norris [this message]
2015-09-18 22:47 ` Eric Sunshine
2015-09-18 22:50 ` Brian Norris
2015-09-21 17:52 ` Junio C Hamano
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=20150918224242.GA45466@google.com \
--to=computersforpeace@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
--cc=viktorin@rehivetech.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.