Comments on: Status update for Chrome Protocol Directory Traversal issue http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/ Thu, 19 Nov 2009 15:36:11 -0800 http://wordpress.org/?v=2.8.6 hourly 1 By: Jeff Walden http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/comment-page-1/#comment-17163 Jeff Walden Thu, 31 Jan 2008 10:07:30 +0000 http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/#comment-17163 Sorry, Ronald, but I don't see "boasting" or "blame" there -- just matter-of-fact statements, and a note that extensions that can update quickly enough can reduce the number of vulnerable users until the real fix happens. Sorry, Ronald, but I don’t see “boasting” or “blame” there — just matter-of-fact statements, and a note that extensions that can update quickly enough can reduce the number of vulnerable users until the real fix happens.

]]> By: Ronald van den Heetkamp http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/comment-page-1/#comment-17143 Ronald van den Heetkamp Thu, 31 Jan 2008 09:07:02 +0000 http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/#comment-17143 Some comments: http://www.0x000000.com/index.php?i=503 Some comments:

http://www.0×000000.com/index.php?i=503

]]> By: Jason Barnabe http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/comment-page-1/#comment-16873 Jason Barnabe Wed, 30 Jan 2008 03:26:00 +0000 http://blog.mozilla.com/security/2008/01/29/status-update-for-chrome-protocol-directory-traversal-issue/#comment-16873 I'm fairly sure you can release 2.0.0.12 and get it into the hands of users before I can new versions of my extensions approved and updated on my users' systems, so I'll just wait this one out. I’m fairly sure you can release 2.0.0.12 and get it into the hands of users before I can new versions of my extensions approved and updated on my users’ systems, so I’ll just wait this one out.

]]>