
So I wrote a blog entry, clicked "Save" and was brought to the login screen as apparently the session had timed out (how are you supposed to write a blog entry in a few minutes?). Anyway, I tried going back, but that only brought me to the login page again. OK, nothing is lost yet, I thought, the text is probably still somewhere in your 1GB of RAM. Now, how does one grep through his RAM? Of course /proc/kcore - I successfully did it for exactly the same kind of situation before, but this time it said:
cat: /proc/kcore: Operation not permitted
But I am root! How can I not be permitted to read? The permissions on the file were fine, so I looked at the kernel source and there it was:
static int open_kcore(struct inode * inode, struct file * filp)
{
return -EPERM;
}
Great! That can only be the works of some distribution patches (I'm using Kubuntu Dapper) and so I looked at the vanilla kernel source and found:
static int open_kcore(struct inode * inode, struct file * filp)
{
return capable(CAP_SYS_RAWIO) ? 0 : -EPERM;
}
So much for getting back at my blog entry.
I tried grepping through /proc/kcore on the server where s9y runs (which runs Kubuntu Breezy and doesn't have the stupid patch), hoping to find the POST data that was sent to apache, but no success.
Now I lost a few hours of my life only because of too short timeouts, and a stupid patch... I better go back to learning now.
PS: Before hitting the "Save" button I will copy the whole text into the clipboard!