Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

2013-07-15 Thread R. David Murray
On Mon, 15 Jul 2013 11:09:08 +0300, Michael Foord mich...@voidspace.org.uk wrote: On 15 Jul 2013, at 11:05, M.-A. Lemburg m...@python.org wrote: Who would be the one to contact for issues like these ? The case is rather urgent, since the XSS can be used for stealing session cookies

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

2013-07-15 Thread Brett Cannon
On Mon, Jul 15, 2013 at 9:33 AM, Brett Cannon br...@python.org wrote: On Mon, Jul 15, 2013 at 8:08 AM, R. David Murray rdmur...@bitdance.comwrote: On Mon, 15 Jul 2013 11:09:08 +0300, Michael Foord mich...@voidspace.org.uk wrote: On 15 Jul 2013, at 11:05, M.-A. Lemburg m...@python.org

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

2013-07-15 Thread R. David Murray
On Mon, 15 Jul 2013 08:22:40 -0400, Donald Stufft don...@stufft.io wrote: So I was able to log in to the nobody account without a password (Why is this even possible?). It gave me powers to edit users and some other shit. I added a password to the nobody account since these lists are publicly

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

2013-07-15 Thread Antoine Pitrou
On 2013-07-15 17:16, R. David Murray wrote: I will make the password available to whoever is in charge, (Or they can just change the password themselves I don't care). I think the user should just be retired. My guess is that it dates from a time when we were less worried about bad actors

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

2013-07-15 Thread Ronald Oussoren
On 15 Jul, 2013, at 18:02, Antoine Pitrou solip...@pitrou.net wrote: On 2013-07-15 17:16, R. David Murray wrote: I will make the password available to whoever is in charge, (Or they can just change the password themselves I don't care). I think the user should just be retired. My guess is

Re: [python-committers] I would suggest not pushing or pulling from the repo

2013-07-15 Thread Benjamin Peterson
There's no unwanted head to close. It's all on the 3.3 branch. 2013/7/15 Jason R. Coombs jar...@jaraco.com: The other option is you could 'close' the unwanted head and create a new head at the point before the unwanted merge. -Original Message- From: python-committers

[python-committers] IMPORTANT: Strip your repos if you pulled recently

2013-07-15 Thread Benjamin Peterson
If you have c3a510b22218 in your repo, you will need to strip it like this $ hg strip c3a510b22218 (make sure to have the mq extension enabled) Sorry for the trouble. -- Regards, Benjamin ___ python-committers mailing list

Re: [python-committers] I would suggest not pushing or pulling from the repo

2013-07-15 Thread Benjamin Peterson
Okay, I fixed the repo. You may need to strip your repo per my last mail. 2013/7/15 Benjamin Peterson benja...@python.org: I accidently pushed a merge from 3.3 to default in the 3.3 branch. I think I'm going to have to strip it. -- Regards, Benjamin -- Regards, Benjamin