<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dropbox on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/dropbox/</link>
    <description>Recent content in Dropbox on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 03 Oct 2011 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/dropbox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Broken Trust, Part 2: Applying the Approach to… Dropbox</title>
      <link>https://insinuator.net/2011/10/broken-trust-part-2-applying-the-approach-to-dropbox/</link>
      <pubDate>Mon, 03 Oct 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/10/broken-trust-part-2-applying-the-approach-to-dropbox/</guid>
      <description>&lt;p&gt;After having introduced the basic elements of our concept of trust, control and confidence in &lt;a href=&#34;http://www.insinuator.net/2011/06/broken-trust-part-1-definitions-fundamentals-some-more-reflections-on-rsa/&#34;&gt;this&lt;/a&gt; post, today I’ll try to strengthen your (and maybe even my own as well ;-)) understanding of these ideas by applying them to another candidate, that is Dropbox. Hence this post is mainly about performing a certain analysis method to some object; conclusions as for the question if Dropbox is suited to be used in enterprise environments processing sensitive data are out of scope and are left entirely to you, the valued reader.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
