<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to SecurityConsiderations</title><link>https://sourceforge.net/p/uisdk/wiki/SecurityConsiderations/</link><description>Recent changes to SecurityConsiderations</description><atom:link href="https://sourceforge.net/p/uisdk/wiki/SecurityConsiderations/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 16 Jul 2013 23:22:54 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/uisdk/wiki/SecurityConsiderations/feed" rel="self" type="application/rss+xml"/><item><title>SecurityConsiderations modified by &lt;REDACTED&gt;</title><link>https://sourceforge.net/p/uisdk/wiki/SecurityConsiderations/</link><description>&lt;div class="markdown_content"&gt;&lt;h2 id="security-considerations"&gt;Security Considerations&lt;/h2&gt;
&lt;p&gt;Microsoft has spent many years working to make Internet Explorer a safe browser. As hacker find new vulnerabilities it becomes a never-ending challenge.&lt;/p&gt;
&lt;p&gt;While the UISDK can be used as an advanced browser, we strongly recommend against this: sites could, in theory, hold scripts that exploit the UISDK and gain access to the very windows API services that Microsoft has worked so hard to block.&lt;/p&gt;
&lt;p&gt;Instead, use the UISDK to load trusted scripts only -- either scripts packaged and installed alongside the UISDK, or scripts hosted on your own &lt;b&gt;secure&lt;/b&gt; web servers.&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;For maximum security:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Always turn off the browser bar within the application window.&lt;/li&gt;
&lt;li&gt;Disable the context menu so that users cannot "view source".&lt;/li&gt;
&lt;li&gt;Install all UISDK scripts and documents locally, unless the UISDK is being used as an install wizard.&lt;/li&gt;
&lt;li&gt;If being used as an install wizard, the starting URL in the exe resources.&lt;/li&gt;
&lt;li&gt;Set up the Safe DNS resource file to ensure only your URLs can be reached.&lt;/li&gt;
&lt;li&gt;Set up your own encryption key within the exe resources.&lt;/li&gt;
&lt;li&gt;Prevent access to the context menu.&lt;/li&gt;
&lt;li&gt;Encrypt your scripts and documents with your own key.&lt;/li&gt;
&lt;li&gt;When you have updated all the exe resources, digitally sign your executable with your own digital signature.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Tracking downloads/installs&lt;/p&gt;
&lt;p&gt;Tracking Ids, marketing campaign IDs, or activation keys can be "embedded" in your file by:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Sending alternative "download" filename information with the file.&lt;/li&gt;
&lt;li&gt;Parsing out that information in the client for subsequent operations. &lt;/li&gt;
&lt;li&gt;This works regardless of browser. see the simplified PHP example below&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;

    $campaignID = $this-&gt;getNextCampaignID(); //or get it from the HTTP GET params.. 
    header("Content-Type: application/octet-stream");
    header("Content-Disposition: attachment; filename=setup_" . $campaignID . ".exe");  
    header("Content-Length: " . filesize("./downloads/uisdk.exe"));         
    readfile("./downloads/uisdk.exe");  
&lt;/pre&gt;
&lt;/div&gt;</description><pubDate>Tue, 16 Jul 2013 23:22:54 -0000</pubDate><guid>https://sourceforge.net2789baa427784855cb2663351df08a0ebeaa6f0d</guid></item></channel></rss>