Greg, this is not an esoteric scenario, but a very common one: imagine the following common instances:
a) A network home directory (something that OS X Server currently supports), where a user can login with the same credentials from different client iMac-s and regardless of the machine, he gets this home folder mounted from the OS X Server (see http://www.apple.com/server/macosx/feat ... aring.html)
b) A folder on another Apple OS X computer that two or more people want to share
b1) Tax folder in your screen-shot: what is my wife, using her iMac, not mine, wants to look something up?
b2) Firm, project file on file server (let's say OS X Server) to be accessible only by some team-members (think of a law firm, or an accounting firm, for example)
These situations are very common and it would be great is Espionage could be improved to work under such scenarios.
Just laying out some ideas, why the encrypted container cannot be stored on the same drive (local or network drive) as the folder being accessed, and the locally installed Espionage (on the client OS X) would not just provide the logic to access it? Manually, these scenarios can be already achieved today using TrueCrypt containers (http://truecrypt.org). With my limited programming knowledge, perhaps all you would need to do would be to hook up the API calls to open a network folder (at least for the AFP protocol). I know that is easier being said than done, all I want to do is to stimulate the discussion.
Is this impossible to do technically, in your opinion?
Thank you
a) A network home directory (something that OS X Server currently supports), where a user can login with the same credentials from different client iMac-s and regardless of the machine, he gets this home folder mounted from the OS X Server (see http://www.apple.com/server/macosx/feat ... aring.html)
b) A folder on another Apple OS X computer that two or more people want to share
b1) Tax folder in your screen-shot: what is my wife, using her iMac, not mine, wants to look something up?
b2) Firm, project file on file server (let's say OS X Server) to be accessible only by some team-members (think of a law firm, or an accounting firm, for example)
These situations are very common and it would be great is Espionage could be improved to work under such scenarios.
Just laying out some ideas, why the encrypted container cannot be stored on the same drive (local or network drive) as the folder being accessed, and the locally installed Espionage (on the client OS X) would not just provide the logic to access it? Manually, these scenarios can be already achieved today using TrueCrypt containers (http://truecrypt.org). With my limited programming knowledge, perhaps all you would need to do would be to hook up the API calls to open a network folder (at least for the AFP protocol). I know that is easier being said than done, all I want to do is to stimulate the discussion.
Is this impossible to do technically, in your opinion?
Thank you