Search Results: "ag"

15 November 2006

MJ Ray: Business: Email, sigs and signing

Ian Rawlings wrote in an article in uk.comp.os.linux that:
"There was a legal precedent set in the UK a little less than a year ago, in which the company's name and contact details in an email signature were taken as sufficient identification of the company for the contents of the email to be acceptable as a contract [...]"
and then helpfully provided some references about it. The headline on Disclaimers could make emails into contracts [The Register] seems a bit off. Even the article ends:
"The end result of this could be that people who include a signature and disclaimer at the bottom of their emails might actually be making themselves more liable than people who just send one line emails."
Note the might there. It's quite a leap, isn't it? Mehta v J Pereira Fernandes SA [2006] EWHC 813 (Ch) (07 April 2006) appears to have ruled that headers were not a sufficient signature, rather than that a plain text signature block (sig) is sufficient. Have I missed a key point here? AFAICS, the ruling contains the following key general points:
"28. I have no doubt that if a party creates and sends an electronically created document then he will be treated as having signed it to the same extent that he would in law be treated as having signed a hard copy of the same document. [...]"
"30. [...] if a party or a party's agent sending an e mail types his or her or his or her principal's name to the extent required or permitted by existing case law in the body of an e mail, then in my view that would be a sufficient signature for the purposes of Section 4. [...]"
I doubt that a sig is quite the same as a hand signature, as it doesn't necessarily 'serve as a method of authentication' as required by the Digital Signature Directive ( 1999/93/EC, Electronic Signatures Regulations 2002), but there are times when it could bind one to things. Essentially, using a sig is like using headed paper, not like hand-signing. Parts of the ruling (para.19) seem to argue that automatic insertions make things carry less weight AFAICT - does that hint at how futile those forced stupid disclaimers would be if relied upon in court? Does the same automatic-or-decision point also mean that using a electronic signature tool (gpg or whatever) selectively helps it carry more weight than signing everything automatically? I don't agree it ... signs death warrant for Digital Signatures [Financial Cryptography] Interesting questions. Anyone know if the answers are decided yet?

Matthew Palmer: Severe Discomfort's "The Joy of UDP"

(For the grammar Nazis out there: no, that apostrophe is not misplaced)
There are times when a connectionless protocol almost doesn't seem worth the hassle. Take, for instance, the troubles of a round-trip communication, using UDP, where the initial request is sent to a secondary IP address on an interface. Your code, on the server, might look like this:
 s = UDPSocket.new
 s.bind('', 12345)
 loop   data, remote = s.recvfrom(65535); s.send(data, 0, remote[3], remote[1]  
This is a pretty simple Ruby fragment which just reflects your UDP packets back at you. It really doesn't get much simpler than that. Connect to this thing from somewhere else (using nc -u remoteip 12345) and you can reflect packets back and forth to your heart's content. Or so you'd think... When talking to a regular IP address, your packets probably look something like this (when viewed using tethereal):
 192.168.0.1 -> 192.168.0.2 UDP Source port: 35716 Destination port: 12345
 192.168.0.2 -> 192.168.0.1 UDP Source port: 12345 Destination port: 35716
Fantastic -- I send a packet, and get one back. In netcat, you see whatever you typed printed back out again. But, what if I add a secondary IP address to the server's interface (ifconfig eth0:1 192.168.0.5, for instance) and try sending packets to that IP address (with nc -u 192.168.0.5 12345)? I get this insanity:
 192.168.0.1 -> 192.168.0.5 UDP Source port: 35772 Destination port: 12345
 192.168.0.2 -> 192.168.0.1 UDP Source port: 12345 Destination port: 35772
And of course, no self-respecting network stack is going to accept a packet back from a totally different IP address, even if it did manage to get the ports right. Hence, the client never sees the return packets, and thinks that the server is snubbing it. What's happening here seems insane, but it's actually just a regular artifact of a connecntionless protocol like UDP. You see, we've bound our socket to the "any" address (the empty string in the call to #bind tells UDPSocket to bind to the "any" address -- no, I don't know why either, it's not a particularly intuitive interface). When we get the packet into our app via #recvfrom, we get no information on what address the packet was actually sent to, only that the OS decided that the packet was for us (yay for encapsulation). The only information we get is where the packet was coming from -- and due to the fact that the kernel keeps no connection-related information around for the socket (the kernel figures it'll hold us to our connectionless pledge), when the time comes for us to send a packet back, we have to explicitly say where we want that packet to go -- that's the remote[3], remote[1] arguments in the #send call. The brain-leakage starts when we work out where to say the packet is coming from. When we send the packet, a source address needs to calculated -- again, the kernel keeps no information on source or destination because we're connectionless. Because our socket is bound to the "any" interface, the OS thinks it has carte blanche to set whatever source address it likes. In Linux, the behaviour appears to be to pick the IP address set on the primary alias for the interface that will be used to send the packet out on. So for the common case (one IP address per physical interface) everything is fine. But those corner cases, gee, they're awfully sharp and pointy... The solution, of course, is to send the packet out through a socket that is bound to the particular address you want to use as the source address -- then the kernel knows what source address you want, and there's no confusion. Seems pretty trivial, right? Surely every sensible network application does that already, right? So obviously Ruby's UDPSocket implementation just sucks. That's what I thought, and I don't blame you if you think so too. But before you raise pitchforks and storm the gem-covered castle, try repeating our little experiment with some other widely-used UDP-based applications, such as net-snmpd or your ntp server. (The NTP server is a little different, in that to trigger the problem you need to start it and then setup the interface alias, for reasons I'll explain later). Both net-snmpd and ntpd exhibit the same behaviour as our trivial UDP echo service -- at least, the versions present in Ubuntu Breezy do, although I can't imagine everyone's suddenly cottoned onto this problem in the last 12 months or so and come out with a rash of fixes. So, basically, everyone seems to be suffering from the same malady. For values of "everyone" that equal "some UDP servers". There's some services that don't seem to have such troubles with alias interfaces -- the Bind DNS server comes immediately to mind, and ntpd works fine if you start the NTP server after you setup the interfaces. Why the difference? These services are clever and bind to each IP address on the system separately, like so:
 $ netstat -lun  grep :53
 udp        0      0 192.168.0.1:53          0.0.0.0:*                          
 udp        0      0 192.168.0.5:53          0.0.0.0:*                          
 udp        0      0 127.0.0.1:53            0.0.0.0:*                          
This is very cool, and solves the problem, except that if you add another interface after you start Bind, it doesn't pick up the new address, and you're boned until you restart the daemon. It also increases code complexity a bit, since you need add a select into your request handling loop (instead of just blocking on the #recvfrom call, like I've been doing thus far). Whilst I'm never happy about unnecessary complexity, I'll deal with it where I have to, but the real killer for this application is the "you can't change your interfaces after starting the daemon" rule -- my particular need is to make requests to a virtual service IP address, and restarting my service after each IP address change is going to suck hard. I mentioned ntpd earlier because it has some extra trickery at work. It's list of bound interfaces looks like this:
udp        0      0 10.6.66.6:123           0.0.0.0:*                          
udp        0      0 192.168.250.6:123       0.0.0.0:*                          
udp        0      0 172.14.16.6:123         0.0.0.0:*                          
udp        0      0 172.31.62.1:123         0.0.0.0:*                          
udp        0      0 192.168.37.179:123      0.0.0.0:*                          
udp        0      0 10.64.64.64:123         0.0.0.0:*                          
udp        0      0 127.0.0.1:123           0.0.0.0:*                          
udp        0      0 0.0.0.0:123             0.0.0.0:*                          
It listens to every IP address explicitly plus the "any" interface. I'm not quite sure why, either -- just listening to the specific addresses works for Bind, and if you add an interface alias after starting ntpd, it exhibits exactly the same problem as the trivial UDP echo service, so I don't think that listening on "any" is really gaining it anything. Listening on "any" does make ntpd behave differently to Bind: with Bind, if you send packets to an interface that wasn't available when Bind was started, it just completely ignores you (because it lacks a socket listening for packets to that address), while with ntpd the packets hit the "any" socket and suffer from the wrong-source-address bug. At the moment, my best chance of a solution appears to be to follow Bind and ntpd's lead and hook onto every address, but with the extra twist inspired by ntpd -- listen on the "any" address as well as all of the specific addresses. If I use any packets that arrive on the "any" socket as a trigger to rescan the available addresses (to add any new addresses that have been created since the last scan), that should solve all my problems. Now I only need to make it work (and deal with the insanities that will no doubt result). Wish me luck. The screams of pain and frustration you hear (no matter where you are in the world) are probably mine.

Clint Adams: ABC, easy as 321, simple as fa-sol-la

Far too late after #394749 got fixed, ZOMG switched from mpg321 to mpg123. The reason that this is so exciting is that mpg123 supports output buffering, whereas mpg321 has been sucking ass for over five years.

14 November 2006

Joey Hess: broken

I fell less than 2 feet and managed to get a minor fracture of my radius at the elbow, so I'm in a sling and will get to practice being right-handed for a few weeks. Typing so slowly feels almost like being struck mute.

Joachim Breitner: Infoning in Ghana

I m running a computer club at the school in Ghana where am volunteering as a Free Software advocate at the moment (as you probably know already). At first I tried to spread a little bit of general hacker attitude by introducing an internal wiki and blog, and by explaining what Free Software is. Then some students indicated interest in a programming course, so I held python lessons in the club (Sessions 3, 4, 5, 6, 7, 8, 9 and 10). Unfortunately, interest was declining over time, and while the first lessons had over ten participants (not to speak of the 20 at the very first one), it soon fell to around four. There was also some fluctuation, students leaving, others joining (and then of course lacking the lessions from the earlier sessions).So today, with four students who only recently joined, I started something new: I introduced the game infon, by fellow entropianian Florian 'dividuum' Wesch. It is a networked battle area where bugs compete over food and fight each other. Suitable for the computer club makes it the fact that the bugs are not directly controlled, but the players write their intelligence (using the simple language lua) and only upload code to the server. They can even do this while the game is running and it was a very fun game to play at GPN5 in Karlsruhe. You can read my infon-tutorial, and it s mostly non-SOSHGIC specific.I got them far enough to type the code that I presented as an example, to get it running, and to extend it slightly. I am only hoping that they will dig in a little bit deeper until next week. I think that you can only be successful in learning programing or similar things if you spend some time doing it besides the classes, and I did not see that happening when I was doing python. Maybe I was going too fast or the text-only way of doing it was discouraging, but I did expect them to starting having their own ideas at least after we were programming a simple text-based maze in the club.

Norbert Tretkowski: IPv6 enabled

Thanks to my new employer (for those who didn't notice, I left Teamix and work for IP Exchange since September), this server has a native IPv6 connection since I moved it to it's new colocation about two weeks ago.

Steve McIntyre: aaargh! cdbs...

Steinar suggests that he doesn't like cdbs. He's not alone. cdbs may make life easy for the maintainer, but it can make it incredibly difficult for anybody trying to fix bugs and NMU a package. I've found this myself when doing RC bugfixes during the recent round of BSPs; I must admit that more than once I've started looking into a bug only to give up the moment I've seen it uses cdbs. Fixing packaging errors is much harder when all the details of the package build are hidden from you in a mass of variables and included Makefiles. Unfortunately, it seems quite a number of new inexperienced maintainers have been using cdbs with very little understanding of the magic it does behind the scenes. This doesn't bode well for the quality of their packages in my experience.

MJ Ray: iCommons is not open and transparent

iCommons's code of conduct states: "iCommoners employ open and transparent governance and processes" The iCommons mailing list replies: "You are not allowed to post to this mailing list, and your message has been automatically rejected." iCommons are good with words, but not so good with deeds. See more examples from Creative Commons in How to not run a consultation and iSummit. At least iCommons lists aren't doing the silent rejection trick from notconsult. A small step forwards...

Jeff Bailey: Equality on Campus

I'm pleased to see that the McGill Student Union is now refusing to allow blood drives until anti-homosexual discriminatory questions on the questionnaire can be dropped. The problem is one of stupid questions combined with discrimination. My friend Katy put it best about when she went to fill out the questionnaire: "No, I can't guarantee that I know my partner's sexual history. But I'm willing to bet my life on it."

According to an article on a recent Public Health Agency of Canada report:

The PHAC report reveals that 51 per cent of those infected with HIV continue to be men who engage in homosexual activity.


(Note that the lifesite.net is a Christian, pro-life, anti-gay website. I don't have time at the moment to dig out either a better source or the original report.)

Perhaps I'm doing my math wrong, but at the point when 49% are those who don't identify as homosexual (and 40% of those are women), then you've probably got a third to half a chance that someone in that line isn't a man who's had sex with a man and could be HIV infected.

I hope that the McGill protest puts enough pressure on Health Canada to review this policy and drop the discrimination completely.

Simon Richter: Portable music players and Web2.0 style community building: the next hype?

So the Zune's big killer feature is (heavily DRM'd) wireless sharing of music. While I believe this will finally educate the masses about the evils of DRM, I would rather have a way to "recommend" a piece of music and offer a snippet for download to people near me, even without me being active in any way. If something like this catched on, and the transfer rates were acceptable, I could get a few new tunes on my daily commute, and learn about new artists this way. Throw in a rating system (doubling as spam protection), and a way for me to get the URLs of the artists' homepages for pieces I marked as "noteworthy" while they were playing into my browser easily, and this is the platform of teh phuture.

Lucas Nussbaum: When Ubuntu users discover that unofficial repositories can be harmful

Unofficial APT repositories are a PITA in the Ubuntu community. Most users use stable release (see previous post about that) since Ubuntu development releases tend to be much more bleeding edge than Debian unstable. But users still want the newest software, so they use unofficial repositories. There are lots of posts about private repositories on Planet.ubuntu-fr.org, and it seems to be the same on other local planets. Recently, somebody posted a sources.list file with a huge list of unofficial repositories. The maintainer of one of these repositories, J han Kiviniemi, was surprised to be in this list without even being contacted first. He chose a good answer: he uploaded a package with cool new default wallpapers. He also wrote a detailed explanation, with which I couldn’t agree more. But this story raises a question: why do all these people work on their unofficial repositories, instead of filing and fixing bugs, improving the official packages, and getting their packages into Ubuntu ? It’s a shame that so much manpower is lost on such stuff. PS: Johan Kiviniemi seems to have a lot of good opinions. :-)

Evan Prodromou: 22 Brumaire CCXV

My third and final article on the Web 2.0 conference came out today in LinuxWorld: Web 2.0 Summit: Open Source software borrows back from the open API Web. I tried to insist that they use the French Revolutionary Calendar for the byline but LW flatly refused. Go figure. The article turned out well, except that Chad Dickerson's name somehow ended up as "Brad Dickerson". D'oh. But I think overall it was pretty good series, and I concentrated on the stuff that I thought was fantastico. Which turned out to be the fun way to do it. I'm not sure whether it's best to take a breather right now and not worry about more conferences until March with SxSWi 2007, or if I should be finding other things to do. Really, I kinda have a lot of work to catch up on, some interesting projects to get started, and all kinds of stuff just goin' on. tags:

MTL I had beers at La ka this evening with Michael Lenczner of le sans Fil (our local, insanely good community wireless system in Montreal) and Civic Access and just generally an all-around good guy. We met... last year, maybe?... at one of Seb Paquet's Friends of Seb lunches. Man, Seb knows everybody. Anyways, a fun time was had. La ka is always a nice place to spend a few hours, especially with a Griffon Rousse in hand. Or so. We chatted about alternative office systems (my new obsession since Patrick Tanguay's presentation at BarCampMontreal), 802.11n (the new multi-antenna standard for wireless), and HAL, the incredible new system SF has for distributing locally-made art and culture on the local network of their hotspots. A great idea, and I hope it goes far... I want to use it in New York, Durban, KL and Perth. I think if I get around to talking to Boris sometime in the next week I'll have completed my post-barcamp trifecta. tags:

Smashing success! Sounds like The Kokoromi Collective had a Smashing success at their event the other night. A little bummed that we couldn't make it, but glad it turned out so well. tags:

13 November 2006

Miguel Gea: bulmages package.

  Bulmages is a big invoice program that has developed as a project in Iglues organization.
Ren Merou and I have been working in bulmages package more than one year. And now, at 15 days to release etch, It's ready!

   I've been thinking to wait to Etch is out, but I've decided to upload it. It's not an a package for experimental, so I've uploaded to unstable, but when it is in unstable, I'll report a RC bug to avoid problems with Etch release. Only if Etch is delayed enought (and I don't think so) and if it has enought installations I'll let it enter.

   If the Dunc-Tank project doesn't exist, I'd let it enter Etch, but I don't want anybody say me I've uploaded it to delay Etch.

Wouter Verhelst: Rock's kernel

I've decided it's been enough. Rock has been running 2.6.12 for ages. Not because I didn't want to upgrade, but since 2.6.12 was the last Debian-packaged kernel that would actually boot on rock. You see, this machine is a rather old SMP system, and there seems to be something wrong with its interrupt system. It would boot if I used a uniprocessor kernel instead, but then it's pretty silly to have a box with two processors, and only use one of them... At first I ignored it, assuming it would get fixed some time soon. Unfortunately, that didn't happen. And since we're at 2.6.18 right now, and the kernel team has done away with uniprocessor or SMP-only kernels, that means I can't even upgrade to the latest kernel anymore, even if I'd want to. I've been using git-bisect for the last few days in an attempt to find the issue, so that I can report it... only today I realized that I did remember 2.6.13 not to work, but that perhaps it failed for reasons not related to my current problem. Downloading that package from snapshot.debian.net and verifying showed that this is, indeed, the case. Grmbl. So I had to start all over again... Not fun. After starting that, I suddenly found out that make-kpkg didn't want to be friends anymore:
LC_ALL=C make-kpkg --initrd --config oldconfig --rootcmd fakeroot kernel-image
exec debian/rules  DEBIAN_REVISION=2.6.13-10.00.Custom  INITRD=YES  ROOT_CMD=fakeroot  kernel-image 
debian/ruleset/targets/source.mk:34: *** target pattern contains no  %'.  Stop.
wouter@rock:/usr/src/linux-2.6$ 
Hate. Grmbl.

Wouter Verhelst: Me too, daddy, me too!

According to Aurelien Jarno, it's possible to run Debian/ARM and both Debian/MIPS platforms inside an emulator that itself is packaged and runs on Debian. Since fairly recently (about a month or two, I guess), the same is true for Debian/m68k. Granted, the emulator you need to install isn't called "qemu", but with ARAnyM (short for 'Atari Running on Any Machine') it is now possible to run Debian/m68k. And it's fairly easy to do, too: There, you have a free m68k development machine! Note, however, that there might be issues with the network interface; the NIC in the emulated machine is unlike any real, actual Atari hardware. There is a driver for Linux, but I'm not 100% sure whether it's been integrated in the Debian kernels yet. I'm sure Christian will kick me awake on this, though ;-)

Aurelien Jarno: Cheap MIPS/MIPSEL development machine

In addition to the ARM platform, it is now possible to emulate a MIPS (big endian) or MIPSEL (little endian) machine running Debian under QEMU. It could be used as a cheap MIPS/MIPSEL development machine to test your packages, provided that you have a not to slow i386, AMD64 or PowerPC computer. Running on an Athlon 64 X2 3800+ the emulated system is around 10% faster than my SGI Indy R4400SC 200MHz and possibly with much more RAM (my emulated system has 512 MB of RAM). Also for the ones who know about the Indy SCSI controller, the transfer rate is around 13 MB/s on the emulated system. I have written a small howto explaining how to install Debian Etch on such an emulated MIPS or MIPSEL machine, using Debian-Installer RC1, which has just been released. Thanks to Daniel Jacobowitz who has recently improved QEMU/MIPS a lot, and to Thiemo Seufer who has started the integration of the MIPS QEMU platform in Debian-Installer and in the Debian kernel. Note 1: I have written this howto very quickly, so there are probably some mistakes. Comments are welcome.
Note 2: I have updated the ARM howto to take in account improvements from Debian-Installer RC1

MJ Ray: Chain Emails: Parcel Delivery Services

I've seen the Parcel Delivery Services email hoax twice in the last few weeks. Premium telephone services regulator ICSTIS issued a press release debunking it on 1 November 2006:

"This is in fact an urban myth. It is not possible for a GBP 15 charge to be made on connection."
I added a new tip about telephone number warnings to my email page.

Sven Mueller: Dual boot and full encryption

I’m trying to set up a laptop which needs as much security and privacy as I can get. It turns out the main problem is that I want and need dual-boot: Windows XP Professional and Linux (Debian Etch). Now, Encrypting of all partitions used (except /boot of the Debian installation) is a must. Without dual-boot, this won’t be any problem, but not with the wish to dual-boot. The Linux side isn’t a real problem, I simply use a dm-crypt’ed partition as the only “physical” volume in an LVM volume group, which contains three logical volumes: Swap, / and /home. This means I only need to enter my LUKS/dm-crypt password once during boot. Shared partitions (shared between Windows and Linux) are also encrypted with dm-crypt/LUKS and decrypted by FreeOTFE (which is a really nice little OpenSource tool BTW), formatted as FAT32. The Windows side on its own won’t be too much of a problem either, since BestCrypt, PGP Whole Disk Encryption as well as DriveCrypt PlusPack (this probably isn’t a complete list) allow encryption of the Windows boot partition, but at least the latter two need their pre-boot authentication part (which is needed to be able to decrypt the Windows boot partition) to be installed into the MBR. Now, I wasn’t yet able to get Linux installed to the disk without breaking the Windows decryption. If anyone knows a program which allows encryption of the Windows boot partition and dual-booting into Linux, I would welcome a hint. Preferably, this solution should use grub as the primary boot manager.

Erich Schubert: Eclipse chaos

For my diploma thesis, I'll be extending a tomcat-based wiki. So I decided to setup a development framework for Tomcat, JSF and all these. What a mess. The installation docs are really really bad etc. Two hours later, a dozen Eclipse restarts, I might finally have the Eclipse.org Web Tools Platform on my computer. I don't know yet, since I didn't even write a single line of code or metadata yet. I think I've picked my preferred mirror about 20 times by now. I wish I could just use apt-get. Debian is so nice for installing software... I wish eclipse were a pure opensource project, and there weren't so many companies trying to sell extensions to it. Oh, and I wish it were a native Linux/Unix project, and wouldn't care about working around Windows userunfriendliness by offering an own installer and own update tool and own everything-that-windows-lacks. [Update: how to install eclipse extensions without going crazy:
mkdir -p ~/.eclipse/eclipse/plugins
mkdir -p ~/.eclipse/eclipse/features
touch ~/.eclipse/eclipse/.eclipseextension
Now start eclipse, go to Help, Software Updates, Manage Configuration and add ~/.eclipse/eclipse as a location to search at. Note that the folder must be called eclipse and have these two folders and marker file in it.]

Nacho Barrientos Arias: Debian NM process movements

I was approved by Debian NM FrontDesk team today, then, only one step remaining to dispatch my application. I hope to be DAM approved soon, go go! :) By the way, tomorrow I will have a skills test to get a driving license, wish me luck!

Next.

Previous.