Hey guys!

I've been looking for a soultion for hiding my computer's TCP Fingerprint which
allows the others to determine whether what OS I'm using (Passive OS Fingerprinting, p0f), what's its uptime, etc.
I'm not talking about I want ONLY to block people who want to fingerprint me, or block the script kiddies or someone who uses nmap.
I want to somehow rewrite the package headers, so if I login to another server
they shouldn't be able to understand my fingerprint (e.g. using the p0f application: http://lcamtuf.coredump.cx/p0f.shtml).
Is there any solution for this problem (e.g. a kernel patch) under linux (2.4)?

Thanks
stringZ

A practical approach for defeating Nmap OS-Fingerprinting.

unSpawn: Thank you for your answer, but as I've told, it's not nmap what i wanna "defeat", but passive os fingerprinting (look at http://lcamtuf.coredump.cx/p0f.shtml). It's similar, but not exactly the same. Nmap can be fooled by a single grsecurity patch... but p0f not...

So you actually read the article and tried IP Personality against the p0f help page?

Since it's for 2,4,18 and I have 2.4.33 I won't be able to try it, but I understand what it wants me to do and I think it won't defeat p0f. Tell me if I'm wrong.

Still looking for solution...

Did you really read the document? and for example search for p0f inside?
If you want to do this sort of strange things (which are not out of consequence for performance or other things) then you should probably know how to apply a patch aimed at a version to another version, you have to correct the reject files so it should be possible (I'm not patronizing you, I just mean that you are doing some network kernel hacking then its not easy stuff and you have to understand what you do)
Btw, there are other private tools floating around and I'm not 100% sure you will defeat them.
What's the point to do this anyway?