From what I understand of how Espionage should work, if an application attempts to access a file within a controlled folder, the password prompt should be displayed if the folder is locked.
What I see however is that the file access results in a "no such file" type error. The simplest case I've seen:
The controlled folder is '/Users/abc/protected'
The folder contains a directory 'test'.
From terminal window:
% ls protected/test # No password prompt from espionage
ls: protected/test: No such file or directory
# results in "No such file or directory" error
% ls protected # password prompt displays as expected - command is paused pending completion
test
%
Is this operating as designed? What I'd expect is for the request to open 'protected/test' to trigger the espionage unlock of the protected folder.
I'm on OSX 10.6.8 with Espionage 2.8.13
What I see however is that the file access results in a "no such file" type error. The simplest case I've seen:
The controlled folder is '/Users/abc/protected'
The folder contains a directory 'test'.
From terminal window:
% ls protected/test # No password prompt from espionage
ls: protected/test: No such file or directory
# results in "No such file or directory" error
% ls protected # password prompt displays as expected - command is paused pending completion
test
%
Is this operating as designed? What I'd expect is for the request to open 'protected/test' to trigger the espionage unlock of the protected folder.
I'm on OSX 10.6.8 with Espionage 2.8.13