From: <rsbecker@nexbridge•com>
To: "'usharerose'" <ushareroses@gmail•com>
Cc: <git@vger•kernel.org>
Subject: RE: [DISCUSS] validation on git config user.email
Date: Fri, 12 Sep 2025 13:23:31 -0400 [thread overview]
Message-ID: <071e01dc2409$f9785230$ec68f690$@nexbridge.com> (raw)
In-Reply-To: <CAJKmQvcqLzJDnpYg5K7_eUNCUdLCkkFse-wB+4R8KGxKo_e+0w@mail.gmail.com>
On September 12, 2025 12:52 PM, usharerose wrote:
>On Fri, Sep 12, 2025 at 11:00 PM <rsbecker@nexbridge•com> wrote:
>> Some customers integrate single sign-on (SSO) via the user.email
>> value. In the case of one customer I helped, the value is an SSO token
>> used by GitHub for their integration. The token value does not conform to any
>valid email address format.
>> Adding an email validation will lock them out of using git.
>
>Thanks for your reply, Randall.
>
>I've fully understood the scenario you described. My follow-up question is: was this
>use case something that was discovered and utilized later because people found
>that Git doesn't validate the email format, or was it a scenario that the architects
>anticipated early on in the project's history, leading to the deliberate decision to skip
>the validation for flexibility?
>
>In other words, is this more of a case of "exploiting a perceived backdoor that later
>became justified" or "a thoughtfully made design decision from the beginning"?
>
>Thanks again for sharing your insight.
I cannot answer decisively. The functionality was first used in this customer about
four years ago. I do not think any changes were required in git to accomplish this.
It is possible GitHub had to have an enhancement but only they can answer that.
next prev parent reply other threads:[~2025-09-12 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 4:13 [DISCUSS] validation on git config user.email usharerose
2025-09-12 15:00 ` rsbecker
2025-09-12 16:29 ` Junio C Hamano
2025-09-12 18:06 ` usharerose
2025-09-12 16:52 ` usharerose
2025-09-12 17:23 ` rsbecker [this message]
2025-09-12 17:44 ` usharerose
2025-09-14 11:17 ` Kristoffer Haugsbakk
2025-09-14 16:59 ` rsbecker
2025-09-12 15:13 ` Konstantin Ryabitsev
2025-09-12 15:39 ` Thomas Guyot
2025-09-12 18:02 ` usharerose
2025-09-14 11:58 ` Kristoffer Haugsbakk
2025-09-15 13:40 ` usharerose
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='071e01dc2409$f9785230$ec68f690$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ushareroses@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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