jordswart.org

Yesterday I received an email from stopbadware.org. They reviewed my site and found no problems anymore:

Google’s most recent test of your website found no badware behaviors on the site.  As such, the Google warning page for your site has either already been removed or should be removed shortly.  In addition, if your site has been listed in our Badware Website Clearinghouse, we will remove your site from the Clearinghouse list.

So far so good, a bit late maybe since my site has been unblocked since about a week. However the last paragraph of the email reads:

Please note that we will be retesting your website at periodic intervals in order to monitor that it remains free from badware. If we find that you are hosting or distributing badware in the future, the reviews process may take considerably longer than the original review.

Now this really made me laugh. The next review process might take even longer? Due to the lack of information provided by stopbadware.org and Google, my site has been marked as a badware site for approximately 2 and half weeks. It took stopbadware.org another week to review my site, after Google found it was clean. But when I get hacked again, it even might take them longer to respond than they already needed?

Considering the cooperation between firefox and stopbadware.org I might have to switch to Opera, or god help me, even Internet Explorer.

I found this beautiful website of the “Universität der Künste in Berlin”. It features some of the most interesting gadgets I have seen in years. If only they would be available. Two fine examples include:

The CharmingBurka:

The Charming Burka deals with Freud’s idea that all clothes can be positioned between appeal and shame. The Burka was chosen, because it is often perceived in the west as a symbol of repression. A digital layer was added so that women can decide for themselves where they want to position themselves virtually. The Burka sends an image, chosen by the wearer, via Bluetooth technology. Every person next to her can receive her picture via mobile phone and see the women’s self-determined identity. In the artists interpretation the virtual appeals can not be gathered by the laws of the Koran and so the Charming Burka fulfills the desire of living a more western life, which some Muslim women have today.
Therefore the Burka is equipped with bluetooth antenna/micro-controller and uses the OBEX protocol, already working with most mobile phones.

The Vanity Ring:

Update of the ring as a status symbol. It shows the number of Google hits you get, when you search for the name of the person who wears it.

While in earlier times richness and importance were equal to the amount of money or jewels someone possessed, in a post information society it’s the attention you get from the worlds people, that counts. Being in people’s mind means being important, whether they think about you in a positive way our not doesn’t matter. And what people have in their mind is what they read in the media. In the future this will mean, what they read/see on the net. Every content creator that copies and pastes your name will rise the value of your virtual mirrored importance. And there is a hard mechanical algorithm on the net, that extremely objectively measures your appearance, it’s called Google and has already passed the “line of no return” (Bruce Sterling). In most job interviews the personnel manager will already use this machine to check your importance and have a look at the first answers this mirror tells about you. Your mirror identity strikes back on your chances in the real world.

On February the 5th WordPress released version 2.3.3 of their blog software. This release fixed the following issue:

WordPress 2.3.3 is an urgent security release. If you have registration enabled a flaw was found in the XML-RPC implementation such that a specially crafted request would allow a user to edit posts of other users on that blog.

On February the 10th I applied the version 2.3.3 to my site.

Three days later Ubuntu Hardy installed the new firefox 3.0 beta. This version of Firefox works very closely with stopbadware.org to prevent users from accessing malware or badware sites. I found this feature when I used Firefox to visit my own site. I was informed of the fact that my site actively distributes or promotes malware and Firefox will not allow access to it. Disabling one of the security features in Firefox restored the access to my site. I instantly understood that my site was hacked  (again) in the last couple of days.

Trying to find out what was going on I read a lot of information on the stopbadware.org pages. Stopbadware.org is founded by Google so it is not surprising they use Google techniques to decide which sites are badware (or malware). A google search for my site today gives the following result (I also tried the same search on Yahoo, MSN and ASK.COM. Those engines have no problem with my site since they do not try to block access to malware sites):

Doing some more research I found that Google’s webmaster tools will give me an option to let Google do a review of my site. The bad thing I found was that Google does not tell you what is wrong with your site. They only state that there is something wrong. This makes it very hard to debug the site and fix the problem. I ended up going through all the pages and have a look at the source of each.

I found two hidden links. The links were hidden in <noscript> tags, so they were not accessible for the visitors of my webpage, they were just there for search engines to enjoy (I guess the person who inserted the links hopes to gain more attention if his site gets linked to a lot). So I removed the links, did some queries on my database and decided my site was completely clean. Then I asked Google to re-evaluate my site.
Read the rest of this entry »

Since information on Google seems to be a bit hard to get and I wanted a central point for all the information, here it is.

Please note:
This information modifies files on your computer. After modification your computer may not work anymore which may result in loss of data. If this, or worse, happens don’t complain, you have been warned.

(K)ubuntu version
The question is what to use for this installation. My personal choice is to use Kubuntu. So everything here has only been tested with that particular distribution. Since nothing I have done has anything to do with either KDE or GNOME, everything should apply to all variations of ubuntu.

The second question was, what version should I use. Gutsy has the advantage that it supports OpenGL 3D effect (screensavers, beryl and Google Dekstop) out of the box. Feisty will freeze if you run those applications. But Gutsy still is very unstable and has a lot of issues. So I went with Feisty and decided to do some backports of the important packages.

Last but not least I asked myself the question whether it should be a 64 bit or a 32 bit installation. Since I have a 64 bit machine it didn’t make sense to me to go with a 32 bit installation. If you have a 32 bit installation, please refer to Ross Burton’s blog for ready compiled packages. This howto will describe how to build the 64 bit packages. It should work for 32 bit as well, but since you can just download them I don’t think you would like to do that.

Now without further delay, here comes the howto install Feisty 64 bit on a Dell Latitude D830 with Intel GPU and all the 3D graphics you could ever dream of.

Installing (K)ubuntu
To install (K)ubuntu on the DELL Latitude D830 forget about all fancy graphical interfaces. You will have to use the text installation provided by the alternate CD, so download that one. I went for the AMD64 distribution, but you might as well go for the 32 bit one, since that will save you some compatibility problems. Then again, why buy a 64 bit machine if you are not going to use it…

Getting X to work
After the installation is done and you reboot the machine you will be prompted by a nice command prompt. Since the cdrom will not function correctly there are a few steps you will have to execute:
Open the file /etc/apt/sources.list and remark the first line, listing your Feisty CD as an installation source. Then install all updates for feisty:
$ sudo aptitude update
$ sudo aptitude dist-upgrade

and install the xserver-xorg-video-intel package by typing
$ sudo aptitude install xserver-xorg-video-intel

Then open your xorg.conf and change the device from vesa to intel. After this change save the file and restart kdm. Things should be better. If restarting kdm doesn’t work, try rebooting the pc.

X is a little bit blurry
No it is not you, you do not need any glasses. After starting X everything will look a bit blurred. We will fix that issue later when we update the intel driver. So for now, you just have to live with it.

Getting the latest intel drivers
The default intel GPU drivers in feisty will freeze your pc as soon as OpenGL is running (Beryl, Google Earth) so these need to be updated. This is probably the hardest part of the installation since it involves updating parts of your x-server installation. I did warn you about blowing up your laptop, didn’t I?

You can achieve this in two ways. The first way would be to install gutsy packages on feisty. This can be achieved by using a debian process called pinning, which involves making changes to your apt.conf. More information can be found here. This is a very easy and very quick process, but it will also upgrade your libc6.

Since I think one should only upgrade the packages really needed, I decided to compile the packages needed for my libc6. This also makes sure that other packages depending on that library will not run into conflicts.

For the update I followed the following procedure:

Open your /etc/apt/sources.list and append the following line (make sure you use your own mirror location):
deb-src http://de.archive.ubuntu.com/ubuntu/ gutsy main restricted

Save the file and execute:
$ sudo aptitude update

Make a root directory for your sources:
$ mkdir ~/xorg

Install the dependencies needed to build everything:
$ sudo aptitude install fakeroot dpkg-dev
$ sudo apt-get build-dep mesa
$ sudo apt-get build-dep libdrm2

Install the libxdamage packages
$ mkdir ~/xorg/libxdamage
$ cd ~/xorg/libxdamage
$ apt-get source libxdamage
$ cd libxdamage-1.1.1
$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i libxdamage1_1.1.1-3_amd64.deb libxdamage-dev_1.1.1-3_amd64.deb

Install the mesa packages
$ mkdir ~/xorg/mesa
$ cd ~/xorg/mesa
$ apt-get source mesa
$ cd mesa-7.0.0/
$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i mesa-swx11-source_7.0.0-0ubuntu2_all.deb mesa-common-dev_7.0.0-0ubuntu2_all.deb libgl1-mesa-dev_7.0.0-0ubuntu2_all.deb libgl1-mesa-dri_7.0.0-0ubuntu2_amd64.deb libgl1-mesa-glx_7.0.0-0ubuntu2_amd64.deb libglu1-mesa_7.0.0-0ubuntu2_amd64.deb mesa-utils_7.0.0-0ubuntu2_amd64.deb

Install the libdrm2 packages
$ mkdir ~/xorg/libdrm2
$ cd ~/xorg/libdrm2
$ apt-get source libdrm2
$ cd libdrm-2.3.0/
$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i libdrm-dev_2.3.0-4_amd64.deb libdrm2_2.3.0-4_amd64.deb

Install the x11proto-print-dev packages
$ mkdir ~/xorg/x11proto-print-dev
$ cd ~/xorg/x11proto-print-dev
$ apt-get source x11proto-print-dev
$ cd x11proto-print-1.0.3.xsf1/
$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i x11proto-print-dev_1.0.3.xsf1-1_all.deb

install the xorg-server packages
$ sudo apt-get build-dep xorg-server
$ mkdir ~/xorg/xorg-server
$ cd ~/xorg/xorg-server
$ apt-get source xorg-server
$ cd xorg-server-1.3.0.0.dfsg/
$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i xnest_1.3.0.0.dfsg-6ubuntu3_amd64.deb xprint_1.3.0.0.dfsg-6ubuntu3_amd64.deb xprint-common_1.3.0.0.dfsg-6ubuntu3_all.deb xserver-xorg-core_1.3.0.0.dfsg-6ubuntu3_amd64.deb xserver-xorg-dev_1.3.0.0.dfsg-6ubuntu3_amd64.deb

Install the xorg-server-video-intel packages
$ sudo apt-get build-dep xserver-xorg-video-intel
$ mkdir ~/xorg/xserver-xorg-video-intel
$ cd ~/xorg/xserver-xorg-video-intel
$ apt-get source xserver-xorg-video-intel
$ cd xserver-xorg-video-intel-2.1.0/

The following is no longer needed with the 2.1.0 driver
This is where we patch the driver to be less blurry. If you like the blurry effect, please skip this part.
$ vim src/i830_lvds.c

Find the following line (line number 230):
pfit_control = (PFIT_ENABLE |
VERT_AUTO_SCALE | HORIZ_AUTO_SCALE |
VERT_INTERP_BILINEAR | HORIZ_INTERP_BILINEAR);

And replace it with the following:
pfit_control = 0;

Save the file (:x). And continue the installation.

$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i xserver-xorg-video-intel_2.1.0-1ubuntu2_amd64.deb

Edit your /etc/apt/source.list again and remove (remark) the gutsy line we added above.

Now reboot and see if X is still running… if not you are in deep trouble.

Installing Beryl
Installing beryl is easy. Just type:

$ sudo aptidute install beryl beryl-manager

Then start it by typing beryl-manager in a konsole

Using my repository
I just setup a repository with the above packages as debs. Please note that I am on a limited download rate, so if you want to install them on a 1000 machines, please setup your own mirror. Please note all packages are amd64!

To use the repository, you should add the following to your /etc/apt/sources.list:

deb http://ubuntu.jordswart.org feisty backports

You will also need to add my key to your list of trusted keys:

wget http://ubuntu.jordswart.org/falcon.gpg -O- | sudo apt-key add -