From: M Hickford <mirth.hickford@gmail.com>
To: julian@swagemakers.org
Cc: git@vger.kernel.org, wiagn233@outlook.com, sandals@crustytoothpaste.net
Subject: Re: [PATCH] send-email: implement SMTP bearer authentication
Date: Tue, 7 Jan 2025 19:49:50 +0000 [thread overview]
Message-ID: <20250107194953.2104-1-mirth.hickford@gmail.com> (raw)
In-Reply-To: 20240228175329.3371-1-mirth.hickford@gmail.com
Hi Julian. The patch looks good. Please could you add instructions how to test it? Which servers have you tested?
I have a gmail.com account. I configured Git following https://git-scm.com/docs/git-send-email#_use_gmail_as_the_smtp_server
[sendemail]
smtpEncryption = tls
smtpServer = smtp.gmail.com
smtpUser = yourname@gmail.com
smtpServerPort = 587
And configured git-credential-oauth following https://github.com/hickford/git-credential-oauth/issues/48#issuecomment-1966486513
[credential "smtp://smtp.gmail.com:587"]
oauthClientId = 406964657835-aq8lmia8j95dhl1a2bvharmfk3t1hgqj.apps.googleusercontent.com
oauthClientSecret = kSmqreRr0qwBWJgbf5Y-PjSU
oauthScopes = https://mail.google.com/
oauthAuthURL = https://accounts.google.com/o/oauth2/auth
oauthTokenURL = https://oauth2.googleapis.com/token
Then tested with: git send-email --smtp-auth=XOAUTH2 --smtp-debug=1 message.txt
"git credential" was queried for an OAuth access token as expected. Note that Gmail access tokens are very long (~220 characters).
However smtp.gmail.com responded authentication error "535-5.7.8 Username and Password not accepted".
Looking at the debug information, it looks like the SMTP command "AUTH XOAUTH2 <base64>" was corrupted by a space at column 241. Exactly one base64 string should follow "AUTH XOAUTH2 ", no spaces.
The same problem occurs with OAUTHBEARER: git send-email --smtp-auth=OAUTHBEARER --smtp-debug=1 message.txt
I can reproduce this with any sufficiently long combination of user and pass, such as: git send-email --smtp-auth=XOAUTH2 --smtp-user=tim.arsietonarsei@example.com --smtp-pass=arsteiarositanrestnerastarstarstarstarstarsetnrasetnearstrasitenarseitnerasntearnstenarsetnearstarstearsetnariestnearsntenarestnerast --smtp-encryption=tls --smtp-server-port=587 --smtp-server=smtp.gmail.com --smtp-debug=1 message.txt
Can you reproduce this problem?
Any ideas?
I think the bug must be in the call to Net::SMTP.
next reply other threads:[~2025-01-07 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 19:49 M Hickford [this message]
2025-01-11 19:06 ` [PATCH] send-email: implement SMTP bearer authentication Julian Swagemakers
2025-01-11 21:19 ` M Hickford
-- strict thread matches above, loose matches on Subject: below --
2025-01-11 21:27 M Hickford
2024-02-25 10:34 Julian Swagemakers
2024-02-28 17:53 ` M Hickford
2024-10-11 17:48 ` Shengyu Qu
2024-10-11 18:05 ` Junio C Hamano
2024-10-11 18:24 ` Shengyu Qu
[not found] ` < <TYCPR01MB8437CDD2208EA6555117E72C98792@TYCPR01MB8437.jpnprd01.prod.outlook.com>
2024-10-12 18:43 ` Julian Swagemakers
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=20250107194953.2104-1-mirth.hickford@gmail.com \
--to=mirth.hickford@gmail.com \
--cc=git@vger.kernel.org \
--cc=julian@swagemakers.org \
--cc=sandals@crustytoothpaste.net \
--cc=wiagn233@outlook.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 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 NNTP newsgroup(s).