eXTReMe Tracker

Installing Google Chrome in Karmic (Ubuntu 9.10)

 Linux and OSS  1 Response »
Nov 172009
 

I followed the procedure outlined by UbuntuGeek, but some of the things are little different – at least when I installed it today.

First, you’ll need to add the repository which contains the deb for Chrome.

sudo gedit /etc/apt/sources.list

Assuming you are running Karmic Koala (Ubuntu 9.10), you’ll need to add the following two lines towards the end of that file.

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu karmic main
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu karmic main

Next, you’ll have to retrieve the PGP keys for this repository.

sudo add-apt-repository ppa:chromium-daily/ppa

Update the sources,

sudo apt-get update

And then instal Chrome

sudo apt-get install chromium-browser

After the installation is successful, you can launch the browser, and import settings from Mozilla Firefox. However, Firefox needs to be closed when the importing of options and favourites is taking place. When Chrome restarts, it will have options configured like you had them in Firefox. The are no add-ons that I could find for Chrome, though – Adblock Plus and Video Download Helper are the two plugins that would make me stick with Firefox for a while.

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED

 Linux and OSS  1 Response »
Nov 102009
 

Sometimes when you change some of the IP settings, or are using a different wireless card on a machine that has been registered with a server, and for many other reasons, you might have encountered a warning which would’ve looked like this:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
f2:92:1d:da:81:2a:d7:16:0a:48:f0:43:20:1c:f4:b5
………………..

The simplest way to deal with this is to remove the ~/.ssh folder, however this clears out all the exchanged keys with all the ssh machines you have ever communicated with. Removing the ~/.ssh folder would mean that each time you reconnect to a SSH server that you have previously connected to, you will have to confirm that the connection is secure and all that.

There is however another simple way to change just the entry for a specific server in question. At the terminal type in -

ssh-keygen -R name_of_the_server.com

name_of_the_server.com in the above example would need to be replaced by the actual server name that you are trying to connect.