From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: Test failure: Test #3 in t1304-default-acl
Date: Mon, 17 Sep 2012 13:35:17 -0700 [thread overview]
Message-ID: <7vvcfctmka.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpqipbcpp69.fsf@grenoble-inp.fr> (Matthieu Moy's message of "Mon, 17 Sep 2012 18:52:30 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> I haven't been paying attention, but does that mean on that system,
>> a total stranger kseygold can write, modify, and remove whatever Ram
>> owns? I am hoping that is not the case.
>
> I can see two reasons for having the same UID for two login names:
>
> 1) the sysadmin really messed up, and as you say, a total stranger has
> complete ownership of your files. Ramkumar, you should check that this
> is not your case.
>
> 2) the sysadmin explicitely gave two login names to the same physical
> person, as kinds of aliases for the same UID (e.g. the person got
> married, changed her name and login, but expects ~oldlogin to continue
> working). I'm not sure how common this is, and to which extend we want
> to support this in our test scripts.
I've only been assuming (1), but (2) feels like a legitimate (if
confusing) way to configure your system.
It is a separate issue if it is worth bending backwards to support
it in the test, though.
next prev parent reply other threads:[~2012-09-17 20:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 14:18 Test failure: Test #3 in t1304-default-acl Ramkumar Ramachandra
2012-09-17 14:26 ` Matthieu Moy
2012-09-17 15:01 ` Ramkumar Ramachandra
2012-09-17 15:23 ` Matthieu Moy
2012-09-17 15:25 ` Ramkumar Ramachandra
2012-09-17 15:49 ` Matthieu Moy
2012-09-17 16:37 ` Junio C Hamano
2012-09-17 16:52 ` Matthieu Moy
2012-09-17 17:59 ` Joachim Schmitz
2012-09-17 20:35 ` Junio C Hamano [this message]
2012-10-01 7:38 ` Ramkumar Ramachandra
2012-10-01 8:08 ` Joachim Schmitz
2012-10-01 16:07 ` Junio C Hamano
2012-09-18 6:19 ` Ramkumar Ramachandra
2012-09-17 15:29 ` Andreas Schwab
2012-09-17 15:32 ` Ramkumar Ramachandra
2012-09-17 17:08 ` Andreas Schwab
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=7vvcfctmka.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=artagnon@gmail.com \
--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).