<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On UNIX and similar systems, files can exist in the filesystem without a filename (specifically known as a "link") pointing to them, as long as those files are held open by a process.</div><div><br></div><div>Usually this happens when a program opens a temporary file in /tmp or /var/tmp and then deletes (unlinks) it. The program can continue to use the file, and then when the file is closed, it completely disappears.</div><div><br></div><div>As you mention, it can also be useful for a process that wants to hide its data from the admin. However, if the process is killed or dies, whatever data that was in that file will be lost because the operating system will reclaim its inode…</div><div><br></div><div>Fun stuff!</div><div><br></div><div>Guy</div><br><div><div>On Oct 12, 2011, at 5:25 PM, Kenneth Younger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><a href="http://danielmiessler.com/study/lsof/">http://danielmiessler.com/study/lsof/</a><br><br>I was reading through this very interesting post about `lsof` and one of the last items he mentioned was `lsof +L1`. The author said this about it:<br>
<br>"lsof +L1 shows you all open files that have a link count less than 1, often indicative of a cracker trying to hide something"<br><br>So (of course) I tried running it myself, and found that I had quite a few results. I tried reading through the man page of lsof, but I'm still not understanding what the "link count" is, and specifically why it matters and/or could be an indicator of malicious activity.<br>
<br>Thoughts?<br><br>Thanks,<br>-Kenny<br>
_______________________________________________<br>Cialug mailing list<br><a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>http://cialug.org/mailman/listinfo/cialug<br></blockquote></div><br>
<br><BR>
<HR>
<i>This message has been scanned by ComplianceSafe, powered by Palisade's PacketSure.</i>
<br></body></html>