Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Mobile Couchbase
Home
+ new post
About this group
Join this group
Message from discussion TouchDB-iOS security
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Sebastian  
View profile  
 More options Aug 14 2012, 2:32 pm
From: Sebastian <fwpban...@web.de>
Date: Tue, 14 Aug 2012 11:32:17 -0700 (PDT)
Local: Tues, Aug 14 2012 2:32 pm
Subject: Re: TouchDB-iOS security
Print | View thread | Show original | Report this message | Find messages by this author

I looked a little deeper into this topic. Yes, the files are by default
encrypted. The problem is that they are only encrypted with the device key
which can be retrieved from the device even when the device is locked. If
you apply the setting NSFileProtectionComplete the files are encrypted with
the device key and the unlock passphrase. This way if the device is lost
and locked an attacker cannot encrypt the files unless he has the unlock
passphrase. There is a similar setting for the kaychain.

Frauenhofer institute invested this and published there results:
http://sit.sit.fraunhofer.de/studies/en/sc-iphone-passwords.pdf
http://sit.sit.fraunhofer.de/studies/en/sc-iphone-passwords-faq.pdf


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google