No validation of discovered cookie - leading to requestsync erroneously assuming that I am in core-dev

Bug #325923 reported by Max Bowsher
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: ubuntu-dev-tools

I just experienced requestsync falsely believing I'm a core-dev.

It turned out to be that it was picking up a dead launchpad logincookie from an old firefox user profile instead of my active firefox profile.

This was compounded by there being no checking whether the discovered cookie is still valid, and further compounded by ubuntutools.lp.isLPTeamMember silently returning True if the cookie it is using is invalid.

1) ubuntu-dev-tools needs to be intelligent about using the *right* firefox profile when there is more than one.

2) When a launchpad cookie is discovered, it must not blindly assumed to be valid

3) isLPTeamMember needs to understand the difference between a page asking you to login, and a page telling you you are a member of a team

[ And 4) isLPTeamMember refers to the sys and urllib2 modules in the error handling code, but doesn't import them, so if an error occurs, it dies messily ]

Revision history for this message
Anders Kaseorg (andersk) wrote :

This patch rewrites isLPTeamMember to use launchpadlib instead.

Changed in ubuntu-dev-tools (Ubuntu):
status: New → Confirmed
Revision history for this message
Anders Kaseorg (andersk) wrote :

Apparently a similar patch was already included in bzr (r394), so ignore that.

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

I'll mark it as won't fix & have removed the sponsors team then, since it looks to already be in 0.74

Changed in ubuntu-dev-tools (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.