I had one more thought after I attempted to post a comment. If a user decides to change which OpenID provider they use, currently this would not be possible on your site. I got a duplicate key error, because I'm assuming you use a natural key for the users table. Do you think it would a good idea to allow users to update the OpenID attached to their account in the same way you might have previously permitted a user to update their email address?
Thanks for the tip. This should come in handy for all those passwords I never remember.
By the way, it was neat to see your article on foiling XSRF referenced in my database class this semester. It's always fun when I'm ahead of the curve.
If Amazon really considered it a "top priority" I would hope they could have addressed it within a year. I feel that this was a very generous time period. If it takes disclosure to motivate them to fix it, then at least it gets done. As Chris said, I'm sure he's not the only person who has figured this exploit out by now.
Sure, this might temporarily increase the level of vulnerability, but if it inspires Amazon to take documented vulnerabilities more seriously, I'd say its worth it.
After reading up on the issue, it appears to be an IE 7 bug, that can't really be fixed without using invalid css. If there is a way to fix it without setting "zoom: 100%" I can't seem to find it.
The new design looks wonderful! Easily one of the most visually appealing and accessible blogs I've seen. Just to let you know though, IE7 messes up the padding in your menu if you scale the text.
I'll check back to see how you fix it because its a problem bothering me right now as well ;).
Last 10 Comments
1
2
3
4
5