public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com> To: elzubeir@fakkir.net,pdm-gnats@zamazal.org,gnats-prs@gnu.org, bug-gnats@gnu.org Subject: Re: gnats/314: gnats.host_acess access-level overrides gnatsd.access settings Date: Mon, 22 Oct 2001 08:14:00 -0000 [thread overview] Message-ID: <3.0.5.32.20011221195104.007c44b0@mail.online.no> (raw) In-Reply-To: <E16HBwt-0002vR-00@fencepost.gnu.org> At 17:45 20.12.01 -0500, elzubeir@fakkir.net wrote: >>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'. What you are seeing is the intended behaviour. For some reason, authentication of the 'cryptguy' user fails, and the user then instead gets the default access level defined for the host that the user is on. The problem could be caused by a wrong password hash. You should start off by checking it, for instance by using it for some user in the system passwd file and then trying a login as that user. Yngve Svendsen GNATS doc guy _______________________________________________ Gnats-prs mailing list Gnats-prs@gnu.org http://mail.gnu.org/mailman/listinfo/gnats-prs
prev parent reply other threads:[~2001-12-21 18:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-22 8:09 elzubeir 2001-10-22 8:14 ` Yngve Svendsen [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=3.0.5.32.20011221195104.007c44b0@mail.online.no \ --to=yngve.svendsen@clustra.com \ --cc=bug-gnats@gnu.org \ --cc=elzubeir@fakkir.net \ --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: linkBe 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).