From: Tim Riker <TimR@CalderaSystems.com>
To: Rick Macdonald <rickm@vsl.com>
Cc: John Goerzen <jgoerzen@progenylinux.com>,
gnats-devel@sourceware.cygnus.com
Subject: Re: Local security
Date: Sat, 10 Jun 2000 12:18:00 -0000 [thread overview]
Message-ID: <39429461.83E21121@CalderaSystems.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10006091901280.28716-100000@sys4>
I install gnats databases under /var/lib/gnats-* and then chown them to
gnats:gnats and remove and world permissions. This means that local
users will not be able to access the files at all (as users are not in
the gnats group). This forces network access for everyone. Works very
well for us.
/etc/gnats* should be owned by root, not gnats. These should be group
gnats but not group writeable. The important issue here is just to make
it harder to muck with the access rules. ie: only root can do that.
Rick Macdonald wrote:
>
> On 9 Jun 2000, John Goerzen wrote:
>
> > I'm looking at setting up gnats. It is impressing me so far, and its
> > network security features look good. However, I can't seem to find
> > any options for local security at all. Anybody with an account on the
> > system seems to be able to use edit-pr to change any bug at all. Is
> > there any way to restrict this? Is something misconfigured on my box?
> > Is this feature planned?
>
> About all that you can do is remove or restrict the command line programs
> and then use the network security by using gnatsweb and/or TkGnats as
> front-ends.
>
> ...RickM...
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
prev parent reply other threads:[~2000-06-10 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-09 18:04 John Goerzen
2000-06-09 18:08 ` Rick Macdonald
2000-06-10 12:18 ` Tim Riker [this message]
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=39429461.83E21121@CalderaSystems.com \
--to=timr@calderasystems.com \
--cc=gnats-devel@sourceware.cygnus.com \
--cc=jgoerzen@progenylinux.com \
--cc=rickm@vsl.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).