logic involved

SELinux is coming to Android. Called SEAndroid, the project looks pretty interesting:

Some distinctive features of our SE Android reference implementation in comparison to prior efforts of which we are aware include:

• Per-file security labeling support for yaffs2,
• Filesystem images (yaffs2 and ext4) labeled at build time,
• Kernel permission checks controlling Binder IPC,
• Labeling of service sockets and socket files created by init,
• Labeling of device nodes created by ueventd,
• Flexible, configurable labeling of apps and app data directories,
• Userspace permission checks controlling use of the Zygote socket commands,
• Minimal port of SELinux userspace,
• SELinux support for the Android toolbox,
• Small TE policy written from scratch for Android,
• Confined domains for system services and apps,
• Use of MLS categories to isolate apps.

I just noticed this while getting the latest version of Boost from sf.net:

Or as Scott Hanselman put it: “It’s over and 7zip won”.

The JVM Serialisers project provides a very extensive comparison of dozens of different JVM serializers out there. Tested tools include several JSON libs, different XML related libs, Scala, protobuf, protostuf, msgpack and many more.
I didn’t know protostuff before – it seems to be really amazing!

(via tutego)

If you are looking for a really simple, free and portable ftp server for Windows, then visit StahlWorks.com and get their excellent Swiss File Knife. It’s a single, small executable with no dependencies that brings a ton of features. If you have it, just run …

sfk ftpserv -rw

… and enjoy your zero-install, ultra-portable ftp server!

Plesk ships Atmail, but the default installation has a minor problem: when you open your webmail site, all you get is a message box saying “Unable to get webmail password!”. This is not caused by the user, who might have entered wrong credentials (in fact, he hasn’t even seen the webmail page yet, let alone entered his password). It’s caused by Atmail being unable to connect to its MySQL database.
The origin of this problem is in /var/www/atmail/libs/Atmail/Config.php, line 4:

fopen("/etc/psa-webmail/atmail/.atmail.shadow")

For some reason, the fopen() call fails, but there are several ways of fixing this. The easiest is to get the database password from .atmail.shadow and hard-code it in Config.php.

Disclaimer: don’t do this if you don’t know exactly what you are doing, why you are doing it and which possible consequences might result.

Now, change your /var/www/atmail/libs/Atmail/Config.php like this:

//if (!($fd = fopen("/etc/psa-webmail/atmail/.atmail.shadow", "r"))) {
//  echo "<script>alert('Unable to get webmail password!')</script>";
//  exit();
//}
//fscanf($fd, "%s", $buff);
//fclose($fd);
$buff = 'MySQL_password';

Note that you changed an Atmail application file, and it is very likely to be reverted by the next Plesk/Atmail update. This patch will be very helpful in that situation.