From: axel.ml@laposte•net
To: Jakub Narebski <jnareb@gmail•com>
To: Axel <axel.ml@laposte•net>
Cc: git@vger•kernel.org
Subject: Re: REMOTE_USER value propagation through http push
Date: Wed, 13 Apr 2011 15:39:32 +0200 (CEST) [thread overview]
Message-ID: <22124707.170284.1302701972329.JavaMail.www@wwinf8403> (raw)
In-Reply-To: <m3oc4a2tzf.fsf@localhost.localdomain>
> Could you explain in more detail _what_ behavior would you like to
> see? Gitweb does display author and comitter (though in 'log' and
> 'shortlog' only author is visible).
>
I understand well your explanations about git mechanisms.
Though git is decentralized, we still use a "central" repository on which gitweb is installed, mainly for pratical reasons (you may tell "then you don't need git!" :) ) because not only developers browse the commits history.
At this moment we use HTTP authentication more for tracing purposes (knowing who pushed data to the repo) than for allowing or not push access.
If i m not wrong, the AUTHOR field displayed in gitweb comes from the git client configuration ($GIT_AUTHOR_NAME).
I would go further : HTTP authentication (for in-house organisation of course, not internet-wide access) usefulness is unclear since the credentials do not pop up anywhere in git repository. We have to trust the client-side configuration. The way to know who pushed something is to browse Apache access.log and cross the date/time with the git log.
What I d like to see is that the push authentication credentials overwrite an eventually defined author name at the client side in order to be displayed while browsing git log.
Even better, in the case of LDAP authentication (I m not sure if it would be possible for htaccess authentication), email and fullname could be extracted from LDAP directory, stored in environment variables by Apache, and given to git-http-backend (as is the REMOTE_USER variable).
Though I dont know if this request is relevant, I guess that if git-http-backend was looking for GIT_AUTHOR_NAME & GIT_AUTHOR_EMAIL environment variables that Apache could have defined, it could replace the client-side values defined. (Note that I absolutly don't know if it would be technically possible to overwrite those variables or even if their values are in the push payload).
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net
next prev parent reply other threads:[~2011-04-13 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 9:48 REMOTE_USER value propagation through http push Axel
2011-04-13 11:00 ` Jakub Narebski
2011-04-13 11:21 ` axel.ml
2011-04-13 12:53 ` Jakub Narebski
2011-04-13 13:39 ` axel.ml [this message]
2011-04-13 14:27 ` Jakub Narebski
2011-04-13 14:58 ` axel.ml
2011-04-13 16:32 ` Jakub Narebski
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=22124707.170284.1302701972329.JavaMail.www@wwinf8403 \
--to=axel.ml@laposte$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@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