public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Peter Novodvorsky <nidd@altlinux.ru>
To: Milan Zamazal <pdm@zamazal.org>
Cc: gnats-devel@sources.redhat.com
Subject: Re: modular database backends
Date: Tue, 29 May 2001 12:43:00 -0000	[thread overview]
Message-ID: <7x4ru4kl9y.fsf@lambda.novdv.ru> (raw)
In-Reply-To: <878zjhdvwu.fsf@blackbird.zamazal.org>

Milan Zamazal <pdm@zamazal.org> writes:

> >>>>> "PN" == Peter Novodvorsky <nidd@altlinux.ru> writes:
> 
>     PN>         Second thing I don't like in GNATS, it doesn't has
>     PN> ACLs. This modular framework should support them.  Here is the
>     PN> header file that will briefly describe what I mean:
> 
> I'm afraid I couldn't understand what kind of ACLs you would like to
> have.  Could you elaborate?

1). i don't like that client can pass without authentication phase.
If he want to login as anonymous,  he  has to do it. IE,

USER anonymous nidd@altlinux.ru

2). I don't like that check of user/password is made by gnatsd and not
by "database driver". I mean that function that authentificates user
isn't called by init_gnats that actually connects to database, but after
it.  Access control is done by gnatsd, and not by database driver.

3). There is no access control for query-pr, send-pr and edit-pr. This 
is close to the subject of 2)., because  authentification is made on
the side of client, not on the side of database.

Advanced topics.

4). I want that some bugs  can be edited only by group of developers.
It can't be done in current version.

Is it enough? ;-)


> However, no new features will get into GNATS 4.0.  I think the backend
> architecture and the MIME handling could be the main feature candidates
> for the first non-bug-fix release after 4.0.  Of course, we can start
> discussing the API and architecture now and you can also work on a
> preliminary implementation in the meantime, just don't expect it to have
> it in 4.0.

May be you could make a CVS branch for 4.99?

> BTW, please note I'll be soon out of Internet for about a week or two.

Heh, that's bad because I wanted to begin making implementation very
actively. Do you have thoughts on the subject?  I'm writing
``specification'' of some kind. Maybe it   will give the subject for
discussion.

Regards,

-- 
Peter Novodvorsky     http://www.altlinux.ru/    AltLinux Team, Russia
Debian.Org                                       http://debian.org/~nidd
            Debian  ---  no need to  wait for tomorrow.

  reply	other threads:[~2001-05-29 12:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27 11:32 Peter Novodvorsky
2001-05-28  2:43 ` Yngve Svendsen
2001-05-28  4:34   ` Peter Novodvorsky
2001-06-04 21:53   ` Margaret BRIERTON
2001-06-05  1:35     ` GNATS discussion group Yngve Svendsen
2001-06-05 19:56       ` Margaret BRIERTON
2001-06-06  4:54         ` Yngve Svendsen
2001-06-07 17:04           ` Margaret BRIERTON
2001-06-07 18:15             ` Database Margaret BRIERTON
2001-05-28 14:37 ` modular database backends Milan Zamazal
2001-05-29 12:43   ` Peter Novodvorsky [this message]
2001-06-11 11:53     ` Milan Zamazal
2001-06-13 10:31       ` Peter Novodvorsky
2001-06-17 12:26         ` Milan Zamazal
2001-06-11 11:53 ` access control (was Re: modular database backends) Milan Zamazal
2001-06-13  5:20   ` access control Hans-Albert Schneider
2001-06-17 12:26     ` Milan Zamazal
2001-06-13 10:44   ` access control (was Re: modular database backends) Peter Novodvorsky
2001-05-27 11:35 modular database backends Peter Novodvorsky
2001-05-29  0:11 Dirk Bergstrom
2001-05-29  0:22 ` Bob Kaehms
2001-05-29  1:16   ` Peter Novodvorsky

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=7x4ru4kl9y.fsf@lambda.novdv.ru \
    --to=nidd@altlinux.ru \
    --cc=gnats-devel@sources.redhat.com \
    --cc=pdm@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).