<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Whisper Systems</title>
<link>http://www.whispersys.com/</link>
<description>Whisper Systems Updates</description>
<language>en-us</language>
<generator>Fingers</generator>
<ttl>5</ttl>


<item>
<title>TextSecure is now Open Source!</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
	We're excited to announce the open source release of TextSecure, our secure text messaging client for Android, 
	which Twitter acquired when we joined their team last month.
	&lt;br&gt;&lt;br&gt;
	We've always been interested in the ability for individuals and organizations to communicate freely and securely. 
	In the year and a half since Whisper Systems launched TextSecure, we've received an enormous amount of thanks, 
	feedback, and encouraging stories from users who have employed TextSecure towards those ends. We hope that as an 
	open source project, TextSecure will be able to reach even more people, with an even larger number of contributors 
	working to make it a great product.
	&lt;br&gt;&lt;br&gt;
	Those interested in the source can find it over on &lt;a href="https://github.com/WhisperSystems/TextSecure"&gt;GitHub&lt;/a&gt;.
	There is also a &lt;a href="https://lists.riseup.net/www/info/whispersystems"&gt;mailing list&lt;/a&gt; for those who have questions, 
	suggestions, or wish to get involved.
</description>
<pubDate>Tues, 30 Dec 2011 11:30 PDT</pubDate>
<guid>http://www.whispersys.com/31</guid>
</item>

<item>
<title>Whisper Systems Has Been Acquired By Twitter!</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
	&lt;p&gt;
	  &lt;b&gt;We're moving:&lt;/b&gt;&lt;br&gt;&lt;br&gt;
	  We started Whisper Systems with the goal of improving security and privacy for mobile devices.
	  We were attracted to this not only because we saw it as an opportunity to reinvent the security
	  solutions that never really worked in the PC environment to begin with, but also because the stakes are much higher 
	  &mdash; due to the nature of mobile devices themselves &mdash; and we didn't like the way that things were looking.
	  &lt;br&gt;&lt;br&gt;
	  We ended up tackling the full stack &mdash; all the way from application-level solutions at the top
	  of the stack, down through a &lt;a href="http://www.whispersys.com/whispercore.html"&gt;hardended version of Android&lt;/a&gt;, 
	  to &lt;a href="https://github.com/WhisperSystems/WhisperYAFFS/wiki"&gt;kernel modifications&lt;/a&gt; at the bottom of the 
	  stack.  Along the way we learned a lot, and developed products that we're proud of.
	  &lt;br&gt;&lt;br&gt;
	  Now that we have been acquired by &lt;a href="https://twitter.com"&gt;Twitter&lt;/a&gt;, we're looking forward
	  to integrating our technology and our expertise into Twitter's products and services.
	  &lt;br&gt;&lt;br&gt;
	  &lt;b&gt;The Transition:&lt;/b&gt;&lt;br&gt;&lt;br&gt;
	  The Whisper Systems software as our users know it will live on (and we have some surprises in store
	  that we're excited about), but there is unfortunately a transition period where we will have to temporarily take
	  our products and services offline. RedPhone service will be interrupted immediately, but FlashBack users 
	  have a month to pull off any backup data they would like before that service also goes offline.
	  &lt;br&gt;&lt;br&gt;
	  &lt;b&gt;Enormous Thanks:&lt;/b&gt;&lt;br&gt;&lt;br&gt;
	  Thanks to everyone who beta tested our software, sent us encouraging emails, filed thoughtful bug
	  reports, and in general kept us going with your enthusiasm and support.  We couldn't have done it 
	  without you, and we hope that we can continue to meet your expectations for software that helps provide
	  security and privacy.
	&lt;/p&gt;
</description>
<pubDate>Mon, 28 Nov 2011 08:30 PDT</pubDate>
<guid>http://www.whispersys.com/30</guid>
</item>

<item>
<title>FlashBack 0.3</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  Today we've released FlashBack 0.3, which adds support for statistics on
  the logical/phsyical storage space each device and individual snapshot is using.
  &lt;br&gt;&lt;br&gt;
  The new release is available in Android Market.
</description>
<pubDate>Mon, 03 Oct 2011 12:41 PDT</pubDate>
<guid>http://www.whispersys.com/29</guid>
</item>

<item>
<title>FlashBack 0.2</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  Today we've released FlashBack 0.2, which includes the ability to change your encryption passphrase, 
  change your account passphrase, rename devices, delete devices, delete all snapshots for a device,
  and delete your FlashBack account.
  &lt;br&gt;&lt;br&gt;
  The new release is available in Android Market.
</description>
<pubDate>Wed, 21 Sep 2011 10:00 PDT</pubDate>
<guid>http://www.whispersys.com/28</guid>
</item>

<item>
<title>WhisperCore 0.5.5</title>
<link>http://www.whispersys.com/whispercore.html</link>
<description>
  Last week, Whisper Systems responded to the 
  &lt;a href="http://googleonlinesecurity.blogspot.com/2011/08/update-on-attempted-man-in-middle.html"&gt;DigiNotar CA compromise&lt;/a&gt;
  by removing the DigiNotar root from the WhisperCore CA trust database, effectively revoking trust in DigiNotar.
  &lt;br&gt;&lt;br&gt;
  This week, a &lt;a href="http://www.rijksoverheid.nl/ministeries/bzk/documenten-en-publicaties/rapporten/2011/09/05/diginotar-public-report-version-1.html"&gt;report was released&lt;/a&gt; by the Dutch government, which indicates that the scope of the breach is worse than we originally
  anticipated.  In addition to the compromised DigiNotar root, it appears that DigiNotar had a number of intermediate CA certificates
  which were also compromised.  These intermediates (signed by "Staadt der Nederlanden," Entrust, and 
  CyberTrust) could potentially have been used to sign some unknown number of forged SSL site certificates.
  &lt;br&gt;&lt;br&gt;
  Intermediate CA certificates are not as straightforward to untrust. We can't simply remove them from a database, because they aren't
  in any databases. Instead, they chain back to roots which are good otherwise.  Firefox and Chrome have addressed this by baking these
  certificates directly into their browser binaries and explicitly making checks against them when setting up SSL connections.
  &lt;br&gt;&lt;br&gt;
  On your Android phone, however, there are many different apps that make SSL connections &mdash; all of which would have to bake
  these explicit certificate checks into their SSL setup logic. At Whisper Systems, we don't want to wait for app developers to make
  these changes, and they shouldn't have to.  So we've extended the Android framework to do it automatically.
  &lt;br&gt;&lt;br&gt;
  Now on WhisperCore, in addition to the trusted cacerts.bks store, we've created an additional untrusted.bks store, which contains
  certificates that are to be explicitly considered compromised, and which is currently populated with the DigiNotar 
  intermediate certificates.  If any application on the device initiates an SSL connection and receives a certificate chain with a 
  certificate from the untrusted.bks store anywhere in it (root, intermediate, or leaf), that SSL connection will be marked as invalid.
  &lt;br&gt;&lt;br&gt;
  We believe that WhisperCore currently represents the only Android SSL experience that fully protects users from the DigiNotar
  compromise.  Stock Android devices have not been updated at all, but even advanced users who have rooted their phones to modify
  the cacerts.bks file on non-WhisperCore devices are still not protected from these bad DigiNotar intermediate CA certs.
  &lt;br&gt;&lt;br&gt;
  As usual, WhisperCore users can quickly upgrade by using the "WhisperCore Updater" app.
</description>
<pubDate>Fri, 09 Sep 2011 10:00 PDT</pubDate>
<guid>http://www.whispersys.com/27</guid>
</item>

<item>
<title>WhisperCore 0.5.4</title>
<link>http://www.whispersys.com/whispercore.html</link>
<description>
  In response to the DigiNotar CA compromise,
  we've released &lt;a href="whispercore.html"&gt;WhisperCore 0.5.4&lt;/a&gt;, which removes the DigiNotar Root CA certificate from the
  trust store.
  &lt;br&gt;&lt;br&gt;
  As usual, WhisperCore users can quickly upgrade by using the "WhisperCore Updater" app.
</description>
<pubDate>Tue, 30 Aug 2011 15:52 PDT</pubDate>
<guid>http://www.whispersys.com/26</guid>
</item>

<item>
<title>WhisperCore 0.5.3</title>
<link>http://www.whispersys.com/whispercore.html</link>
<description>
  We released &lt;a href="whispercore.html"&gt;WhisperCore 0.5.3&lt;/a&gt; today, which features an upgrade 
  to Android 2.3.5, along with some bug fixes and stability improvements.
  &lt;br&gt;&lt;br&gt;
  As usual, WhisperCore users can upgrade by using the "WhisperCore Updater" app.
</description>
<pubDate>Mon, 29 Aug 2011 09:32 PDT</pubDate>
<guid>http://www.whispersys.com/24</guid>
</item>

<item>
<title>WhisperCore 0.5.2</title>
<link>http://www.whispersys.com/whispercore.html</link>
<description>
  We rolled out a few bug fixes over the weekend as &lt;a href="whispercore.html"&gt;WhisperCore 0.5.2&lt;/a&gt;.
  This addresses an issue some people were seeing with MMS messages, as well as a problem with APN
  configuration that was causing some users to lose their 3G data connections.
  &lt;br&gt;&lt;br&gt;
  If you installed WhisperCore 0.5 and are having problems with 3G data, after upgrading to WhisperCore 0.2,
  open Settings -&gt; Wireless And Networks -&gt; Mobile Networks -&gt; Access Point Names. There, click Menu -&gt; Reset 
  to default.  This should resolve your issues.
  &lt;br&gt;&lt;br&gt;
  As usual, WhisperCore users can upgrade by using the "WhisperCore Updater" app.
</description>
<pubDate>Wed, 27 Jun 2011 21:32 PDT</pubDate>
<guid>http://www.whispersys.com/23</guid>
</item>

<item>
<title>WhisperCore 0.5 and Selective Permissions</title>
<link>http://www.whispersys.com/whispercore.html</link>
<description>
  Today we've released &lt;a href="whispercore.html"&gt;WhisperCore 0.5&lt;/a&gt;, which features the ability to 
  &lt;a href="permissions.html"&gt;selectively revoke permissions an app has requested&lt;/a&gt;.  We think this 
  is an exciting development that will continue to give users and administrators more control over the 
  security of their data.
</description>
<pubDate>Wed, 22 Jun 2011 11:12 PDT</pubDate>
<guid>http://www.whispersys.com/22</guid>
</item>

<item>
<title>WhisperCore Platform SDK</title>
<link>http://www.whispersys.com/sdk.html</link>
<description>
  Today we released the &lt;a href="sdk.html"&gt;WhisperCore Platform SDK&lt;/a&gt;, which provides developers
  with access to capabilities specific to the WhisperCore platform.  While this initial SDK focuses
  on provider access to iptables settings, we will continue to make more WhisperCore features available
  to developers over time.
</description>
<pubDate>Tue, 7 Jun 2011 12:00 PDT</pubDate>
<guid>http://www.whispersys.com/21</guid>
</item>

<item>
<title>Smudge Attack Prevention Details</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  WhisperCore 0.4 includes &lt;a href="screenlock.html"&gt;smudge resistant screen unlock patterns&lt;/a&gt;,
  part of our efforts to help provide data security for Android devices
</description>
<pubDate>Wed, 1 Jun 2011 11:85:00 PDT</pubDate>
<guid>http://www.whispersys.com/20</guid>
</item>

<item>
<title>WhisperCore 0.4 and Flashback</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
	  We released WhisperCore 0.4 today, which includes &lt;a href="flashback.html"&gt;Flashback&lt;/a&gt;, a new product
	  that provides secure snapshot-based backups for your device.  We're pretty excited about it, so check
	  it out!
	  &lt;br&gt;&lt;br&gt;
	  You can download &lt;a href="whispercore.html"&gt;WhisperCore here&lt;/a&gt;, or existing
	  WhisperCore users can click "Check for updates" in the updater tool.
	  &lt;br&gt;&lt;br&gt;
	  Additionally, this version of WhisperCore includes:
	  &lt;ul&gt;
	    &lt;li&gt;New anti-greasetrail screen unlock patterns (we'll post more about this soon).&lt;/li&gt;
	    &lt;li&gt;An upgrade to Android 2.3.4.&lt;/li&gt;
	    &lt;li&gt;Upgraded 2.6.35 kernel support.&lt;/li&gt;
	  &lt;/ul&gt;
</description>
<pubDate>Wed, 1 Jun 2011 07:00:00 PDT</pubDate>
<guid>http://www.whispersys.com/19</guid>
</item>

<item>
<title>RedPhone 0.4.3 and International Support</title>
<link>http://www.whispersys.com/updates.html</link>
<description>  
  RedPhone 0.4.3 is now available in Android Market.  This release, at long last, supports international calling.  In addition
  to our existing international support in Egypt, we're also rolling out support for Canada and Spain today.  Users in those
  countries can now download RedPhone from Android Market, and if everything goes well, we'll continue adding support for more 
  countries throughout the week.
</description>
<pubDate>Tues, 15 Mar 2011 18:59:00 PDT</pubDate>
<guid>http://www.whispersys.com/18</guid>
</item>

<item>
<title>WhisperCore 0.1 Released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>  
  We've released &lt;a href="whispercore.html"&gt;WhisperCore 0.1&lt;/a&gt;.  Device and data security for Android, and
  the first iteration of a platform-level security project.
</description>
<pubDate>Tues, 15 Mar 2011 11:00:00 PDT</pubDate>
<guid>http://www.whispersys.com/17</guid>
</item>

<item>
<title>TextSecure 0.5.6 Released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>  
  TextSecure 0.5.6 addresses two bugs.
  &lt;ul&gt;
    &lt;li&gt;We've fixed a bug that was causing session fingerprints not to match in some scenarios.
    &lt;li&gt;Fixed a bug that was causing TextSecure to crash in some cases where one party in a secure session did not have an identity key.
  &lt;/ul&gt;
</description>
<pubDate>Mon, 03 Mar 2011 17:39:00 PDT</pubDate>
<guid>http://www.whispersys.com/16</guid>
</item>

<item>
<title>RedPhone 0.4 Released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  RedPhone 0.4.1 is a maintenance release.
  &lt;ul&gt;
    &lt;li&gt;We've fixed a bug that was intermittently causing a deadlock on initiating connections.&lt;br&gt;&lt;br&gt;
    &lt;li&gt;We've introduced some new latency peak detection heuristics to help with call quality.&lt;br&gt;&lt;br&gt;
  &lt;/ul&gt;
</description>
<pubDate>Mon, 03 Mar 2011 17:39:00 PDT</pubDate>
<guid>http://www.whispersys.com/15</guid>
</item>


<item>
<title>RedPhone 0.4 Released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  RedPhone 0.4 introduces several new features and improvements:
  &lt;ul&gt;
    &lt;li&gt;We've added audio alerts that play during call setup to indicate progress towards a
      completed call.  These sounds correspond to the alert messages already
      displayed on-screen, but allow you to keep the phone to your ear while the
      call connects.&lt;br&gt;&lt;br&gt;
    &lt;li&gt;We've improved handling of periodic brief network data
      droupouts that occur on some networks, which should make these interruptions
      as unintrusive as possible.&lt;br&gt;&lt;br&gt;
    &lt;li&gt;For those of you who wish to experiment with alternate signaling methods,
      we've added an option, which you can select in the main options
      menu, to use Google's C2DM ("push") service as a replacement 
      for the standard SMS signalling mechanism.
      &lt;br&gt;&lt;br&gt;
      Note, however, that while C2DM can sometimes be faster than SMS, in the case
      when your phone has been asleep for a while, it can take much longer to complete 
      a connection than with the SMS based signalling.  &lt;br&gt;&lt;br&gt;
    &lt;li&gt;Finally, we've made two improvements to the dialing process.  
      First, when you make a regular call, we present the option to
      upgrade that call to RedPhone &mdash; but only if the person you're calling also has
      RedPhone installed on their device.  
      &lt;br&gt;&lt;br&gt;
      Second, we've improved the look and feel of our dialer, making it easier to find contacts quickly.
</description>
<pubDate>Mon, 07 Feb 2011 17:50:00 PDT</pubDate>
<guid>http://www.whispersys.com/14</guid>
</item>

<item>
<title>TextSecure 0.5.5 Released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  TextSecure 0.5.5 is now available in Android Market.  This release primarily improves
  the key exchange process, which no longer requires any user interaction once a key exchange
  has been initiated.  It also includes a number of small bug fixes.
</description>
<pubDate>Wed, 12 Jan 2011 14:18:00 PDT</pubDate>
<guid>http://www.whispersys.com/13</guid>
</item>

<item>
<title>TextSecure 0.5.4 Released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  TextSecure 0.5.4 is now available in Android Market.  
  This release fixes an issue with Sprint Visual Voicemail on Sprint phones. 
  Visual voicemail should now work with TextSecure installed.
</description>
<pubDate>Wed, 05 Jan 2010 18:43:00 PDT</pubDate>
<guid>http://www.whispersys.com/12</guid>
</item>


<item>
<title>RedPhone 0.3 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  RedPhone 0.3 is now available in Android Market. This release focuses on improvements to call 
  audio quality.  It features a complete re-write of the jitter buffer and packet loss
  concealment code to better handle the burst-mode characteristics of 3G
  networks when signal strength drops.  New options, available from the
  settings menu, allow users to force a 'minimum latency' mode, which
  will degrade audio quality while improving latency, and a 'single
  thread' mode, which improves performance on some phones.  We recommend
  disabling these options unless you encounter difficulties.
  &lt;br&gt;&lt;br&gt;
  When starting a new call, RedPhone may take a few seconds to adjust
  its internal settings to the characteristics of your network
  connection - if audio quality does not improve within 5-10 seconds,
  try moving to an area with better reception or using WiFi.  Users
  should also note that due to asymmetric broadcast power when using 3G,
  downlink audio can sound fine, while uplink audio is noticeably
  choppy.  If this situation occurs, it indicates that your device is
  unable to send packets to the cellular tower reliably.  The problem
  can be resolved by moving to an area with better reception.
</description>
<pubDate>Tues, 30 Nov 2010 15:24:00 PDT</pubDate>
<guid>http://www.whispersys.com/11</guid>
</item>

<item>
<title>TextSecure 0.5.2 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  TextSecure 0.5.2 is now available in Android Market.  Changes:
  &lt;ul&gt;
    &lt;li&gt;When composing a new message, you can now select recipients by a multi-select list of contacts,
      a multi-select list of contact groups, and a multi-select list of recent incoming/ougoing calls.
    &lt;li&gt;The identity key options have been moved from the main menu into the settings.
    &lt;li&gt;Added message "forward" and "cleartext send" options.
    &lt;li&gt;Added batch mode operations for the thread list.
  &lt;/ul&gt;	  
</description>
<pubDate>Mon, 22 Nov 2010 22:11:00 PDT</pubDate>
<guid>http://www.whispersys.com/10</guid>
</item>

<item>
<title>RedPhone 0.2 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  RedPhone 0.2 is now available in Android Market.  Changes:
  &lt;ul&gt;
    &lt;li&gt;&lt;b&gt;Audio Quality&lt;/b&gt; : Users should experience significant audio quality improvements, particularly on mobile 3G networks.
    &lt;li&gt;&lt;b&gt;Reduced Echo&lt;/b&gt; : Some devices will experience reduced echo.
    &lt;li&gt;&lt;b&gt;Device Support&lt;/b&gt; : RedPhone should now be compatible with more devices, particularly some Samsung models which have
       been troublesome in the past.
    &lt;li&gt;&lt;b&gt;Dialer Integration&lt;/b&gt; : You can now use the normal dialer in order to make calls.
  &lt;/ul&gt;
</description>
<pubDate>Thu, 21 Oct 2010 15:53:00 PDT</pubDate>
<guid>http://www.whispersys.com/9</guid>
</item>


<item>
<title>TextSecure 0.5 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
	TextSecure 0.5 is now available in Android Market.  Changes:

	  &lt;ul&gt;
	    &lt;li&gt;&lt;b&gt;Identity Keys&lt;/b&gt; : TextSecure now supports the concept of an "identity key." These are keys that are only
	      used for signing, but never used for encrypting.  The key exchanges at the beginning of a session can be signed
	      with these identity keys, allowing you to verify an identity fingerprint once and automatically trust all subsequent
	      session initiations signed by the same key afterwards.  This can be very useful if you're changing SIM cards frequently,
	      or otherwise tearing down and re-initiating sessions on a regular basis.
	    &lt;li&gt;&lt;b&gt;Advanced Passphrase Caching And Management&lt;/b&gt; : TextSecure is now much smarter about caching your passphrase,
	      such that it will no longer be randomly knocked out of memory when using other applications.  Additionally, you can
	      now explicitly define a timeout for how long you would like your passphrase to stay cached while you're not using TextSecure.
	      If you thought you had to enter your passphrase too often before, this release is for you.  If you thought you didn't have
	      to enter your passphrase often enough before, this release is also for you.
	    &lt;li&gt;&lt;b&gt;QR Code Validation&lt;/b&gt; : TextSecure now supports using visual QR codes for validating session and identity keys. If you
	      do a key exchange with someone who's physically present, you can simply scan each-other's screens in order to validate the
	      session or their identity key.
	    &lt;li&gt;&lt;b&gt;Thread Search&lt;/b&gt; : TextSecure now supports searching for a thread in the main thread-list screen. Simply select "search"
	      under the menu options, or if you have a phone with a hard keyboard, simply start typing while in the main thread-list view.
	    &lt;li&gt;&lt;b&gt;Identity Selection&lt;/b&gt; : TextSecure now allows you to explicitly select a contact from the contacts list which represents
	      your "identity."  It will use this photo from this contact as the photo to display in conversation threads, and you can export
	      your identity key to be stored in this contact and shared out via other mechanisms.
	    &lt;li&gt;&lt;b&gt;Bug Fixes&lt;/b&gt; : You can now copy the text from MMS messages to the clipboard, contact selection from the compose view on
	      Android 2.x devices works more reliably, and clicking "Send" from the soft keyboard on a device in landscape mode now actually
	      sends.
	    &lt;li&gt;&lt;b&gt;Speedups&lt;/b&gt; : TextSecure has been optimized to be a little zippier than before on slower devices.
	  &lt;/ul&gt;
</description>
<pubDate>Thu, 21 Oct 2010 14:53:00 PDT</pubDate>
<guid>http://www.whispersys.com/9</guid>
</item>

<item>
<title>TextSecure 0.4.3 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
	TextSecure 0.4.3 is now available in Android Market.  Changes:
	  &lt;ul&gt;
	    &lt;li&gt;&lt;i&gt;Always Locally Encrypt&lt;/i&gt; : Previous versions of TextSecure wouldn't locally encrypt received messages
	      if the passphrase wasn't in memory.  This change always locally encrypts messages, even if the passphrase
	      has fallen out of memory.
	    &lt;li&gt;&lt;i&gt;MMS Bug Fixes&lt;/i&gt; : Fixes for assorted bugs including: crashing on receiving MMS messages without
	      a "from" field, crashing on receiving MMS messages with an empty "part", and crashing on receiving MMS 
	      with certain types of audio.
	  &lt;/ul&gt;
</description>
<pubDate>Thu, 23 Sep 2010 13:27:00 PDT</pubDate>
<guid>http://www.whispersys.com/8</guid>
</item>

<item>
<title>TextSecure 0.4 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  TextSecure 0.4 is now available in Android Market.  This release fixes a bug where disabling MMS support
  was not effective, adds support for (optional) contact photo icons in the thread list and conversation views,
  fixes a bug where contact names were not correctly resolving on some phones, adds support for import/export
  of messages/keys/preferences, and adds support for saving MMS media to the gallery of the device.
</description>
<pubDate>Mon, 06 Sep 2010 11:54:00 PDT</pubDate>
<guid>http://www.whispersys.com/7</guid>
</item>

<item>
<title>TextSecure 0.3.3 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  TextSecure 0.3.3 is now available in Android Market.  This release fixes a bug where TextSecure would not 
  intercept key exchange messages when it wasn't in "use for all SMS messages" mode.  It also adds support for
  light/dark themes, as well as the ability to customize the notification LED blink color and pattern.
</description>
<pubDate>Wed, 21 Jul 2010 11:28:00 EST</pubDate>
<guid>http://www.whispersys.com/6</guid>
</item>

<item>
<title>TextSecure 0.3.2 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
  A minor release of TextSecure 0.3.2 is now available in Android Market.  This release fixes some bugs with
  MMS support, as well as a bug that occasionally prevented you from returning to the thread list.
</description>
<pubDate>Sun, 18 Jul 2010 17:24:00 EST</pubDate>
<guid>http://www.whispersys.com/5</guid>
</item>

<item>
<title>TextSecure 0.3 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
TextSecure 0.3 is now out.  This release incorporates a number of features that people have been asking for.
	  The big changes are:
	  &lt;ol&gt;
	    &lt;li&gt;&lt;i&gt;MMS Support&lt;/i&gt; : TextSecure now supports MMS messages on Android 2.0+ platforms, and allows them
	      to fall through to the system's default Messaging application on Android 1.6.
	    &lt;li&gt;&lt;i&gt;Encrypted MMS Support&lt;/i&gt; : TextSecure users can now also exchange encrypted MMS messages. These are
	      encrypted with the normal OTR-dervied protocol that TextSecure uses for all SMS traffic, providing both
	      secrecy as well as forward security.
	    &lt;li&gt;&lt;i&gt;Separate Database Support&lt;/i&gt; : TextSecure now stores all its messages in a database that is separate
	      from the system's default Messaging application.  On install, TextSecure gives you the option of importing
	      all your messages from the system database into the TextSecure database.  Additionally, you can configure
	      TextSecure to handle all SMS/MMS messages, all SMS messages, or just encrypted SMS/MMS messages. So while
	      we recommend using TextSecure for everything, if you'd like to use the system's default Messaging application 
	      for all of your normal SMS/MMS traffic and only use TextSecure for encrypted traffic, that option is now
	      available.
	  &lt;/ol&gt;
	  &lt;br&gt;&lt;br&gt;
	  Thanks to everyone who has continued submitting bug reports, suggestions, and comments.  Please keep the feedback
	  coming.
</description>
<pubDate>Tue, 31 May 2010 13:12:00 EST</pubDate>
<guid>http://www.whispersys.com/4</guid>
</item>


<item>
<title>TextSecure 0.2 released</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
We've released TextSecure 0.2, which includes a number of bug fixes and enhancements.  Most notably, the 0.2
release fixes the Verizon problems with both out-of-order timestamps and multipart (long) encrypted messages.
Based on user feedback, we've also improved the notification system to be less annoying, added the long-click
features that you're used to with the stock messaging app, fixed some international number issues, and added an
option to change your local encryption passphrase.  We've also made some changes that should allow the decrypt
process to be quicker and more reliable.
Thanks to everyone who has submitted comments, suggestions, and reports on TextSecure thus far.  They really help
as we try to get this stable and production ready.
</description>
<pubDate>Tue, 31 May 2010 13:12:00 EST</pubDate>
<guid>http://www.whispersys.com/3</guid>
</item>

<item>
<title>RedPhone updated to fix Droid and GoogleVoice problems</title>
<link>http://www.whispersys.com/updates.html</link>
<description>
We've gotten a lot of good feedback on RedPhone and TextSecure so far.  The biggest problems we've had have been
with Motorola Droid and GoogleVoice compatibility.  Users with a Droid phone have not been able to receive calls,
and users with GoogleVoice setup to relay their text messages have not been able to register or receive calls.
We've released RedPhone version 0.1.2 to the Android Market which should fix these problems.  Droid compatibility
with TextSecure multipart text messages remains a problem that we will be fixing soon.
</description>
<pubDate>Tue, 26 May 2010 21:29:00 EST</pubDate>
<guid>http://www.whispersys.com/2</guid>
</item>

<item>
<title>Announcing the public beta</title>
<link>http://www.whispersys.com/updates.html</link>
<description>Today we are opening the Whisper Systems mobile security suite up for a public beta.  Please download RedPhone and TextSecure, try them out, and let us know how they work.</description>
<pubDate>Tue, 25 May 2010 15:00:00 EST</pubDate>
<guid>http://www.whispersys.com/1</guid>
</item>

</channel>
</rss>

