From: Igor Vlasenko <vlasenko@imath.kiev.ua>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Cc: ldv@altlinux.org
Subject: Re: [devel] (gcc-gnat) repocop-lintian: bad-permissions-for-ali-file
Date: Tue, 6 May 2008 12:32:09 +0300
Message-ID: <20080506093209.GA8775@dad.imath.kiev.ua> (raw)
In-Reply-To: <20080506092137.GB7336@wo.int.altlinux.org>
On Tue, May 06, 2008 at 01:21:37PM +0400, Dmitry V. Levin wrote:
> Надо поправить тест, поскольку права доступа 0644 вполне адекватны
> приведённому ниже обоснованию. Кроме того, на процессы с fsuid==0
> эти ограничения прав доступа обычно не распространяются.
Я вот не уверен. Вот что говорит народ:
http://osdir.com/ml/debian.devel.policy/2004-02/msg00027.html
ill Allombert <allomber@xxxxxxxxxxxxxxxxxx> writes:
> Why is it not sufficient for the file to be `write-protected' for the
> user running gnat instead of all users including root ? Or if it is, why
> when running as root cannot it add the compiled files in the same
> directory ? If it is not, why not just fix the test ?
The file must be 0444, not 0644. The reason for this is within GNAT
itself; I think it has to do with portability (with Windows, OpenVMS).
If we would change this for Debian, we would become incompatible with
the other platforms and distributions where GNAT runs.
Одним словом, надо выяснить.
--
Dr. Igor Vlasenko
--------------------
Topology Department
Institute of Math
Kiev, Ukraine
next prev parent reply other threads:[~2008-05-06 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 7:31 Igor Vlasenko
2008-05-06 9:21 ` Dmitry V. Levin
2008-05-06 9:32 ` Igor Vlasenko [this message]
2008-05-06 15:18 ` Alexey Tourbin
2008-05-06 18:08 ` Mikhail Gusarov
2008-05-06 18:49 ` Alexey Tourbin
2008-05-06 20:04 ` Mikhail Gusarov
2008-05-06 20:59 ` Dmitry V. Levin
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=20080506093209.GA8775@dad.imath.kiev.ua \
--to=vlasenko@imath.kiev.ua \
--cc=devel@lists.altlinux.org \
--cc=ldv@altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git