hydrazine doesn't check for the access granted

[Vincent Ladeuil]

I installed hydrazine in a new environment and made a mistake: I grant *read* access for eveything.
This didn't sound silly at the time...

Then I encounter problem with feed-pqm, some weird traceback (sorry I didn't keep it) when sending a submission
by mail.

But the submission was sent anyway !

Since I was in a hurry I forgot about it for a while until I try making a submission again and *then* I noticed a 401 HTTP error. I suspect it was when feed-pqm tried to post the 'sent by mail' comment to the mp.

So I remove the .cache/hydrazine dir and started again, granted write access and viola, it works.

[Martin Pool (mbp)]

launchpadlib now lets the app specify what access it wants. Perhaps
hydrazine should just ask for all access?

[Vincent Ladeuil (vila)]

At least feed-pqm should, since it intends to post on the user behalf.

[Max Bowsher (maxb)]

Should it ask for access to private things?

[Martin Pool (mbp)]

On 21 September 2010 19:03, Max Bowsher <email address hidden> wrote:
> Should it ask for access to private things?

If you mean "should it get access to private bugs" then I think yes,
that's clearly useful.

If you mean "should it check with the user before requesting access to
private bugs" then I think it depends on whether the user would ever
want to refuse access to private bugs. Since hydrazine is intended to
run directly under the control of the user and they have the source, I
don't really see why they would want to refuse. So let's keep it
simple for now.

--
Martin