[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4668: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4670: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4671: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4672: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
Tao Effect Forums • View topic - "Tight" security question with Espionage in "all Mac OS mode

"Tight" security question with Espionage in "all Mac OS mode

General discussion about Espionage 2.

"Tight" security question with Espionage in "all Mac OS mode

Postby Jezza » Sat Nov 19, 2011 5:31 am

I am just trialling Espionage and so far, it looks promising.

But I have the following questions / required clarifications after having looked up a few forum posts. Basically my aim is that specific data on my hard drive (and then copied onto a backup location - external HDD or offline/cloud storage) is unaccessible to anybody else than me.

If I understand correctly, encrypted folders use the standard/native Mac OS encryption with sparse images/bundles "wrapped in a clever way" that allows Espionage to do its magic such as application data locking, auto-unlock, white-listing, etc.

1- I read on the forum that this means data on the hard drive is always encrypted (it only gets mounted as a volume and decrypted on the fly and stored in RAM when unlocked - but the actual HDD data is unlocked). Is this correct?

2- Does that mean that if I have many large encrypted folders - all unlocked, this will greatly increase RAM usage (to hold all this decrypted data)?

3- I understand that there are lots of requests for timed or screensaver/sleep-triggered auto-locks (many messages from 2010 in forum) but this does not seem to have been implemented (yet?) as I could not see any mention of it in the app or help file. I understand the complexities of it (if a document from an encrypted folder is open, etc.) and the usual answer seems to be "to enable the sleep/screensaver password in the Security System Preferences" (which I already do). I completely understand the rationale behind this: if a thief resets my user password to be able to login (will need to log off/restart) or access the HDD from another machine, they wont be able to access my RAM, which is where the decrypted information resides.
However my question is with regards to the sleepimage file, which - as I understand - contains a dump of the RAM to disk. Does this mean that the Espionage-protected data (all unlocked folders) will implicitly be dumped in its RAM-DEcrypted state to disk as part of the overall RAM dump/copy?

4- If the above is true. Is it sufficient to set the Security System Preference "Use Secure Virtual Memory" to true to be protected (i.e. the unlocked Espionage folders will be dumped in their decrypted state as part of the overall RAM, which is in turn fully encrypted somehow by Mac OS)?

5- In terms of backup, there should not be any of the problems above: if I keep to the recommendation of either using the built-in backups or ensure that the folders are locked when running the backup, only the encrypted data should be copied?

Thanks in advance (and sorry for the long message!)

Jezza
Jezza
 
Posts: 5
Joined: Sat Nov 19, 2011 4:50 am

Re: "Tight" security question with Espionage in "all Mac OS

Postby greg » Sat Nov 19, 2011 9:09 pm

Follow for news!
greg
Tao Effect Support
 
Posts: 564
Joined: Thu Apr 02, 2009 3:14 am
Location: Tao Effect

Re: "Tight" security question with Espionage in "all Mac OS

Postby Jezza » Sun Nov 20, 2011 6:19 am

Jezza
 
Posts: 5
Joined: Sat Nov 19, 2011 4:50 am

Re: "Tight" security question with Espionage in "all Mac OS

Postby greg » Sun Nov 20, 2011 3:53 pm

Follow for news!
greg
Tao Effect Support
 
Posts: 564
Joined: Thu Apr 02, 2009 3:14 am
Location: Tao Effect


Return to Espionage 2

Who is online

Users browsing this forum: No registered users and 6 guests

cron