Blackmoor Vituperative

The SCO Group was dealt a serious, potentially fatal blow today in its courtroom battle against Linux. The jury in the trial between SCO and Novell has issued a verdict affirming that Novell is the rightful owner of the UNIX SVRX copyrights. This verdict will make it difficult for SCO to continue pursuing its baseless assault on the open source operating system.

(from SCO loses again: jury says Novell owns UNIX SVRX copyrights, Ars Technica)

Mwahahahahaha.

The actual title of the article is “Six easy steps to make a super secure Linux server”, but I think that’s hyperbole. Even so, these are some basic steps that should be followed, and they do help make a server more secure.

1. Install latest security updates.
2. Disable root login via SSH
3. Disable or filter extra services
4. Remove active guest accounts and test accounts
5. Remove version notification
6. Hide application errors and PHP errors

(From Six easy steps to make a super secure Linux server, Technicant)

Fedora 12 has been released into the wild, and the general response is positive.

Every time a new version of Fedora (or any major Linux distribution) is released, there is always a great deal of confusion over the various releases: x86, i386, 686, and so on. Here is a quick guide that covers the vast majority of cases:

i386

• A generic “lowest common denominator” designation for Intel 80386 compatible CPUs (includes all of the above, but does not take advantage of extended instructions on those later CPUs).

Don’t use this unless you have to.

i686

• All Intel 32-bit Pentiums (excluding Pentium 1 and Pentium MMX)
• All AMD 32-bit Athlons

If your computer is several years old, you will probably have nothing to lose by using this version. However…

x86_64

• AMD’s Athlon 64, Athlon 64-FX, and Opteron
• Intel EMT64 processors – Pentium 4, Pentium D, Pentium Extreme Edition, Celeron D, Xeon and Pentium Dual-Core processors, the Atom 230 and 330 and in all versions of the Core 2, Intel Core i9, Core i7, Core i5 and Core i3

If your computer is less than a few years old, try this version first. If it won’t work on your machine, you will know almost immediately. If it does work on your machine, you may find that the performance is improved slightly (when compared to a 32 bit kernel), because the compiler was able to take advantage of slight improvements made in the instruction set for your processor.

So, start with x86-64. If that does not work, try i686. If that doesn’t work, try i386.

Good luck!

According to a new report on ZDNet, the SCO group won an appeal in its copyright case. In case you are wondering if this will halt or reverse the inexorable death spiral of SCO, or if it has any repercussions for the Unix/Linux world… it won’t, and doesn’t. All this means is that SCO owes money to Novell, and that SCO should have had a trial before they lost in Utah, rather than a summary judgment.

Bottom line: SCO will waste more of its investors money beating this dead horse. For Novell, it means a few more pennies, and for the rest of the Linux world, it’s a footnote in the history books.

If you would like aliases to work when you use sudo (for example, so that when you type sudo ls, your directory listings are in color, assuming you set up an alias for ls="ls --color=auto"), add the following lines to your ~/.bashrc:

# Enable aliases when using sudo.
alias sudo='sudo ' # Note the trailing space.

Credit for this goes to Curtis Free. Thanks, Curtis.

Google says that there are at least 18 Android devices on the way. Let’s hope that at least one of these has:

1. Everything the T-Mobile G1 has, including a physical keyboard,
2. a 4.5″ (measured diagonally) screen (but the same aspect ratio as the G1),
3. the Bluetooth DUN profile enabled (currently disabled on the G1, to my extreme annoyance).

Crossing my fingers…

I recently set up an old Dell Inspiron 2200 laptop to dual-boot Fedora 10 and Ubuntu 9. Neither distribution installed drivers for the Broadcom wireless-G card, but it was pretty straightforward. These instructions are for Fedora:


$ sudo yum install b43-fwcutter NetworkManager NetworkManager-glib NetworkManager-gnome
$ wget -c http://downloads.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2
$ bzip2 -d broadcom-wl-4.150.10.5.tar.bz2
$ tar -xvf broadcom-wl-4.150.10.5.tar
$ cd ./broadcom-wl-4.150.10.5/driver/
$ b43-fwcutter -w /lib/firmware wl_apsta_mimo.o


Then just select the wireless access point in Network Manager and enter the password, and you should be connected.

To think how much of a pain this was just a few years ago, it really is quite astonishing.

Michael Widenius, the original creator of the MySQL database system, announced in a blog entry on Thursday that he has left Sun Microsystems and is launching his own company. He is unsatisfied with the direction of MySQL development and believes that he will be able to make more meaningful contribution to the software from outside of the company.

[...]

It’s unclear how this move will ultimately impact the MySQL community, but it seems likely that the outcome will be positive. Widenius clearly wants MySQL to have a stronger community focus and is also still committed to making technical contributions. The departure of the project’s two cofounders in the aftermath of the acquisition doesn’t reflect particularly well on Sun, but it probably won’t have any direct impact on the company’s business interests or MySQL development efforts.

(from Unsatisfied with direction, MySQL creator leaves Sun, Ars Technica)

I got a fun email today from Comcast (my ISP), saying they are blocking port 25, the port on which SMTP sends email, as a measure to fight spam. Isn’t that a kick in the pants? Of course, the only time I send email from home is when mortshire.org sends me reports. However, that is important, so I needed to find a way for mortshire to send me email with Comcast’s blessing. Thanks to Patrick Ben Koetter and Chris Fay, I have done just that.

1. In /etc/postfix/main.cf I added or changed these lines:

myhostname = annwn.mortshire.org
mydomain = mortshire.org
myorigin = $mydomain
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain


relayhost = [smtp.comcast.net]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options=


2. I create a file /etc/postfix/sasl_passwd with the contents:

[smtp.comcast.net]:587 userid:password


where userid and password are my comcast.net username and password.

3. Next, I changed the ownership and permissions on the sasl_passwd file to protect it from unauthorized access.

sudo chown root:root /etc/postfix/sasl_passwd
sudo chmod 600 /etc/postfix/sasl_passwd


4. Finally, I created a database file from the contents of the sasl_passwd file:

sudo postmap hash:/etc/postfix/sasl_passwd


There we go: postfix now uses the Comcast mail gateway, and operates on port 587 rather than 25 (because spammers would never be able to do that, right? Yeeeeaaaahhhhhh…).

(Note: this is Postfix 2.5.5 under Fedora 10.)

I have been using the Nokia n810 for a few weeks now, and I am going to soften my criticism of it a bit. What the n810 does, it does really well. I am able to check my email, chat through Pidgin, and research on the web any time I am near a wireless hotspot.

The n810 has become my lifeline to my wife, my mother (who is having serious health problems), and my colleagues across the world. Suffice to say that I have turned around completely on the n810. No, it doesn’t replace my Palm — nowhere near. But it does keep me connected to my friends and loved ones, and at this time in my life I couldn’t really live without that.