There are some things that I have learned over the years as bad practice. There are some that I have learned through reading and contemplation, and a little experimentation. One of the categories of bad things that I have learned is visual aids for statistics. There is basically one cardinal rule for data presented in a graphical form:

Let the user see the actual data.

It seems kindof obvious, doesn't it? I'm presenting data, you should be able to see it. If you want to show me that there are 450 widgets, and 230 whazits, and only 210 whositz, then you should show those. The simplest way of doing this is by just listing them out in a table:

Type	Amount
Widgets	450
Whazits	230
Whositz	210

That's simple, isn't it? However, it doesn't help the viewer any. They're pretty good if you want to know exactly how many of something there is, but not great at other things that you want to do with data. How do you find the minimum (or maximum) of all of the values? You scan, remembering the highest one you saw so far, and then go back to that one and find out. If the goal is to somehow compare, the viewer will be helped out by using a graphical display of some sort. One thing that humans are good at estimating is length. Quick, tell me what we have the least of:
That was easy, wasn't it. Bar charts are good - they can still be abused by people in evil ways, but most of the time they're pretty useful.

All of this is working up to pie charts. What's smaller, Whazits or Whositz here:

Is Widgets half or more than half of the pie? Pie charts are the bad seed of the graph world. They aren't very useful, hang out a lot, and don't help you much. The worst thing about pie charts is that they aren't even good at the thing they're supposed to be the best at: comparing relative sizes. Consider thanksgiving, or christmas, or whatever large gathering you prefer where there is pie. Lots of pie slices are laid out on the table. Which one is the biggest? It's hard to tell. It's even hard to cut even slices from a normal pie. Sure, you can cut in 4ths, 6ths, or 8ths, but I challenge you to cut a pie in 5 pieces equally - it's really hard! It's because humans aren't great at judging the differences between angles. They're only really good for seeing one thing: the largest piece in the pie. Even then, it's sometimes questionable - if you looked at a evenly sliced pie, could you tell the difference between a 23% piece from a 20% piece? The bad thing about this is that they are ingrained into our culture. There wasn't a finance report in the last 10 years without a pie chart.

All of this ranting was basically brought to you by a recent post on BoingBoing. This post features the most horrible monstrosity I have seen in a long time: the hierarchial pie chart. Feast your eyes on this monstrosity. I challenge any reader to tell me: what is the smallest third-level category? What is the largest?

Our brunch yesterday went super-well. We had about 15 people over, which was far too many for our supposedly mellow evening. But it was great -- we got to catch up with a lot of folks I've been missing over the holidays and haven't gotten to see. I hadn't seen Lucinda Catchlove much for a few months, and Heather Kelley and Damian DiFede made an appearance, too. We got to see John Usher, who's off to do weird things to people's ears at the Consumer Electronics Show in Las Vegas. Niko came with friend Johanie, who made some great black-bean brownies; DJ Ghostbeard was still feeling ill from NYE; and Meg showed off her deep purple hockey bruises. It was also nice to have some new friends come, too. I've been wanting to hang out with MC Turgeon, one of the most experienced bloggers in Quebec, founder of me dia and toiles-du-Web, since we met last year at South by Southwest. She and her partner Chris came over with a nice bottle of wine and got to know everyone there. Actually, she knew a lot of the people already -- she and Anne-Marie had met at Mutek, for example. When Patti came in, she said, "Oh, yeah, I know M-C. We do a lot of panels together." Ah, the panel circuit. Altogether a really good time. Probably the only downside is that our oven was really dirty, and while I was making quiches and roasted potatoes I smoked up the entire house. But it cleared pretty quickly, and with the nice weather we're having, I could even have the kitchen door open to clear the smoke. Unheard of! tags: bruncher mcturgeon montreal cooking

Making a point Speaking of unseasonably warm weather, the Green Party of Canada held a picnic and ice cream social on Mount Royal last Saturday, which would have a couple of feet of snow on it in a regular year. The subject of discussion? Climate change, of course. I dunno -- clever move, but do they have to rub it in? tags: green party picnic climate change

Shameless plugs My friend Allegra has started a great new blog, Sucking-stones. She's got a really good voice and it's now in circulation as one of the blogs I read each morning. Also, my friend Anne-Marie Bergeron has her first travel TV show on 33mag tomorrow. She's got a four-part series on her trip to Iceland which they're going to show. It's in French, but her husband Jeff only cusses in English, so that's probably what you'll hear when they're climbing glaciers and lava floes. Did that get everyone? I hope so. You know what they say: You can plug your friends, and you can plug your ears, but you can't plug your friends' ears. Or something. tags: allegra sucking-stones annemarie jeff 33mag

Chix I was just reading Angela Beesley's end-of-year blog post and realized that I'd missed the establishment of WikiChix. It's a new organization for female wiki participants, in the great tradition *Chix tradition of Linux Chix or Debian Women. All the more galling is that two other blogs I regularly read also covered the new group. Joseph Reagle made a note about gendered spaces and the role they play in any movement (like Open Content and wikis). Biella blogged about his bloggage and put some social-science twist that was a little hard for me to follow. In any event, good luck to WikiChix. I find clubs extremely fun and useful and by nature exclusionary, and nothing to get worked up about. Of course, as one of the two founding members of the Maldekstrulaj Vegeteranaj Esperantistaj Linuxamantoj (Left-handed Vegetarian Esperantist Linux-users Club), I'd probably be pretty hypocritical calling anyone else exclusionary. tags: wikichix wiki angela beesley joseph reagle biella coleman clubs

I am deeply missing a real wiki.debian.org/Hardware page. The current one is a joke. It would be nice to have something in the style of the Gentoo hardware page with nice pages which show what works and what doesn't.

I know about the Debian GNU/Linux device driver check page which is a good start, but:

• in most places (installation reports in and out of Debian) you will not see lspci -n output
• there is more to it than lspci (think lsusb, think stuff behind new/strange/uncommon buses - like the sound chips on some Apple ppc based machines)
• you need a running linux system (a live CD can be used for the test), but:
• Debian's live CD is in its infancy (I know, Knoppix should do fine)
• most live CD-s are i386 only (it doesn't matter that much, since amd64 machine should work with i386 live CDs)
  
• most places where you can buy hardware from:
• either they don't have the hardware in stock,
• either want an answer immediately,
• or they don't allow you to access the machine
• (I think) the database is outdated and people are not adding stuff to it
  
• there is no way to make a search based on the product name of the whole system and/or the component

Current situation (bad stuff)

wiki.debian.org/Hardware is a joke. For example, I was expecting to see a Network compatibility list, but instead I see some useless info.

What annoys me the most in this matter are dead links or links to dead/inactive projects.

Information is scattered all over the place (redirects and directories can help), is mixed/ungroupped, or is outdated.

Current situation (good stuff)

The information partly exists. Probably, in time, the wiki will be cleaned up, but until then you have to dig for the information.

There are plenty of sites and pages with information, but, still, you need to weed out the old/irrelevant stuff.

What to do about it

Before you say anything, no, there is no need for yet another Linux compatibility list project.

Ideas:

• contribute to the wiki
• add a wiki page for every machine you installed under Hardware/Compatibility/ Laptop,Desktop,Misc /$PRODUCTNAME (would it make sense to have it under Hardware/Compatibility/ Laptop,Desktop,Misc /$PRODUCTNAME/$DIST ?); link your page to the installation-report (you did fill an installation report for every installation you did, didn't you?)
  
• reorganize pages with directories (as proposed above)
  
• remove dead llinks
• add redirects for pages that just say "See foo"
  
• unify pages that contain almost the same information
  
• automatically make a wiki page for each (successful and unsuccessful) Debian installation-report based on the machine type (would need some logic to weed out the home made systems) - but only select the success/fail rate based on strictly hardware issues
• help Kenshi with his efforts for better hardware support

Update: Justin told me about the Ubuntu Laptop Testing Team project which is kind of nice. There is also a scraper script which was supposed to help making queries like "info about laptop X" and "which laptops have these features", but that script didn't work for me.

Via the Trademark Blog, My Cage — digitally generated silence for cellphone:

My Cage (Silence for Cellphone) dispenses with performer, piano and auditorium, instead utilizing a continuous stream of silence produced on a computer, and compressed to ringtone format. While noting that Mr. Keats doesn’t have a cellphone of his own, and may be less-than-qualified to make global pronouncements about them, the CEO of the company that distributes the ringtone believes that “My Cage” may be a platinum hit. “People want a respite,” he says, “and not everybody has the time or money to go to a spa. The virtues of silence are unsung.” Nevertheless, Mr. Keats is careful not to take credit for silence in general, and hopes that people will bootleg his creation, just as he was inspired by John Cage. Mr. Cage, who died in 1992, could not be reached for comment.

I hope the IP professors in the crowd are preparing a hypothetical for the next round of exams.

As part of my work on Xen I've been playing with Xephyr (a replacement for Xnest). My plan is to use Xen instances for running different versions of desktop environments. You can't just ssh -X to a Xen image and run things. One problem is that some programs such as Firefox do strange things to try and ensure that you only have one instance running. Another problem is with security, the X11 security extensions don't seem to do much good. A quick test indicates that a ssh -X session can't copy the window contents of a ssh -Y session, but can copy the contents of all windows run in the KDE environment. So this extension to X (and the matching ssh support) seem to do little good.

One thing I want to do is to have a Xen image for running Firefox with risky extenstions such as Flash and keep it separate from my main desktop for security and managability.

Xephyr :1 -auth ~/.Xauth-Xephyr -reset -terminate -screen 1280x1024

My plan is to use a command such as the above to run the virtual screen. That means to have a screen resolution of 1280x1024, to terminate the X server when the last client exits (both the -reset and the -terminate options are required for this), to be display :1 and listen with TCP (the default), and to use an authority file named ~/.Xauth-Xephyr.

xauth generate :1 .

The first problem is how to generate the auth file, the xauth utility is documented as doing it via the above command. But this really connects to a running X server and copies the auth data from it.

The solution (as pointed out to me by Dr. Brian May) is to be found in the startx script which solves this problem. The way to do it is to use the add :1 . $COOKIE command in xauth to create the auth file used by the X server, and to generate the cookie with the mcookie program.

In ~/.ssh/config:
Host server
SendEnv DISPLAY

In /etc/ssh/sshd_config:
AcceptEnv DISPLAY

The next requirement is to tell the remote machine (which incidentally doesn't need to be a Xen virtual machine, it can be any untrusted host that contains X applications you want to run) which display to use. The first thing to do is to ssh to the machine in question and run the xauth program to add the same cookie as is used for the X server. Then the DISPLAY environment variable can be sent across the link by setting the ~/.ssh/config file at the client end to have the above settings (where server is the name of the host we will connect to via SSH) and in the sshd_config file on the server have the line AcceptEnv DISPLAY to accept the DISPLAY environment variable. It would have been a little easier to configure if I had added the auth entry to the main ~/.Xauthority file and used the command DISPLAY=:1 ssh -X server, this would be the desired configuration when operating over an untrusted network. But when talking to a local Xen instance it gives better performance to not encrypt the X data.

The following script will generate an xauth entry, run a 1280x1024 resolution Xephyr session, and connect to the root account on machine server and run the twm window manager. Xephyr will exit when all X applications end. Note that you probably want to use passwordless authentication on the server as typing a password twice to start the session would be a drag.

#!/bin/sh

COOKIE= mcookie
FILE=~/.Xauth-Xephyr
rm -f $FILE
#echo "add 10.1.0.1:1 . $COOKIE" xauth
ssh root@server "echo \"add 10.1.0.1:1 . $COOKIE\" xauth"
echo "add :1 . $COOKIE" xauth -f $FILE
Xephyr :1 -auth $FILE -reset -terminate -screen 1280x1024 $* &
DISPLAY=10.1.0.1:1 ssh root@server twm
wait

According to my neighborhood newspaper (the Roslindale transcript), there has been a rash of late-night home burglaries in the area lately. Although the paper calls them “robberies,” they are probably more accurately burglaries (and thefts). Common law burglary requires breaking and entering the dwelling of another during the night with the intention to commit a felony therein; robbery requires taking property from a person by force. (Modern statutory definitions of burglary typically do not require the “night” element). In any event, my point is not to quibble with the legal terminology, but rather to question the preventitive measures. From the article:

Captain James Hasson of District E-5 said that this robbery does not fit the mold of the Bellevue Hill break-ins. … Hasson said he was very shocked because Rendall Road is a beautiful, quiet neighborhood that doesn’t normally see violent crimes. He added that there have been extra patrols of the Bellevue Hill area and there will now be extra patrols of the Rendall Road area.

On a much smaller scale, this response is similar to the air travel liquid ban that occurred shortly after the foiled transatlantic bomb plot from last August. Obviously a complete ban on liquids will make it less likely that a terrorist will concoct a liquid explosive plot, but does nothing to actually deter attacks overall. Similarly, once a house on a particular street has been burglarized, adding additional patrols on that street might make another attack on that street less likely, but I don’t see how it makes the community as a whole any safer. More likely this response makes the community less safe. Assuming the total amount of police protection hasn’t changed but just been reallocated, there are now other areas with less coverage. Even a dumb criminal should be able to figure out to avoid heavily policed areas. Unless you actually live on the street that is now getting the additional protection, I would not be reassured by this news.

While the next debian release is being prepared it is not a good idea to upload new packages, so I'm trying to use the holiday to 'look across the fence'. For starters I've gotten me an iMac and so far I like Mac OS X. It is an immense improvement over Windows and a pretty good alternative to KDE from my point of view. I'm still a bit lost with accelerators and in-program window movement but it is nice to have another environment to play with.

And on that machine I'll try to play with sbcl, openmcl and f-script. But so far I'm been busy using iMovie to convert our DV tapes into DVD's.

(continuing with clearing the blogging backlog) Four days after returning home to the US from the trip to Australia, I was at it again, flying the other way around the world. In hindsight, this was totally insane, but I'd expressed interest in going much earlier in the year, I think before we'd organised to visit Australia. I flew to Madrid, via Philadelphia. I've said it before, but I'll say it again, Philadelphia International is a very nice airport. It's the first time I've flown across the United States, and it really is a long way. Just like Brisbane to Perth, it's a long time on a plane for staying in the same country. Arriving in Madrid, entering the country was extremely straightforward, as I've also said previously, the immigration guy barely looked at my passport long enough to open it and find a page to stamp. It was my first time in a country that didn't speak English and wasn't terribly bilingual. Fortunately the airport was signed in English as well as Spanish, and the information/assistance people all seemed to be able to speak English. I arrived in Terminal 1, and the European contingent were mostly arriving at Terminal 4, which is essentially a completely separate airport, a short shuttle bus ride away. My flight arrived in the morning, and I had about 4 or 5 hours to kill before the first of the European contingent rocked up. It was tempting to get a train or taxi into Madrid and have a bit of an explore, but I really didn't want to risk not getting back in time, so I just loitered around Terminal 4 for the time. The highlight of the waiting was I bumped into Doug Foster, who I used to work with a SecureNet in Canberra, disembarking a flight from London (where he's now working). It really is a small world. After everyone turned up, we got on a bus and headed for Badajoz, a mere 5 hour bus ride away. We didn't get away until about 7pm, so by the time we hit the road, it was dark, so there wasn't a lot to see. We arrived at Badajoz around midnight, and made a short walk to the hotel and had a late dinner and hit the sack. Unfortunately with all my travelling in the three weeks, I'd managed to come down with a cold, which started manifesting itself pretty much from the moment I got to Badajoz, so I started to feel increasingly suboptimal as the week wore on. Badajoz itself is an incredible little city. It's just like what I envisaged an old European city to be: narrow winding streets. It had a funny effect on me. I'd alternate between finding it really quaint, and incredibly claustrophobic (and I'm not usually the claustrophobic type). After doing a bit of self-analysis, I think the problem was the lack of sky. With so many buildings crammed in together and the narrow streets, the amount of sky you got to see was minimal. Definitely no horizon. I felt more comfortable at night, in fact the place looked really awesome at night. Everything was lit up, I think especially so for Christmas, and everyone came out and walked around and did shopping. The other thing that, well, I noticed about the city was that it was wall to wall concrete (or bricks, or bitumen). The buildings all connected up, there were no gaps between them, and the sidewalk basically ran from the front edge of the building, to the kerb, then there was the road, and then the reverse, so it was a real concrete jungle. That said, it was pretty clean. the sidewalks were all swept, there was no rubbish in the gutters. By about the second day, my cold had driven me crazy (my nose was running incessantly) and I just wanted some pseudoephedrine to dry it up. I didn't have a clue how pharmacies operated, but fortunately I was able to get Miriam to tag along with me, who spoke English as well as Spanish. She'd never heard of pseudoephedrine before, but as soon as she said it to the pharmacist, he knew what it was and came back with some form of Nurofen (ibuprofen) that also had pseudoephedrine in it. I didn't really want or need the ibuprofen, but when sick in Spain, beggars can't be choosers, so I took it. I didn't feel that it did a great deal for me anyway. Getting home again was fun. Due to various peoples' flights, the bus was leaving at 6:30am, and that wouldn't get me back to Madrid the ideal 3 hours before departure, so I took a taxi with a few people who needed to be there earlier. It left Badajoz at midnight, and arrived at Madrid at about 4am, where I had to wait for about 5 hours before I could check in for my flight. I had a bit of fun leaving, which I've already written about, and was happy to get home late on Sunday night. My cold had gone to my chest by this stage and I had bronchitis, so I was just glad to get home and see a doctor on Monday. So now I can say I've been to Europe. It was a shame I didn't get to see Madrid itself. Next time. Update Photos from the trip are here

You scored as Either. You brain is neither specifically male, nor female in the way you perceive your surroundings. As bad as this may sound to some, it can easily mean that you are capable of combining both gender aspects to your advantage. Rather than being genderless you are possibly able think freely. This does not mean that you are bisexual or androgynous or indecisive, but it might. Either 64% Male 57% Female 43% Neither 18%

Should you be MALE or FEMALE?*
created with QuizFarm.com

This quiz was blissfully short. I've seen ones at quizfarm go hundreds long. I love the "this does not mean xxxx, but it might" complete cop-out.

I have been asked for advice about long-term storage of documents. I decided to blog about it because my thoughts may be useful to others, and because if I get something wrong then surely people will correct me. ;)

Many organizations are looking at using computers for storing all documents. This gives savings on the costs of storing paper - the promise of the paperless office is being fulfilled. There are some potential issues about whether a signature in a PDF file that's scanned from paper is valid - but I guess it's the same as a signature on a FAX and everyone seems to accept FAXed contracts.

The technical problem is how to reliably store data long-term. The problem is that all modern methods of storing data will degrade over time. Anything less than engraving a message in stone, gold, or platinum and burying it will have some data loss eventually.

If the documents that need to be archived have no special requirements and if you have a good backup system in place (testing backup media, off-site storage in case of disaster, multiple sets of hardware that can read the backup media in case of hardware failure, etc) then you might be able to just store the documents on a server and include them in the backup plan. The regular backups should cater for replacing media over the long term. If however there is a significant amount of data or the data has confidentiality requirements that preclude having it all online all the time then you need a separate infrastructure for such storage.

Regular backup systems have to deal with files being deleted from storage and files that have their contents changed. For a document archiving system no file will ever be changed once it has been created and no file will be deleted. This allows some simplifications to the backup strategy. For example if you have multiple terabytes of documents backed up by tape and stored off-site you could use CD-ROMs or other media for storing recent changes. It would be very easy for an employee to grab a couple of CDs before rushing out of a burning building, but grabbing a set of tapes (or the correct tape from a large set) may not be possible.

It would be possible to use a tape library system as the primary storage for documents. If a large organization was going to implement this a few years ago that might be a good option. Nowadays storage is getting increasingly large and cheap. Terabytes are available in desktop PCs and hundreds of terabytes are available for server storage. So having the primary document store on a server with a decent amount of space and then making tape backups for storage in secure locations seems viable.

One thing to note about such document storage is that having everything on a server allows a much larger amount of data to be accessed and copied more easily than on paper. Sorting through a billion paper documents and copying the thousand most useful ones would be a difficult task for someone who was involved in industrial espionage. Finding the most useful files when they are indexed on a server should be quite easy and copying a few thousand is also easy (one thousand scanned documents of medium size should fit on a USB memory stick - much smaller than a few reams of copied documents).

Finally documents have to be archived in publicly documented file formats that can be easily read in the future. The PDF specification is well known and there are multiple programs that can display data in such files, another good option for scanned documents is JPEG. Proprietary formats such as MS-Word should never be used, you never know whether you will be able to read them in four years, let alone the seven years for which many documents must be retained or the 20-30 years that some documents must be retained.

We got back to Montreal yesterday morning just after midnight. Maj got us upgrades on United to business class, which was really a life-saver. There's a direct flight from San Francisco to Montreal, but it's 5 hours one way and 6 hours on another. This time traveling to California, we decided to split up the flight, stopping in Chicago about halfway between. Returning was a good flight. We were comfortable, there was room, Amita had enough space to play on the ground and sleep comfortably on our laps. Maj: "Business class isn't anything fancy; it's just enough space, good service and quality food that you feel like a human rather than like livestock." The only downside was that Chicago O'Hare is a half-ass airport. For one of the most (the most?) visited and transited airports in the world, it's really skimpy on services inside the security area. There aren't any big restaurants or nice bars or stores inside the B and C concourse; just stand-up kiosks. We walked halfway across the airport to find a pub to eat at. Probably the best thing about the airport is the giant brachiosaurus skeleton in B concourse. Amita June couldn't stop looking at it; she ran from foot to foot banging it with her hand. Good for her; it's a pretty neat thing to see in a boring airport. tags: airport travel ohare brachiosaurus amitajune maj

Ebjo Another Maj quote: "It's just a coincidence that we use the term blog as a cutesy contraction for 'Web log'. It could have easily have been a 'Web journal' people were contracting, and then we'd call it an ebjo." tags: ebjo blog maj

Goethe One of the things that I've found as a participant in Open Source software and Open Content is that there are a lot of different people involved. And today, in 2007, Germany and France have become important loci of new developments in Free Culture. I've been working on my French for a while, and I think I'm getting pretty good, but I've never learned any German. At all. But German Wikitravel is one of the largest and most popular versions of the project. And I want to be more of a participant -- or, at least, have some better relationships with our German users. So, today I signed up for German lessons at the Montreal Goethe Institute. The Goethe Institute promotes German language and culture world-wide, including high-quality lessons in German. Montreal's is in a beautiful old building right at the corner of Sherbrooke and St. Denis. It's got a nice office and a friendly warm bookstore, "Das Buch". I'm going to take the intensive beginner's course -- mornings Tuesday and Thursday for 6 weeks. I hope at the end of that time I'll be better able to meet German-speaking Free Software advocates, Open Content participants, and most of all Wikitravellers a little more towards halfway. tags: goethe institute german wikitravel classes montreal

La ka I went to La ka this afternoon again to meet a couple of people. It was my first two-meeting day at La ka, which I think is a bad sign I'm turning into a serious maven. But like they say, it's really where the hipsters are doing business on this le lately. The nice thing was that I got to introduce two Montrealers that I like a lot. Hugh Macguire of, among other things, the Librivox public-domain audiobook project, is really interesting and passionate about communities and free content. Nicolas Ritoux is one of the most clued-in tech journalists I've met. It was nice to introduce them, and it was good that they seemed to get along. Depressing, on the other hand, was walking around the Plateau in January with 12C weather. This has gotten beyond funny into scary -- we just haven't had any serious snow in Montreal this winter. I'm worried that it's going to get worse, too, and I don't know what that will mean for Quebec's culture. Mon pays, c'est l'hiver, goes the song, and I'm not sure I get what a city without winter would mean here. tags: winter laika hugh macguire nicolas ritoux librivox montreal snow

House Maj and I have been watching House on DVD. It's really good, although a little formulaic. Everybody's always running around and bleeding and vomiting, and people get an average of 3.8 different rare diseases per episode. There's also a lot of cheating and sneakiness. It's great. tags: house tv

Mantini One nice thing about New Year's Eve this year was that Baron Earl served a refreshing -- nay, energizing -- spocktail called a mantini. I was especially pleased to find out that the first ingredient was not, in fact, a praying mantis. With the Baron, you never know. tags: mantini spocktail baron earl

This is sort of a New Year's resolution... In no particular order:

1. Write a book.
2. Learn at least one new programming language.
3. Donate money to (or become member of) either the EFF, the FSF, the CCC, or another similarly important organization.
4. Make use of my rights as a citizen and write letters to elected politicians, urging them to promote certain topics/issues/laws (privacy, democracy, transparency) and to combat others (software patents, voting computers, data retention, mass surveillance and lots more comes to mind).
5. Work on and support selected Free Software projects in my spare time, especially projects which are of a greater importance to the Free Software movement (or the Free Culture movement; or freedom; or privacy; or anonymity; or democracy) than the 158th IRC client or the 276th tetris clone. Some examples: LinuxBIOS, Nouveau, Tor, Gnash, and Democracy Player to name just a few projects. General motto: Choose your battles!

Oh, and one more thing: Do the most important duty as a citizen of any democratic country — help to save democracy by killing voting computers. Yeah, so that makes six things I plan to do in 2007. Sue me.

I jumped on the gender quiz meme. I found this question rather funny: ‘You think this quiz is quite superfluous’. Anyways. It said that:

Male 57% Either 54% Neither 46% Female 36%

Should you be MALE or FEMALE?*
created with QuizFarm.com After that, I changed my mind. I do find it superfluous.

You scored as Either. You brain is neither specifically male, nor female in the way you perceive your surroundings. As bad as this may sound to some, it can easily mean that you are capable of combining both gender aspects to your advantage. Rather than being genderless you are possibly able think freely. This does not mean that you are bisexual or androgynous or indecisive, but it might. Either 71% Female 64% Neither 54% Male 39% Should you be MALE or FEMALE?* created with QuizFarm.com

Maybe it's these memes that are useless :)

The issue of core file management has come up for discussion again in the SE Linux list.

I believe that there are two essential security requirements for managing core files, one is that the complete security context of the crashing process is stored (to the greatest possible extent), and the other is that processes with different security contexts be prevented from discovering that a process dumped core (when attacking a daemon it would be helpful to know when you made one of it's processes dump core).

The core file will have the same UID and GID as the process that crashed. It's impossible to maintain the complete security context of the crashing process in this manner as Unix permissions support multiple supplementary groups and Unix filesystems only support one GID. So the supplementary groups are lost.

There is also a sysctl kernel.core_pattern which specifies the name of the core file. This supports a number of modifiers, EG the value "core.%p.%u.%g" would give a file named "core.PID.UID.GID". It would be good to have a modification to the kernel code in question to allow the SE Linux context to be included in this (maybe %z).

To preserve the SE Linux context of the crashing process with current kernel code we need to have a unique type for each process that dumps core, this merely requires that each domain have an automatic transition rule for creating files in the directory chosen for core dumps. In the default configuration we have core files dumped in the current directory of the process. This may be /tmp or some other common location which allows an attacker to discover which process is dumping core (due to the directory being world readable) and in the case of SE Linux there may be multiple domains that are permitted to create files in /tmp with the same context which gets in the way of using such a common directory for core files.

The traditional Unix functionality is to have core files dumped in the current directory. Obviously we can't break this by default. But for systems where security is desired I believe that the correct thing to do is to use a directory such as /var/core for core files, this can be easily achieved by creating the directory as mode 1733 (so that any user can create core files but no-one but the sys-admin can read them) and then setting the core_pattern sysctl to specify that all core files go in that directory. The next improvement is to have a poly-instantiated directory for /var/core such that each login user has their own version. That way the user in question could see the core files created by their own processes while system core files and core files for other users would be in different directories. Poly-instantation is easier to implement for core files than it is for /tmp (and the other directories for which it is desirable) because there is much less access to such a directory. When things operate correctly core files are not generated, and users never need to access each other's core files directly (they are mode 0600 so this isn't possible anyway).

This area will require a moderate amount of coding before it works in the ideal manner. I aim to briefly describe the issues only in this post.

You scored as Neither. You think neither like a man nor like a woman. What you are you may decide for yourself. Most people will consider you strange, alien, weird or funny. You are probably quite interesting.

Neither		75%
Male		43%
Female		43%
Either		36%

Should you be MALE or FEMALE?*
created with QuizFarm.com