Update: Based on an email I received, I've updated this post with more relevant information regarding setting up SAVDI with amavisd-new.

I recently migrated to using Postfix with amavisd-new on Ubuntu Linux, and was looking at integrating Sophos AntiVirus with amavisd-new. amavisd-new shipping with the LTS release of Ubuntu is 2.6.5, which does not include SPPP functionality for communicating with savdi so you must use Sophie protocol.

The following components were used for setting up this functionality with amavisd-new from MySophos Download & Updates:

• Sophos Anti-Virus for Linux v9.1
• SAV Dynamic Interface 2.2 Linux 32-bit

This post is assuming that you have setup amavisd-new on your system, and have it integrated with Postfix or equivalent MTA already.

savdid.conf:

channel {
commprotocol {
type: UNIX
socket: /var/run/savdid/savdid.sock
user: amavis
group: amavis
requesttimeout: 120
sendtimeout: 2
recvtimeout: 5
}

scanprotocol {
type: SOPHIE
allowscandir: SUBDIR
maxscandata: 500000
maxmemorysize: 250000
tmpfilestub: /tmp/savid_tmp
}

scanner {
type: SAVI
inprocess: YES
maxscantime: 3
maxrequesttime: 10
deny: /dev
deny: /home
savigrp: GrpArchiveUnpack 0
savigrp: GrpInternet 1
savists: Xml 1
}
}

This should permit amavisd-new to communicate with the SAVDID interface. Don't forget to create the appropriate init.d script to start savdid on boot and make sure to create the /var/run/savdid directory – as Debian/Ubuntu clean /var/run on system startup. Please download the init script from here and place it in /etc/init.d/savdid with an executable bit.

amavis communicates with SAVI using the Sophie protocol, to enable this support in amavis-new edit /etc/amavis/conf.d/15-av_scanners and add the following lines:

  ['Sophie',
    \&ask_daemon, ["{}/\n", '/var/run/savdid/savdid.sock'],
    qr/(?x)^ 0+ ( : | [\000\r\n]* $)/m,  qr/(?x)^ 1 ( : | [\000\r\n]* $)/m,
    qr/(?x)^ [-+]? \d+ : (.*?) [\000\r\n]* $/m ],

Please be aware that the socket line is being pointed at the place where we have SAVI listening for connections, based on our previous post.

If you have an ejabberd deployment, and you use Trillian and try to sign in on multiple devices you may notice that you are disconnected on one of the Android devices (usually the oldest) when the other device signs in. As one of the benefits of Trillian is to be able to use chat on multiple devices and have messages sync, this is annoying and defeats the purpose of Trillian.

The reason that Trillian has this behaviour with Jabber/XMPP is because the Resource name on all devices is the same ("Android" by default, or configurable statically.) ejabberd will disconnect the old connection with the same resource name.

In 2.1.9 release of ejabberd, a new configuration/behaviour was added to handle duplicate resources names called resource_conflict. The new behaviour will permit a second connection with the same name to be assigned a random resource name allowing both devices to stay connected.

To enable this functionality, add the following stanza to your /etc/ejabberd/ejabberd.cfg (or equivalent location):

{resource_conflict, setresource}.

Then restart ejabbered, or reload the configuration via ejabberdctl. This should resolve the issue with resource name conflicts, and allow you to use ejabberd with Trillian to provide a seamless mobile experience!

Update on March 26th, 2011: Actiontec has put the files for V1000H back on their Open Source Download Area. The files are now missing the Broadcom userspace/private directory, and will not provide you with a working open source build out-of-the-box (missing a lot of userspace binary blobs.) The last known good release for the V1000H is 2011/01/18. Please note that this new release will cause your device to be put into an irreparable state if you flash it.

Update on September 24th, 2011: Actiontec has once again removed the open source downloads for a number of their products on their Open Source Download Area site. I have decided to republish the tarballs of the source in response to this action.

Actiontec has removed all traces of releases for the Actiontec V1000H, R1000H, and Q1000 from their Open Source Download Area. These routers are running Broadcom 96368VVW reference design which uses Linux and BusyBox, and thus under the terms of GPL the source code must be released. I e-mailed the group in charge of Open Source compliance at Actiontec, and received the following response:

We are in the middle of revamping all of those codes and until our engineering department is done they have asked that we take the old ones down. Sorry for any trouble this has cause. I do not have an ETA on when I will have them back up there. I can only suggest that you keep checking back periodically.

I have an archive of most files that Actiontec has released based around the BCM96368 reference platform, and have posted them below. This issue adds onto my already growing list of issues with Actiontec, such as posting source code that doesn't work on the device, or is missing critical drivers (eg. Ethernet, HPNA.) The reason for multiple releases with the same filename and version is that Actiontec re-releases files under the same name with changed content.

It has also come to my attention that the releases for these products have also been removed from the Qwest GPL Download site. TELUS, which also distributes the Actiontec V1000H does not make an offer available for source code under terms of the GPL.

Please view the README authored by Actiontec for more information on how to build and flash the open source release.

An update to my The state of Android phones in relation to hackability post the other day. I guess I have to take back my views on HTC!

HTC has decided to start locking down their boot loaders with signed images with the release of the HTC Incredible S. This is garbage, and goes against the very spirit of Android. What happens when HTC decides to stop releasing updates for the phone, does this mean I am out of luck and have to be stuck with an old version of Android only 6 months after buying the phone? (As was the case with my HTC Legend if CyanogenMod hadn't released an updated Android.)

I don't know what Android phone I should be buying next time I get a phone? Looks like I'll be stuck buying the stock Google experience phones like the Nexus One and the Nexus S.