public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: elzubeir@fakkir.net
To: pdm-gnats@zamazal.org,gnats-prs@gnu.org,bug-gnats@gnu.org
Subject: gnats/314: gnats.host_acess access-level overrides gnatsd.access settings
Date: Mon, 22 Oct 2001 08:09:00 -0000	[thread overview]
Message-ID: <E16HBwt-0002vR-00@fencepost.gnu.org> (raw)

>Number:         314
>Category:       gnats
>Synopsis:       gnats.host_acess access-level overrides gnatsd.access settings
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 20 17:45:58 -0500 2001
>Originator:     Mohammed Elzueir
>Release:        4.0-alpha
>Organization:
Arabeyes Project (http://www.arabeyes.org/)
>Environment:
Debian Linux (woody), i386.
>Description:
When the gnatsd.host_access access-level is set to 'view' (for example), and gnatsd.acess has users with various access-levels - only the access-level set on gnatsd.host_access prevail.

That does not appear to happen when the passwords are stored in clear-text (ie. $0$passme). If the passwords are encrypted, it fails to see the user access-level and defaults to gnatsd.host_acess settings.
>How-To-Repeat:
1. In /etc/gnats/gnatsd.host_access put:
127.0.0.1:view:

2. In /var/lib/gnats/gnats-db/gnats-adm/gnatsd.access put:
plainguy:$0$test:edit:default
cryptguy:4/1d3Y7NqgISI:admin:default

The cryptguy password is 'test'. 'plainguy' will have proper access-level, whereas 'cryptguy' will default to 'view'.


>Fix:
Unknown
>Unformatted:
 

_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs


             reply	other threads:[~2001-12-20 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  8:09 elzubeir [this message]
2001-10-22  8:14 ` Yngve Svendsen

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=E16HBwt-0002vR-00@fencepost.gnu.org \
    --to=elzubeir@fakkir.net \
    --cc=bug-gnats@gnu.org \
    --cc=gnats-prs@gnu.org \
    --cc=pdm-gnats@zamazal.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 read-only IMAP folder(s) and NNTP newsgroup(s).