From: "Luca Weiss" <luca.weiss@fairphone.com>
To: <tools@linux.kernel.org>
Subject: Requirement of using smtpPass
Date: Fri, 09 Dec 2022 13:35:21 +0100 [thread overview]
Message-ID: <COXAHN6YWLQH.33YW8LAHHXH21@otso> (raw)
Hi,
I'm enjoying using b4 so far.
I've noticed that in both my current git-send-email setups (work &
personal address) I don't set smtpPass in my git config.
For example for gmail this is the config:
[sendemail]
smtpserver = smtp.gmail.com
smtpuser = luca.weiss@fairphone.com
smtpencryption = tls
smtpserverport = 587
confirm = always
Regular git-send-email just prompts for the password when needed, or
alternatively I supply it in the invocation with
--smtp-pass=$(get-my-email-password) to avoid putting my email password
plaintext into the config.
However b4 just skips authenticating completely leading to more or less
obscure error messages from the smtp server (b4 only tries to
authenticate if it has both user *and* password set).
Would be great if I could specify in my config a command that will be
run that just prints the password on stdout (e.g. keepassxc-cli with
some parameters) and b4 uses this password then, this is then similar
functionality to the --smtp-pass=$(foo) I wrote above.
Regards
Luca
next reply other threads:[~2022-12-09 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 12:35 Luca Weiss [this message]
2022-12-13 20:19 ` Requirement of using smtpPass Konstantin Ryabitsev
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=COXAHN6YWLQH.33YW8LAHHXH21@otso \
--to=luca.weiss@fairphone.com \
--cc=tools@linux.kernel.org \
/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 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).