sec
team. This also won't improve the situation.
So, I think we cannot do much to avoid further confusion in the future
Marcus
-Original Message-
From: Marcus [mailto:marcus.m...@wtnet.de]
Sent: Friday, September 16, 2016 09:52
To: dev@openoffice.apache.org
Subject: Re: Acces
org
> Subject: Re: Access denied on bugzilla ...
>
> Dennis, please have a look into the history of the issue [1]. Here you
> can see that *Pedro has not* set the assignee. The reason is the BZ
> setting of the "security" component he has chosen at issue creation. So,
>
ity, do not use bugzilla.
Communicate with the security@ mailing list directly.
- Dennis
-Original Message-
From: Pedro Giffuni [mailto:p...@apache.org]
Sent: Friday, September 16, 2016 08:41
To: OOo Apache
Subject: Access denied on bugzilla ...
FWIW ...
I just tried to access BZ
t: Friday, September 16, 2016 08:41
> To: OOo Apache
> Subject: Access denied on bugzilla ...
>
> FWIW ...
> I just tried to access BZ 127117, which I created in the first place,
> and now I got
> "You are not authorized to access issue #127117."
> It is only a very mino
Dennis was faster and fixed this in the meantime.
Marcus
Am 09/16/2016 05:41 PM, schrieb Pedro Giffuni:
FWIW ...
I just tried to access BZ 127117, which I created in the first place, and now I
got
"You are not authorized to access issue #127117."
It is only a very minor update to openssl, an
FWIW ...
I just tried to access BZ 127117, which I created in the first place, and now I
got
"You are not authorized to access issue #127117."
It is only a very minor update to openssl, and I wanted to submit the patch to
do it.(AOO bugzilla and I have never been in a good relationship).
While he
