My gennerally approach is: 1) Download source 2) Uncompress file 3) ./configure 4) make 5) ./[name of binary] 6) Read documentation/source_code/other_stuff

Aside from the fact that that's a horrible habit, even following those steps, you couldn't have missed it.

Anyway, enough of this discussion. Let's talk about the actual keylogger -- Comments? Questions? Suggestions?

Just want to add first of all that I generally read the ReadMe first. --

Besides that, what do you (zx2c4) think of Linux? Do you think it's a safe platform?

I think it still has a long way to go. _Most_ programs require root access to install; and even ones that don't need root still have access to all user files. This is a but of problem.

Contrast this with iOS, where every app has local storage and one app cannot read another's files/data. On Linux & Android the problem of data security (among others) is persistent.

For some strange reason, zx2c4, the comment you made under mine is dead. (Try logging out and seeing if it's visible.)

I don't know if you've been banned. If you have, that would bee very strange. Why would someone do that? Were they pissed at the fact you shared potential dangerous code that could be used to infiltrate the OS run by many HNers?

Or you might have hit some sort of reply-depth. (Just guessing here.)

But that kills any hope of having an email client attach files made by other programs with the current implementation.