ATI Catalyst 9.8 Proprietary Linux x86 Display Driver

Update : Drivers are working now. Move on to How To: Install ATI Catalyst (fglrx) 9.8 Drivers on Fedora 11.

I wonder why MSN would crawler same page from two different machines. I wonder if a single page can be divided further for crawling. Checkout the screenshots below

A few minutes later. Three Microsoft machines were crawling the same page

I have conformed using ARIN that all these IPs belong to Microsoft

PS : Direct link for translated website.

PS2 : The actual website.

ATI Catalyst 9.7 Proprietary Linux x86/x86_64 Display Drivers

In case you happen to screw your graphics display while trying to install ATI drivers, use the following command to uninstall fglrx.

[root@fedora ~]$ /usr/share/ati/fglrx-uninstall.sh

Well, I am back to square one. Have to wait for another month and I hope next release will have support for kernel 2.6.29+.

Update : Drivers are working now. Move on to How To: Install ATI Catalyst (fglrx) 9.8 Drivers on Fedora 11.

Now, if you are able to grab the url used to set the session variables, you can login as the user to whom that url belongs from any machine on the Internet (need not be the machine belonging to the same subnet) without entering the username and password of the user.

The proxy servers in the organizations can be used to exploit this vulnerability. Squid is the most popular proxy server used. In the default configuration, squid strips the query terms of a url before logging. So, this vulnerability can’t be exploited. But if you turn off the stripping mechanism by adding the line shown below, then squid will log the complete url.

strip_query_terms off

So, after turning stripping mechanism off, the log will contain urls which will look like this

http://www.google.co.in/accounts/SetSID?ssdc=1&sidt=Q5UrfB0BAAA%3D.oHVGErODzffQ%2Bms%2FOKfk53g5naReDKehRNHOBsmJlBu3VTNXjF03SbgX%2FVEEhmImhR4mlu5IAAjM%2BdbuXvMMSIb0oU8IGCYpnLcSNkbCIrG%2BQnm81YmX5%2Brcrq7U6Qx65%2F1yaQ2NzgmKD94jg0Iw13iXDen3qD5qn6L%2FhmmYWwTrcOeuTzGbO%2BAehpjEU3mrWapRafaq3b4kxyigJ68s8QrGQqZTINNE%2Bs%2BoIkZWmGt5kNzoT8fkVAsWJeu3CKFkxj4oVMngeDvpwb1nyFpsJCltOzmAr46fTxVJSpvQdx0%3D.BMLtjUdIDCcuszktZSvYzA%3D%3D&continue=http%3A%2F%2Fwww.orkut.com%2FRedirLogin.aspx%3Fmsg%3D0%26ts%3D1226148773097%3A1226148773386%3A1226148774868%26auth%3DDQAAAIcAAAC1pPE1QT4chKgrU4B3oyKZrQRkEVPtYlclpESQoXV_d9x9gdoe75Z0hfJ_22Pn5tVMR7j-uV5YCps3NB48L0bFlDeX-4PGHVT6Loztp_ru3tAy_gxDa9_YAEbz4d9CO4wD2VTKtzax9zvpGgrnJVZQfoWPkkIomUmxDtVGoH7g3fA3UjS0vdBJ2PJtgFMElso

Replace .co.in with your tld specific to your country. If you paste this url in any browser, it’ll directly log you in and you can do whatever you want to that account. Remember that all such urls remains valid only for two minutes. So, if you use that url after two minutes, it’ll lead nowhere.

At the time of writing this post Orkut, Google Docs, Google Calendar, Google Books and Youtube are vulnerable.

So, make sure your squid has stripping mechanism turned on and your squid server is properly firewalled.

You can watch the Video proof for Orkut on Blip.tv, Youtube.

We (the yum people) are organising Yum Bug Day on May 30, 2008. We try to kill as much bugs as possible. For a list of bugs, check Yum Bugs and Yum-Utils Bugs. If you think you can fix, provide info about one or more or you have any suggestions, just drop in #yum on freenode.net or shoot a mail at yum-devel.

In Seth’s words,

Yum Bug Day!
It’s exciting! It’s Fun! You get to tell people things like: Already
fixed, WONTFIX, CANTFIX, NOTABUG, and ‘ooo yah, that’s pretty broken’.

So, what are you waiting for??

Step 1:

Get the KDE4 rpms from rpmfind.net . Here is the list of all the kde4 rpms that you need to download from rpmfind.net.

Step 2:

Enable the fedora development repository. In '/etc/yum.repos.d/fedora-development.repo' file check if enabled is equal to 1 for development repo. If its zero, then change it to 1.

Step 3:

Use yum to install the kde rpms that you have downloaded.

[root@bordeaux KDE4_RPMS]# yum install *.rpm [Enter]  (do as root)

Note: After the KDE4 rpms are up in the fedora repos, then you can skip the step 1 and directly install kde by issuing the command

[root@bordeaux saini]# yum install kde* [Enter] (do as root)

My Experience

I was expecting a lot from KDE4. But a lot of things went wrong. When I logged into KDE4 for the first time, everything was looking awesome and very sharp. But then I faced the first crash while editing the settings for a widget and I realized that its not possible to have a crash free KDE application. After upgrade ( which cost me around 1GB of downloading via yum) and spending a lot of time manually downloading the packages, all I got was a desktop environment which will crash frequently to remind that you just wasted 1GB of bandwidth.

After upgrading, Kopete stopped working due to some conflict in ssl libraries, xchat is also not working due to some other library conflicts, dolphin the new file manager for KDE doesn’t even start and flush all kind of errors and faults when launched from command line. After the first crash the panel disappeared and I couldn’t get it back. Launching kicker returns the kde3 panel.

KDE4 is awesome when you just sit back and look at it. But when you want to work with some apps, its miserable. One of my friend had this status message on gtalk ‘ KDE4 : KDE3.5.8 :: Vista : XP ‘. KDE4 is as good as Vista when it comes to looks but its equally bad as Vista as compared to XP when it comes to work with it.

Conclusion: Don’t upgrade to KDE4 and wait till May, 2008 when KDE4 will be shipped with Fedora 9. I hope that KDE4 will not crash frequently when it’ll be embedded natively.

Here are some screen shots if you wanna have a look

It worked fine for Fedora Core 6 because compat-libstdc++-33 is provided by default in Fedora Core 6.

But its kind of strange that if libstdc++.so.5 and hence compat-libstdc++-33 is required for jdk-6u2 then why ‘rpm -ivh’ didn’t give dependency error.