[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/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 - deny file-read-data on Espionage.keychain since Lion

deny file-read-data on Espionage.keychain since Lion

General discussion about Espionage 2.

deny file-read-data on Espionage.keychain since Lion

Postby nexus66 » Mon Aug 15, 2011 10:15 am

Dear all,

I'm getting thousands (several 10 per second) of log messages a day like:

WebProcess(6656) deny file-read-data /Users/<myuserid>/Library/Application Support/Espionage/Espionage.keychain

from sandboxd since I have upgraded to Lion. The espionage version is 2.8.13 .

Any ideas how to fix this?

Cheers, nexus66
nexus66
 
Posts: 3
Joined: Mon Aug 15, 2011 10:08 am

Re: deny file-read-data on Espionage.keychain since Lion

Postby marty » Mon Aug 15, 2011 4:08 pm

Welcome to the forums, nexus66!

What you are seeing is due to Safari 5.1's new "sandbox" isolation process. Something within the Safari environment is attempting to check your Espionage keychain (for some reason) and due to this sandboxing, those accesses are denied. We are looking into what component(s) are causing these access attempts. Hopefully we can find something that can be done to minimize or eliminate these messages.

It's important to note that it is not Espionage making these access, and that it is not any kind of "attack" on your Espionage passwords stored in the keychain. It is simply something that needs to be looked into further from our point of view so that you don't get scared by the message and that it doesn't get logged so often — if that's possible.

/Marty
Tao Effect Support

follow for news!
marty
Tao Effect Support
 
Posts: 27
Joined: Mon Feb 28, 2011 12:13 am

Re: deny file-read-data on Espionage.keychain since Lion

Postby nexus66 » Mon Aug 15, 2011 5:07 pm

Thanks a lot for the quick answer. I wasn't scared too much - just wanted to decrease the log pollution after the lion upgrade
and this is not the only frequent warning. Thanks a lot for your very nice tool!

Cheers,
nexus66
 
Posts: 3
Joined: Mon Aug 15, 2011 10:08 am

Re: deny file-read-data on Espionage.keychain since Lion

Postby mike » Mon Aug 15, 2011 8:35 pm

Follow on twitter for news!
mike
Tao Effect Support
 
Posts: 82
Joined: Tue Mar 01, 2011 6:51 pm

Re: deny file-read-data on Espionage.keychain since Lion

Postby nexus66 » Wed Aug 17, 2011 7:02 am

Thanks a lot again - this worked fine for me.

Cheers, nexus66
nexus66
 
Posts: 3
Joined: Mon Aug 15, 2011 10:08 am

Re: deny file-read-data on Espionage.keychain since Lion

Postby mike » Thu Aug 18, 2011 12:02 am

Thanks for the update, I'm glad that worked for you.

If we can be of further assistance, please let us know.
Follow on twitter for news!
mike
Tao Effect Support
 
Posts: 82
Joined: Tue Mar 01, 2011 6:51 pm


Return to Espionage 2

Who is online

Users browsing this forum: No registered users and 8 guests

cron