From: Rick van Rein <rick@openfortress.nl>
To: git@vger.kernel.org
Subject: Git over HTTP; have flexible SASL authentication
Date: Fri, 27 Jan 2023 16:34:34 +0000 [thread overview]
Message-ID: <20230127163434.GA784@openfortress.nl> (raw)
Hello,
Git providers are inventing proprietary extensions to HTTP authentication
for Git. It seems smarter to use SASL for this purpose, possibly allowing
the client a choice and authentication ringback to the client's own domain.
I wrote an Internet Draft to allow just that, and we implemented it for
Apache, Nginx and FireFox. I would love to learn if this list considers
it a sensible extensions to Git.
https://datatracker.ietf.org/doc/html/draft-vanrein-httpauth-sasl
If you think this is useful, it would be wonderful to mention that on the
HTTP WorkGroup list as well, because they are now considering HTTP-SASL
for adoption, a formal requisite to send "Authorization: SASL" headers.
https://datatracker.ietf.org/wg/httpbis/about/
Thanks!
Rick van Rein
InternetWide.org
Apache :- https://gitlab.com/arpa2/apachemod/-/tree/master/arpa2_sasl
https://gitlab.com/arpa2/apachemod/-/tree/master/arpa2_diasasl
Nginx :- https://github.com/stef/ngx_http_auth_sasl_module
FireFox :- https://gitlab.com/arpa2/http_sasl_client
next reply other threads:[~2023-01-27 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 16:34 Rick van Rein [this message]
2023-01-27 17:06 ` Git over HTTP; have flexible SASL authentication Junio C Hamano
2023-02-01 11:24 ` Jeff King
2023-02-01 19:36 ` Matthew John Cheetham
2023-02-04 11:34 ` Rick van Rein
2023-02-06 22:08 ` 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=20230127163434.GA784@openfortress.nl \
--to=rick@openfortress.nl \
--cc=git@vger.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 NNTP newsgroup(s).