Re: Fwd: Fwd: Getting path in inode_permission

On Thu, 12 Feb 2015 00:31:45 +0530, noyb noybee said:

I was planning that the calling process would call the new system call which would return a pseudo-random key that is used as the pass-phrase.

So what prevents malicious code from doing a fork and then calling the new syscall to get its own pseudo-random key to use as a passphrase? Like I said, this is a lot harder to make secure than it looks.