linux-kernel - Re: Bugzilla permissions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090117110814.GA10385@joi>
Date:	Sat, 17 Jan 2009 12:08:18 +0100
From:	Marcin Slusarz <marcin.slusarz@...il.com>
To:	Martin Bligh <mbligh@...gle.com>
Cc:	Jean Delvare <khali@...ux-fr.org>,
	bugme-admin@...ux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Bugzilla permissions

On Fri, Jan 16, 2009 at 09:35:45AM -0800, Martin Bligh wrote:
> Given that there's no real control on bugzilla accounts, I'm somewhat
> reluctant to make it a complete free for all and let any new user edit
> any bug. However, for anyone running a subsystem, or anyone else
> that I have a vague clue who they are (or any established developer
> will vouch for, anyone I can see git commits for, etc), I am perfectly

Couldn't it be automatic?
Pulling once a day, refreshing mail list by:
git shortlog -e -s|sed "s/.*<\([^>]*\)>/\1/"
and wiring it into bugzilla permission system shouldn't be too time consuming...

> willing to enable global edit on a individual basis. Hasn't been a big
> problem up until now, so I suspect it won't turn into one.

Marcin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/