ubuntu14.04

Ubuntu updater unable to find public key

Posted on by littlenotes

Problem: The user was unable to update ubuntu due the error shown below-

pmt@v-ng-01dd:~$ sudo apt-get update
[sudo] password for pmt:
Get:1 ftp://mirror.cse.iitk.ac.in trusty-updates Release.gpg [933 B]
<snip> … <snip>

Hit ftp://mirror.cse.iitk.ac.in trusty-security/universe Translation-en
Fetched 855 kB in 48s (17.8 kB/s)
Reading package lists… Done
W: There is no public key available for the following key IDs:
3B4FE6ACC0B21F32
W: There is no public key available for the following key IDs:
3B4FE6ACC0B21F32
W: There is no public key available for the following key IDs:
3B4FE6ACC0B21F32
W: There is no public key available for the following key IDs:
3B4FE6ACC0B21F32

Solution:

pmt@v-ng-01dd:~$ sudo apt-get install debian-keyring debian-archive-keyring
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following NEW packages will be installed:
debian-archive-keyring debian-keyring
0 upgraded, 2 newly installed, 0 to remove and 1309 not upgraded.
Need to get 48.7 MB of archives.
<snip> … <snip>
Setting up debian-archive-keyring (2012.4) …
Setting up debian-keyring (2014.03.03) …
pmt@v-ng-01dd:~$ sudo apt-key update
gpg: key 437D05B5: “Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>” not changed
gpg: key FBB75451: “Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>” not changed
gpg: Total number processed: 2
gpg:              unchanged: 2
pmt@v-ng-01dd:~$

root@v-ng-01dd:~# gpg –recv-keys 3B4FE6ACC0B21F32

root@v-ng-01dd:~# gpg –export 3B4FE6ACC0B21F32 | apt-key add –

Reference:

  1. http://www.linuxquestions.org/questions/debian-26/there-is-no-public-key-available-for-the-following-key-id-705108/
  2. http://gnuru.org/article/1486/debian-public-keys-error-2

Unable to ssh after upgrading to ubuntu 14.04

Posted on by littlenotes

Problem: A colleague had got Ubuntu 14.04 installed on her desktop.  Post-installation, the sysads were unable to ssh to the m/c using PuTTY.  Since, the team uses a combination of Windows and Linux desktops, we needed this to work.

Solution: Apparently, post-installation the sysads updated the m/c (sudo apt-get update) without setting https_proxy.  So, the two steps that got the issue resolved were-

  1. export http_proxy and https_proxy to point to the proxy server
  2. sudo apt-get update
  3. Add following line to /etc/sshd_config in the “#Authentication” section

#PermitRootLogin without-password
PermitRootLogin yes