On Wed, Feb 11, 2015 at 4:29 AM, <[email protected]> wrote: > On Wed, 11 Feb 2015 03:42:50 +0530, noyb noybee said: > You missed the point. How does the process *securely* get the passphrase > that will be passed into the syscall? (Hint - a keystroke logger is only > the *start* of your problems. Think about why the kernel module signing > code uses public-key crypto instead of symmetric private keys...)
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. _______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
