<html> <head> <title>Ubiquitous computing - Widget Signing</title> <style type="text/css"> body { font-family: Consolas; height: 100%; width: 100%; } tbody { } thead { font-family: Consolas; font-weight: bolder; } tbody { font-family: "Consolas"; } td { text-indent: justified; } .highlight { font-weight: bolder; background-color: Highlight; color: Maroon; } .contactdetails { color: Blue; font-weight: bolder; } </style> </head> <body> <table> <thead> </thead> <tbody> <tr> <td> <p>Hi,</p> <p>I have a doubt regarding WRT, and Widget Signing. I have a widget that virtually performs functionality of a Browser.</p> <p> Hence, this widget can open content in ubiquious manner. To keep things clear, "Ubiquitous" manner is understood as the capability to access content at various locations, in various formats i.e., Local files using application layer protocols, and Server interaction using transport layer protocols. </p> <p> Please let me know the role of signing widgets, in determining access to services/protocols offered by WRT or platform. </p> <p>Should this <span class="highlight">flexibility</span> be considered as an appreciable feature, or a potential vulnerability. Also, how would WRT handle such vulnerabilities? Would it be the responsibility of WRT, or be delegated to the platform?</p> <p>Kindly suggest if there is any mistake in my understanding. </p> <p class="contactdetails"> K Chandrasekhar Omkar,<br /> <u>E-Mail</u>: <a href="mailto:kcomkar@gmail.com">kcomkar@gmail.com </a>, <br /> <u>Blog</u>: <a href="http://omkarkc.blogspot.com/">http://omkarkc.blogspot.com/</a><br /> </p> </td> </tr> </tbody> <tfoot> </tfoot> </table> </body> </html>

Reply With Quote

