After a night out I was about to go to bed when I saw the news that ATI has released a new version of ATI Catalyst™ 9.8 Proprietary Linux x86 Display Driver, its proprietary display drivers for Linux. I immediately downloaded the drivers to test with my Fedora 11 as I am getting more and more desperate to watch HD Movies 😐 Installed them on a manually compiled kernel 2.6.27 and the build failed 🙁 Installed the latest kernel version (for fedora 11) 184.108.40.206.xxx and build failed yet another time. Switched back to 2.6.27 and tried to build again. This time build was successful. Everything worked as expected. I was getting 1500FPS with glxgears and 300FPS with fgl_glxgears. But after sometime display hanged inturn freezing the system. Hard reboot was the only solution and then this happened for a few times in a row. Now, I am back to radeonhd, waiting for yet another release of ATI drivers so that I can try them yet another time to see yet another failure 🙁
Well, I was getting bored and just googled my domain name. As I was browsing through the search results, I clicked on a Spanish site containing the word gofedora. I clicked on google’s “Translate this page” and was surprised by the result. Watch it yourself below.
Yesterday, AMD released ATI Catalyst™ 9.7 Proprietary Linux x86/x86_64 Display Drivers. I happened to checkout the website today. Initially I was very excited about it hoping that these drivers will work with 2.6.29+ and I’ll be able to use my ATI Radeon HD 3200 which is lying dead since a fortnight or so. I downloaded the drivers immediately and switched to Fedora 11 default kernel. Installed the drivers and checked the install log located at /usr/share/ati/fglrx-install.log. And I saw a failure. AMD disappointed me, yet another time 🙁
In case you happen to screw your graphics display while trying to install ATI drivers, use the following command to uninstall fglrx.
There is a vulnerability in the way Google authentication service works. Whenever you login to any of the Google’s online services like GMail, Orkut, Groups, Docs, Youtube, Calendar etc., you are redirected to an authentication server which authenticates against the entered username and password and redirect back to the required service (GMail, Youtube etc.) setting the session variables.
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.
So, after turning stripping mechanism off, the log will contain urls which will look like this
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.