[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/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 - [Feature Request] Encrypt/hide a single file
Page 1 of 1

[Feature Request] Encrypt/hide a single file

PostPosted: Thu Jul 05, 2012 2:54 pm
by fmcypriano
Hi there,

I think it would be great if I have a way to encrypt/hide a single file. I'm suggesting it because I can't move this file.

My use case is this. I use Sparrow as my email client and on my job's Mac I want to encrypt my personal email accounts when I'm not at the office. Currently I can encrypt ~/Library/Application Support/Sparrow and this would hide Sparrow's data, theoretically. Upon testing I found out that Sparrow keeps the account list in a file (com.sparrowmailapp.sparrow.plist) inside ~/Library/Preferences so even with the Sparrow data "locked" when I open the app it recreates the emails because it access all the accounts.

The idea is to be able to hide this file when the ~/Library/Application Support/Sparrow is locked, so that it only have work related email accounts. This feature could be an option inside the Folder Info (the little "i" in Espionage's window) saying "hide these files when this folder is locked". When locked Espionage would put a file that was there before the lock, just like it does with folders.

Hope you guys like the idea. It would be awesome to me.

Re: [Feature Request] Encrypt/hide a single file

PostPosted: Fri Jul 06, 2012 3:25 pm
by zsolt
Hello, your request is pointing into "application association" direction, the feature Espionage 2 had. This feature is under review but there is not release and feature set defined yet.

Thanks for your input.

Zsolt

Re: [Feature Request] Encrypt/hide a single file

PostPosted: Fri Jul 06, 2012 3:31 pm
by fmcypriano
Deep down it point to de app association. But the suggestion does not require the spy and does one thing that app association didn't.

With app association Espionage asks for password to open the app. What this would do is allow the app to open but without my protected data. Another level of plausible deniability.

And Espionage wouldn't know about apps. I would be responsible to configure "single file associations outside the current folder" thing :)

Re: [Feature Request] Encrypt/hide a single file

PostPosted: Fri Jul 06, 2012 9:05 pm
by zsolt
Sure, but your approach is very application specific. But you are right about iSpyd...this is more about kind of setting a set of folders (and files) which should unlock and lock all together, whereas the files should be moved into a protected folder and back, depending on the folder state...all nice as a rough idea but once you go into details it must be simple otherwise you get tangled in all the possibilities... but we are listening :-)

Rgds
Zsolt

Re: [Feature Request] Encrypt/hide a single file

PostPosted: Mon Jul 09, 2012 8:29 pm
by fmcypriano
I hope you find a good solution :mrgreen: