4 ms·
Perhaps, if the <link> points to a menu.xml you don't control? I'm not sure what you could do with this that couldn't also be done with <link rel=stylesheet>...
by psadauskas 16y ago
Perhaps, if the <link> points to a menu.xml you don't control? I'm not sure what you could do with this that couldn't also be done with <link rel=stylesheet>...
- count 16y agoSorry, I wasn't more clear. I meant the browser feature, not the specific implementation. I think the idea in the article was fantastic, and would be much cleaner for developers.
- count 16y agoWhy was this voted down so harshly?
- ars 16y agoIt didn't deserve -1, but I guess it was downvoted because it's wrong? Why would the existence of this feature lead to a remote compromise? The specific implementation maybe, but the idea??
- count 16y agoMy original comment deserved it then, not my clarification and praise of the implementation idea in the article? The idea of a website being able to inject things into the task bar menu seems like it would open the door for injecting things that overflow buffers, call other code, etc. What is the security model for that code? What are the limits on what the URL can point to, etc. It's not like the IE team has a stellar record for this kind of stuff?
- psadauskas 16y agoI can't seem to ropy to the child of this post, but this is a response to that. All of those risks are present for PDFs or png images. If the browser's XML parser is vulnerable, having this feature additionally available won't make and difference.
- aberkowitz 16y agoThe pinned menu feature allows you to put images and text on a native system menu. It is conceivable that a malicious person could use this to crash the browser, or have unauthorized code run.