Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug #799552

41 views
Skip to first unread message

David E. Ross

unread,
Oct 13, 2012, 12:42:10 PM10/13/12
to
Why is viewing bug #799552 restricted? Is there really a security
vulnerability involved?

<https://bugzilla.mozilla.org/show_bug.cgi?id=799552>

--

David E. Ross
<http://www.rossde.com/>

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
� 1997 by David E. Ross

Kyle Huey

unread,
Oct 13, 2012, 12:49:19 PM10/13/12
to dev-pl...@lists.mozilla.org
On Sat, Oct 13, 2012 at 9:42 AM, David E. Ross <nob...@nowhere.invalid>wrote:

> Why is viewing bug #799552 restricted? Is there really a security
> vulnerability involved?
>
> <https://bugzilla.mozilla.org/show_bug.cgi?id=799552>
>

Are you perhaps looking for Bug 799952?

- Kyle

David E. Ross

unread,
Oct 13, 2012, 7:53:19 PM10/13/12
to
For various reasons, I track a number of bug reports. One of them is
bug #718066.

Yes, I meant #799552. That's what I get for typing the bug number
instead of copying it from bug #718066.

Bug #718066 indicates it is dependent on bug #799552. I'm not the first
person to question why viewing that latter bug report is blocked. See
<https://bugzilla.mozilla.org/show_bug.cgi?id=718066#c69>.

Kyle Huey

unread,
Oct 13, 2012, 7:59:26 PM10/13/12
to dev-pl...@lists.mozilla.org
On Sat, Oct 13, 2012 at 4:53 PM, David E. Ross <nob...@nowhere.invalid>wrote:

> On 10/13/12 9:49 AM, Kyle Huey wrote:
> > On Sat, Oct 13, 2012 at 9:42 AM, David E. Ross <nob...@nowhere.invalid
> >wrote:
> >
> >> Why is viewing bug #799552 restricted? Is there really a security
> >> vulnerability involved?
> >>
> >> <https://bugzilla.mozilla.org/show_bug.cgi?id=799552>
> >>
> >
> > Are you perhaps looking for Bug 799952?
> >
> > - Kyle
> >
>
> For various reasons, I track a number of bug reports. One of them is
> bug #718066.
>
> Yes, I meant #799552. That's what I get for typing the bug number
> instead of copying it from bug #718066.
>
> Bug #718066 indicates it is dependent on bug #799552. I'm not the first
> person to question why viewing that latter bug report is blocked. See
> <https://bugzilla.mozilla.org/show_bug.cgi?id=718066#c69>.


Given that Stacey Martin filed it, I suspect it is in the legal component.
All bugs there are private (even to most MoCo employees) because of
attorney-client privilege considerations.

Whether that's the right place for it to be, I can't say, but that's
probably why you can't see it.

- Kyle

Gavin Sharp

unread,
Oct 13, 2012, 10:09:28 PM10/13/12
to Kyle Huey, dev-pl...@lists.mozilla.org
On Sun, Oct 14, 2012 at 1:59 AM, Kyle Huey <m...@kylehuey.com> wrote:
> Given that Stacey Martin filed it, I suspect it is in the legal component.
> All bugs there are private (even to most MoCo employees) because of
> attorney-client privilege considerations.
>
> Whether that's the right place for it to be, I can't say, but that's
> probably why you can't see it.

The bug is in the Privacy component in the Legal product. Tom
Lowenthal explained (via private email, after I asked in bug 718066)
that this is just a side effect of how the component was originally
set up (as part of the Legal product). They are working on creating a
new Privacy Bugzilla product that doesn't have these hard-coded access
restrictions - that is tracked in bug 764156.

Gavin
0 new messages