Fwd: Fwd: Getting path in inode_permission

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Wed Feb 11 15:37:02 EST 2015

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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150211/b254cf22/attachment.bin 

More information about the Kernelnewbies mailing list