I made a new release of the Chronicle blog compiler the other day, which seems to be getting a suprising number of downloads from my apt repository.
The apt repository will be updated shortly to drop support for Sarge, since in practise I've not uploaded new things there for a while.
In other news I made some new code for the Debian Administration website! The site now has the notion of a "read-only" state. This state forbids new articles from being posted, new votes being cast, and new comments being posted.
The read-only state is mostly designed for emergencies, and for admin work upon the host system (such as when I'm tweaking the newly installed search engine).
In more coding news I've been updating the xen-shell a little recently, so it will shortly have the ability to checksum the filesystem of Xen guests - and later validate them. This isn't a great security feature because it assumes you trust dom0 - and more importantly to checksum files your guest must be shutdown.
However as a small feature I believe the suggestion was an interesting one.
Finally I've been thinking about system exploitation via temporary file abuse. There are a couple of cases that are common:
- Creation of an arbitrary (writeable) file upon a host.
- Creation of an arbitrary (non-writable) file upon a host.
- Truncation of an existing file upon a host.
Exploiting the first to go from user to root access is trivial. But how would you exploit the last two?
Denial Of Service attacks are trivial via the creation/truncation of /etc/nologin, /etc/shadow, (or even /boot/grub/menu.lst! But gaining privileges? I can't quite see how.