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] [thread-next>] [day] [month] [year] [list]
Message-ID: <33307c790901160935v2495615fo4ee0998d348fa117@mail.gmail.com>
Date:	Fri, 16 Jan 2009 09:35:45 -0800
From:	Martin Bligh <mbligh@...gle.com>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	bugme-admin@...ux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Bugzilla permissions

> Dear bugzilla admin,

Please send bugzilla admin emails to bugme-admin@...ux-foundation.org
(is linked from the front page of http://bugzilla.kernel.org). Sorry, I can't
keep up with reading all of LKML nowadays ;-)

> Could you please unlock bugzilla so that everybody (starting with me)
> is allowed to change the attachment types? I am a bit tired of having
> to e-mail the person who created the attachment to ask him/her to
> change the type from application/octet-stream to text/plain so that I
> can see the attachment directly in my web browser. If we want people to
> help with bugs, we must make it as easy for them as possible.

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
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.

I enabled your account. Thanks for looking at bugs ;-)

M.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ