Re:Rel="logo" (2011)
by toyg on Sunday February 10, 2013 @05:00PM
(#5198121)
I can see various applications where third-party sites could enjoy the opportunity to reliably "pull" official logos that never get old, without having to duplicate/rehost/modify them and/or incur in trademark diatribes.
For example, a stock-trading website could have official logos near (or even replacing) stock tickers. "Log in with *" buttons could be dropped altogether, mandating websites to pull the official logo. And so on.
However, like every "machine-oriented" standard that promotes embedding, I can't help but feel there are security implications, something which might not be obvious now but will end up biting our ass 5 years down the line, when spammers and gangsters start exploiting some hole in the mechanism. Embedding untrusted images is already unsafe as it is, adding support for SVG looks even more unsafe.
EDIT: and as someone else mentioned, it makes phishing easier.
For example, a stock-trading website could have official logos near (or even replacing) stock tickers. "Log in with *" buttons could be dropped altogether, mandating websites to pull the official logo. And so on.
However, like every "machine-oriented" standard that promotes embedding, I can't help but feel there are security implications, something which might not be obvious now but will end up biting our ass 5 years down the line, when spammers and gangsters start exploiting some hole in the mechanism. Embedding untrusted images is already unsafe as it is, adding support for SVG looks even more unsafe.
EDIT: and as someone else mentioned, it makes phishing easier.