Wednesday, April 9, 2014

Acquia Cloud password reset due to the heartbleed bug

On 7 April 2014, a flaw in software that is widely used to secure Web communications was disclosed. The Heartbleed bug introduced a security vulnerability (http://heartbleed.com) in the widely used OpenSSL cryptographic library. Acquia resolved this vulnerability on all servers within hours of learning of the issue. In addition, we recommend that the following steps be performed as soon as possible.

For any SSL-protected Drupal sites on Acquia Cloud where you were managing the SSL certificate, rekey your SSL certs as per https://docs.acquia.com/articles/how-do-i-rekey-my-ssl-certificate. This step does not apply to customers with Acquia-managed certificates.
For any SSL-protected Drupal sites not hosted with Acquia, rekey your SSL cert by following your hosting provider's instructions
Reset your Drupal site(s) admin passwords
Reset your Acquia password as follows:
Log in at https://accounts.acquia.com
Change password at https://accounts.acquia.com/account/password/change
Review your Acquia Cloud site's SSH keys and team members to ensure they appear as expected
Please note: Acquia has scanned the Acquia Cloud and Acquia Network and found no evidence to suggest user credentials or other sensitive information have been compromised. We are recommending that you update your passwords as described above as a precaution.

For additional background information, see our article on the Heartbleed bug. https://docs.acquia.com/articles/heartbleed-acquia-cloud.

Please contact the Acquia Client Advisory team if you have any questions by logging in to https://insight.acquia.com and visiting the Acquia Help Center.

Thank you,

Acquia Client Advisory Team

The Heartbleed Bug

The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SS


L/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.

What leaks in practice?

We have tested some of our own services from attacker's perspective. We attacked ourselves from outside, without leaving a trace. Without using any privileged information or credentials we were able steal from ourselves the secret keys used for our X.509 certificates, user names and passwords, instant messages, emails and business critical documents and communication.

How to stop the leak?

As long as the vulnerable version of OpenSSL is in use it can be abused. Fixed OpenSSL has been released and now it has to be deployed. Operating system vendors and distribution, appliance vendors, independent software vendors have to adopt the fix and notify their users. Service providers and users have to install the fix as it becomes available for the operating systems, networked appliances and software they use.

Q&A

What is the CVE-2014-0160?

CVE-2014-0160 is the official reference to this bug. CVE (Common Vulnerabilities and Exposures) is the Standard for Information Security Vulnerability Names maintained by MITRE. Due to co-incident discovery a duplicate CVE, CVE-2014-0346, which was assigned to us, should not be used, since others independently went public with the CVE-2014-0160 identifier.

Why it is called the Heartbleed Bug?

Bug is in the OpenSSL's implementation of the TLS/DTLS (transport layer security protocols) heartbeat extension (RFC6520). When it is exploited it leads to the leak of memory contents from the server to the client and from the client to the server.

What makes the Heartbleed Bug unique?

Bugs in single software or library come and go and are fixed by new versions. However this bug has left large amount of private keys and other secrets exposed to the Internet. Considering the long exposure, ease of exploitation and attacks leaving no trace this exposure should be taken seriously.

Is this a design flaw in SSL/TLS protocol specification?

No. This is implementation problem, i.e. programming mistake in popular OpenSSL library that provides cryptographic services such as SSL/TLS to the applications and services.

What is being leaked?

Encryption is used to protect secrets that may harm your privacy or security if they leak. In order to coordinate recovery from this bug we have classified the compromised secrets to four categories: 1) primary key material, 2) secondary key material and 3) protected content and 4) collateral.

What is leaked primary key material and how to recover?

These are the crown jewels, the encryption keys themselves. Leaked secret keys allows the attacker to decrypt any past and future traffic to the protected services and to impersonate the service at will. Any protection given by the encryption and the signatures in the X.509 certificates can be bypassed. Recovery from this leak requires patching the vulnerability, revocation of the compromised keys and reissuing and redistributing new keys. Even doing all this will still leave any traffic intercepted by the attacker in the past still vulnerable to decryption. All this has to be done by the owners of the services.

What is leaked secondary key material and how to recover?

These are for example the user credentials (user names and passwords) used in the vulnerable services. Recovery from this leaks requires owners of the service first to restore trust to the service according to steps described above. After this users can start changing their passwords and possible encryption keys according to the instructions from the owners of the services that have been compromised. All session keys and session cookies should be invalided and considered compromised.

What is leaked protected content and how to recover?

This is the actual content handled by the vulnerable services. It may be personal or financial details, private communication such as emails or instant messages, documents or anything seen worth protecting by encryption. Only owners of the services will be able to estimate the likelihood what has been leaked and they should notify their users accordingly. Most important thing is to restore trust to the primary and secondary key material as described above. Only this enables safe use of the compromised services in the future.

What is leaked collateral and how to recover?

Leaked collateral are other details that have been exposed to the attacker in the leaked memory content. These may contain technical details such as memory addresses and security measures such as canaries used to protect against overflow attacks. These have only contemporary value and will lose their value to the attacker when OpenSSL has been upgraded to a fixed version.

Recovery sounds laborious, is there a short cut?

After seeing what we saw by "attacking" ourselves, with ease, we decided to take this very seriously. We have gone laboriously through patching our own critical services and are in progress of dealing with possible compromise of our primary and secondary key material. All this just in case we were not first ones to discover this and this could have been exploited in the wild already.

How revocation and reissuing of certificates works in practice?

If you are a service provider you have signed your certificates with a Certificate Authority (CA). You need to check your CA how compromised keys can be revoked and new certificate reissued for the new keys. Some CAs do this for free, some may take a fee.

Am I affected by the bug?

You are likely to be affected either directly or indirectly. OpenSSL is the most popular open source cryptographic library and TLS (transport layer security) implementation used to encrypt traffic on the Internet. Your popular social site, your company's site, commerce site, hobby site, site you install software from or even sites run by your government might be using vulnerable OpenSSL. Many of online services use TLS to both to identify themselves to you and to protect your privacy and transactions. You might have networked appliances with logins secured by this buggy implementation of the TLS. Furthermore you might have client side software on your computer that could expose the data from your computer if you connect to compromised services.

How widespread is this?

Most notable software using OpenSSL are the open source web servers like Apache and nginx. The combined market share of just those two out of the active sites on the Internet was over 66% according to Netcraft's April 2014 Web Server Survey. Furthermore OpenSSL is used to protect for example email servers (SMTP, POP and IMAP protocols), chat servers (XMPP protocol), virtual private networks (SSL VPNs), network appliances and wide variety of client side software. Fortunately many large consumer sites are saved by their conservative choice of SSL/TLS termination equipment and software. Ironically smaller and more progressive services or those who have upgraded to latest and best encryption will be affected most. Furthermore OpenSSL is very popular in client software and somewhat popular in networked appliances which have most inertia in getting updates.

What versions of the OpenSSL are affected?

Status of different versions:
  • OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
  • OpenSSL 1.0.1g is NOT vulnerable
  • OpenSSL 1.0.0 branch is NOT vulnerable
  • OpenSSL 0.9.8 branch is NOT vulnerable
Bug was introduced to OpenSSL in December 2011 and has been out in the wild since OpenSSL release 1.0.1 on 14th of March 2012. OpenSSL 1.0.1g released on 7th of April 2014 fixes the bug.

How common are the vulnerable OpenSSL versions?

The vulnerable versions have been out there for over two years now and they have been rapidly adopted by modern operating systems. A major contributing factor has been that TLS versions 1.1 and 1.2 came available with the first vulnerable OpenSSL version (1.0.1) and security community has been pushing the TLS 1.2 due to earlier attacks against TLS (such as the BEAST).

How about operating systems?

Some operating system distributions that have shipped with potentially vulnerable OpenSSL version:
  • Debian Wheezy (stable), OpenSSL 1.0.1e-2+deb7u4
  • Ubuntu 12.04.4 LTS, OpenSSL 1.0.1-4ubuntu5.11
  • CentOS 6.5, OpenSSL 1.0.1e-15
  • Fedora 18, OpenSSL 1.0.1e-4
  • OpenBSD 5.3 (OpenSSL 1.0.1c 10 May 2012) and 5.4 (OpenSSL 1.0.1c 10 May 2012)
  • FreeBSD 10.0 - OpenSSL 1.0.1e 11 Feb 2013
  • NetBSD 5.0.2 (OpenSSL 1.0.1e)
  • OpenSUSE 12.2 (OpenSSL 1.0.1c)
Operating system distribution with versions that are not vulnerable:
  • Debian Squeeze (oldstable), OpenSSL 0.9.8o-4squeeze14
  • SUSE Linux Enterprise Server
  • FreeBSD 8.4 - OpenSSL 0.9.8y 5 Feb 2013
  • FreeBSD 9.2 - OpenSSL 0.9.8y 5 Feb 2013
  • FreeBSD Ports - OpenSSL 1.0.1g (At 7 Apr 21:46:40 2014 UTC)

How can OpenSSL be fixed?

Even though the actual code fix may appear trivial, OpenSSL team is the expert in fixing it properly so latest fixed version 1.0.1g or newer should be used. If this is not possible software developers can recompile OpenSSL with the handshake removed from the code by compile time option -DOPENSSL_NO_HEARTBEATS.

Should heartbeat be removed to aid in detection of vulnerable services?

Recovery from this bug could benefit if the new version of the OpenSSL would both fix the bug and disable heartbeat temporarily until some future version. It appears that majority if not almost all TLS implementations that respond to the heartbeat request today are vulnerable versions of OpenSSL. If only vulnerable versions of OpenSSL would continue to respond to the heartbeat for next few months then large scale coordinated response to reach owners of vulnerable services would become more feasible.

Can I detect if someone has exploited this against me?

Exploitation of this bug leaves no traces of anything abnormal happening to the logs.

Can IDS/IPS detect or block this attack?

Although the content of the heartbeat request is encrypted it has its own record type in the protocol. This should allow intrusion detection and prevention systems (IDS/IPS) to be trained to detect use of the heartbeat request. Due to encryption differentiating between legitimate use and attack can not be based on the content of the request, but the attack may be detected by comparing the size of the request against the size of the reply. This seems to imply that IDS/IPS can be programmed to detect the attack but not to block it unless heartbeat requests are blocked altogether.

Has this been abused in the wild?

We don't know. Security community should deploy TLS/DTLS honeypots that entrap attackers and to alert about exploitation attempts.

Can attacker access only 64k of the memory?

There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed.

Is this a MITM bug like Apple's goto fail bug was?

No this doesn't require a man in the middle attack (MITM). Attacker can directly contact the vulnerable service or attack any user connecting to a malicious service. However in addition to direct threat the theft of the key material allows man in the middle attackers to impersonate compromised services.

Does TLS client certificate authentication mitigate this?

No, heartbeat request can be sent and is replied to during the handshake phase of the protocol. This occurs prior to client certificate authentication.

Does OpenSSL's FIPS mode mitigate this?

No, OpenSSL Federal Information Processing Standard (FIPS) mode has no effect on the vulnerable heartbeat functionality.

Does Perfect Forward Secrecy (PFS) mitigate this?

Use of Perfect Forward Secrecy (PFS), which is unfortunately rare but powerful, should protect past communications from retrospective decryption. Please seehttps://twitter.com/ivanristic/status/453280081897467905 how leaked tickets may affect this.

Can heartbeat extension be disabled during the TLS handshake?

No, vulnerable heartbeat extension code is activated regardless of the results of the handshake phase negotiations. Only way to protect yourself is to upgrade to fixed version of OpenSSL or to recompile OpenSSL with the handshake removed from the code.

Who found the Heartbleed Bug?

This bug was independently discovered by a team of security engineers (Riku, Antti and Matti) atCodenomicon and Neel Mehta of Google Security, who first reported it to the OpenSSL team. Codenomicon team found heartbleed bug while improving the SafeGuard feature in Codenomicon's Defensics security testing tools and reported this bug to the NCSC-FI for vulnerability coordination and reporting to OpenSSL team.

What is the Defensics SafeGuard?

The SafeGuard feature of the Codenomicon's Defensics security testtools automatically tests the target system for weaknesses that compromise the integrity, privacy or safety. The SafeGuard is systematic solution to expose failed cryptographic certificate checks, privacy leaks or authentication bypass weaknesses that have exposed the Internet users to man in the middle attacks and eavesdropping. In addition to the Heartbleed bug the new Defensics TLS Safeguard feature can detect for instance the exploitable security flaw in widely used GnuTLS open source software implementing SSL/TLS functionality and the "goto fail;" bug in Apple's TLS/SSL implementation that was patched in February 2014.

Who coordinates response to this vulnerability?

NCSC-FI took up the task of reaching out to the authors of OpenSSL, software, operating system and appliance vendors, which were potentially affected. However, this vulnerability was found and details released independently by others before this work was completed. Vendors should be notifying their users and service providers. Internet service providers should be notifying their end users where and when potential action is required.

Is there a bright side to all this?

For those service providers who are affected this is a good opportunity to upgrade security strength of the secret keys used. A lot of software gets updates which otherwise would have not been urgent. Although this is painful for the security community, we can rest assured that infrastructure of the cyber criminals and their secrets have been exposed as well.

Where to find more information?

This Q&A was published as a follow-up to the OpenSSL advisory, since this vulnerability became public on 7th of April 2014. The OpenSSL project has made a statement athttps://www.openssl.org/news/secadv_20140407.txt. NCSC-FI published an advisory athttps://www.cert.fi/en/reports/2014/vulnerability788210.html. Individual vendors of operating system distributions, affected owners of Internet services, software packages and appliance vendors may issue their own advisories.

References


Thursday, April 3, 2014

installing nodejs on linux mint

sudo apt-get install nodejs
[sudo] password for adm:
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following extra packages will be installed:
  libc-ares2 libev4 libv8-3.8.9.20
The following NEW packages will be installed:
  libc-ares2 libev4 libv8-3.8.9.20 nodejs
0 upgraded, 4 newly installed, 0 to remove and 5 not upgraded.
Need to get 2,213 kB of archives.
After this operation, 6,526 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com/ubuntu/ raring/main libc-ares2 amd64 1.9.1-3 [38.1 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ raring/universe libv8-3.8.9.20 amd64 3.8.9.20-2 [1,382 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ raring/universe libev4 amd64 1:4.11-1 [29.0 kB]
Get:4 http://archive.ubuntu.com/ubuntu/ raring/universe nodejs amd64 0.6.19~dfsg1-5ubuntu1 [764 kB]
Fetched 2,213 kB in 18s (117 kB/s)                                            
Selecting previously unselected package libc-ares2:amd64.
(Reading database ... 200591 files and directories currently installed.)
Unpacking libc-ares2:amd64 (from .../libc-ares2_1.9.1-3_amd64.deb) ...
Selecting previously unselected package libv8-3.8.9.20.
Unpacking libv8-3.8.9.20 (from .../libv8-3.8.9.20_3.8.9.20-2_amd64.deb) ...
Selecting previously unselected package libev4.
Unpacking libev4 (from .../libev4_1%3a4.11-1_amd64.deb) ...
Selecting previously unselected package nodejs.
Unpacking nodejs (from .../nodejs_0.6.19~dfsg1-5ubuntu1_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 1 added doc-base file...
Registering documents with scrollkeeper...
Setting up libc-ares2:amd64 (1.9.1-3) ...
Setting up libv8-3.8.9.20 (3.8.9.20-2) ...
Setting up libev4 (1:4.11-1) ...
Setting up nodejs (0.6.19~dfsg1-5ubuntu1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

the inxi -Sr command

 inxi -Sr
System:    Host: yourhostname
Kernel: 3.8.0-26-generic x86_64 (64 bit)
Desktop: Xfce 4.10.2
Distro: Linux Mint 15 Olivia
Repos:     Error: inxi does not support this feature for your distro yet.
http://forums.linuxmint.com/viewtopic.php?f=190&t=101876

the read line meant that my sourcs.list was empty!!


http://forums.linuxmint.com/viewtopic.php?p=794714#p794714

 deb http://packages.linuxmint.com olivia main upstream import #id:linuxmint_main
           deb http://archive.ubuntu.com/ubuntu raring main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu raring-updates main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ raring-security main restricted universe



N: Ignoring file 'official-package-repositories.list:' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
W: GPG error: http://packages.linuxmint.com olivia Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY d4534ehsg445t34gfe(some key)


http://www.webupd8.org/2009/11/what-to-do-when-keyserverubuntucom-is.html


the below solution did not work 
irst open a terminal then type or paste

sudo rm -r /var/lib/apt/lists
sudo mkdir -p /var/lib/apt/lists/partial
apt-get clean
apt-get update

- See more at: http://www.linux.com/learn/answers/view/1267-help--how-can-i-fix-this--i-cant-update#sthash.6mx0eyS1.dpuf
http://www.linux.com/learn/answers/view/1267-help--how-can-i-fix-this--i-cant-update



gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1
https://help.ubuntu.com/community/SecureApt
http://trog.qgl.org/20091030/troubleshooting-gnupg-gpg-no-ultimately-trusted-keys-found
https://wiki.debian.org/SecureApt

deb http://packages.linuxmint.com/ debian main upstream import
deb http://debian.linuxmint.com/latest testing main contrib non-free
deb http://debian.linuxmint.com/latest/security testing/updates main contrib non-free
deb http://debian.linuxmint.com/latest/multimedia testing main non-free
deb http://packages.linuxmint.com/ debian main import backport romeo upstream
deb http://ftp.debian.org/debian/ testing-proposed-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ testing-proposed-updates main contrib non-free
deb http://security.debian.org wheezy/updates main contrib non-free
deb-src http://security.debian.org wheezy/updates main contrib non-free
deb http://ftp.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.debian.org/debian/ testing main contrib non-free
deb http://ftp.debian.org/debian/ experimental main contrib non-free
deb http://http.us.debian.org/debian/ squeeze main contrib non-free
deb-src http://http.us.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free

apt.conf.d/ - DirectoryExists (2: No such file or directory)

W: Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)
W: Unable to read /etc/apt/preferences.d/ - DirectoryExists (2: No such file or directory)
Make a backup of your settings and reinstall. 


could not find a soltion online so i
opened the file director in linux mint
went to /etc/apt/ under file system
then opened the folder is root and created
two folders
apt.conf.d
and
preferences.d

some command i gave deleted these folders

solved!!

The below line was written on a forum which is not true. so STFU if you do not know 
Fixing the core of apt is mostly a really irritating procedure if even possible.

installing npm and nodejs on a linux desktop

sudo apt-get install -y python-software-properties python g++ make
sudo add-apt-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs



sudo apt-get install -y python-software-properties python g++ make
Reading package lists... Done
Building dependency tree      
Reading state information... Done
g++ is already the newest version.
g++ set to manually installed.
make is already the newest version.
python is already the newest version.
The following NEW packages will be installed:
  python-software-properties
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 19.3 kB of archives.
After this operation, 132 kB of additional disk space will be used.
Get:1 http://security.ubuntu.com/ubuntu/ raring-security/universe python-software-properties all 0.92.17.3 [19.3 kB]
Fetched 19.3 kB in 0s (28.0 kB/s)                    
Selecting previously unselected package python-software-properties.
(Reading database ... 198914 files and directories currently installed.)
Unpacking python-software-properties (from .../python-software-properties_0.92.17.3_all.deb) ...
Setting up python-software-properties (0.92.17.3) ...


sudo apt-get install nodejs
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following extra packages will be installed:
  libc-ares2 libev4 libv8-3.8.9.20
The following NEW packages will be installed:
  libc-ares2 libev4 libv8-3.8.9.20 nodejs
0 upgraded, 4 newly installed, 0 to remove and 5 not upgraded.
Need to get 2,213 kB of archives.
After this operation, 6,526 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
  libc-ares2 libv8-3.8.9.20 libev4 nodejs
Install these packages without verification [y/N]? n
E: Some packages could not be authenticated


http://askubuntu.com/questions/83472/i-cannot-solve-the-install-these-packages-without-verification-problem



http://askubuntu.com/questions/75565/why-am-i-getting-authentication-errors-for-packages-from-an-ubuntu-repository

sudo apt-key update
gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key " not changed
gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key " not changed
gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) " not changed
gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) " not changed
gpg: Total number processed: 4
gpg:              unchanged: 4




94% [Connecting to mirrors.liquidweb.com (69.167.187.144)]

sudo apt-get upgrade
Reading package lists... Done
Building dependency tree      
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
W: Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)
W: Unable to read /etc/apt/preferences.d/ - DirectoryExists (2: No such file or directory)


W: Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)


i tried this and get an error
http://getkickstrap.com/docs.html#/first-steps
https://www.npmjs.org/doc/README.html

for a newbie. How the F** do i run insall.sh when linux wants to open it in gedit


so after googling i tried  at the terminal

sh install.sh
npm cannot be installed without nodejs.
Install node first, and then try again.

Maybe node is installed, but not in the PATH?
Note that running as sudo can change envs.

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games


??? wft 

then i found this

 sudo apt-get install nodejs npm
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  javascript-common libc-ares-dev libc-ares2 libev-dev libev4 libjs-node-uuid
  libssl-dev libssl-doc libv8-3.8.9.20 libv8-dev node-abbrev node-block-stream
  node-fstream node-graceful-fs node-inherits node-ini node-lru-cache
  node-minimatch node-mkdirp node-node-uuid node-nopt node-request node-rimraf
  node-semver node-tar node-which nodejs-dev wwwconfig-common zlib1g-dev
Suggested packages:
  apache2 httpd mysql-client postgresql-client
The following NEW packages will be installed:
  javascript-common libc-ares-dev libc-ares2 libev-dev libev4 libjs-node-uuid
  libssl-dev libssl-doc libv8-3.8.9.20 libv8-dev node-abbrev node-block-stream
  node-fstream node-graceful-fs node-inherits node-ini node-lru-cache
  node-minimatch node-mkdirp node-node-uuid node-nopt node-request node-rimraf
  node-semver node-tar node-which nodejs nodejs-dev npm wwwconfig-common
  zlib1g-dev
0 upgraded, 31 newly installed, 0 to remove and 5 not upgraded.
Need to get 5,954 kB of archives.
After this operation, 18.6 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
  libc-ares2 wwwconfig-common javascript-common libjs-node-uuid zlib1g-dev
  libv8-3.8.9.20 libev4 nodejs node-node-uuid libc-ares-dev libev-dev
  libv8-dev node-abbrev node-inherits node-block-stream node-rimraf
  node-mkdirp node-graceful-fs node-fstream node-ini node-lru-cache
  node-minimatch node-nopt node-request node-semver node-tar node-which
  nodejs-dev npm
Install these packages without verification [y/N]? y

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Wednesday, April 2, 2014

unmet dependencies linux-headers-3.2.0-60-generic

The following packages have unmet dependencies:
 linux-headers-3.2.0-60-generic : Depends: linux-headers-3.2.0-60 but it is not going to be installed


this helped

sudo apt-get autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libdmapsharing-3.0-2 libtelepathy-farstream2 libvncserver0
  linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic
  linux-headers-3.2.0-43-generic-pae linux-headers-3.2.0-44
  linux-headers-3.2.0-44-generic linux-headers-3.2.0-44-generic-pae
  linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic
  linux-headers-3.2.0-45-generic-pae linux-headers-3.2.0-48
  linux-headers-3.2.0-48-generic linux-headers-3.2.0-48-generic-pae
  linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic
  linux-headers-3.2.0-51-generic-pae linux-headers-3.2.0-52
  linux-headers-3.2.0-52-generic linux-headers-3.2.0-52-generic-pae
  linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic
  linux-headers-3.2.0-53-generic-pae linux-headers-3.2.0-54
  linux-headers-3.2.0-54-generic linux-headers-3.2.0-54-generic-pae
  linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic
  linux-headers-3.2.0-55-generic-pae linux-headers-3.2.0-56
  linux-headers-3.2.0-56-generic linux-headers-3.2.0-56-generic-pae
  linux-headers-3.2.0-57 linux-headers-3.2.0-57-generic
  linux-headers-3.2.0-57-generic-pae linux-headers-3.2.0-58
  linux-headers-3.2.0-58-generic linux-headers-3.2.0-58-generic-pae
  mplayer-skins openjdk-7-jre-lib python-central python-mako python-markupsafe
  rhythmbox-data



debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
(Reading database ... 1145345 files and directories currently installed.)
Removing libdmapsharing-3.0-2 ...
Removing libtelepathy-farstream2 ...
Removing libvncserver0 ...
Removing linux-headers-3.2.0-43-generic-pae ...
Removing linux-headers-3.2.0-43-generic ...
Removing linux-headers-3.2.0-43 ...
Removing linux-headers-3.2.0-44-generic-pae ...
Removing linux-headers-3.2.0-44-generic ...
Removing linux-headers-3.2.0-44 ...
Removing linux-headers-3.2.0-45-generic-pae ...
Removing linux-headers-3.2.0-45-generic ...
Removing linux-headers-3.2.0-45 ...
Removing linux-headers-3.2.0-48-generic-pae ...
Removing linux-headers-3.2.0-48-generic ...
Removing linux-headers-3.2.0-48 ...
Removing linux-headers-3.2.0-51-generic-pae ...
Removing linux-headers-3.2.0-51-generic ...
Removing linux-headers-3.2.0-51 ...
Removing linux-headers-3.2.0-52-generic-pae ...
Removing linux-headers-3.2.0-52-generic ...
Removing linux-headers-3.2.0-52 ...
Removing linux-headers-3.2.0-53-generic-pae ...
Removing linux-headers-3.2.0-53-generic ...
Removing linux-headers-3.2.0-53 ...
Removing linux-headers-3.2.0-54-generic-pae ...
Removing linux-headers-3.2.0-54-generic ...
Removing linux-headers-3.2.0-54 ...
Removing linux-headers-3.2.0-55-generic-pae ...
Removing linux-headers-3.2.0-55-generic ...
Removing linux-headers-3.2.0-55 ...
Removing linux-headers-3.2.0-56-generic-pae ...
Removing linux-headers-3.2.0-56-generic ...
Removing linux-headers-3.2.0-56 ...
Removing linux-headers-3.2.0-57-generic-pae ...
Removing linux-headers-3.2.0-57-generic ...
Removing linux-headers-3.2.0-57 ...
Removing linux-headers-3.2.0-58-generic-pae ...
Removing linux-headers-3.2.0-58-generic ...
Removing linux-headers-3.2.0-58 ...
Removing mplayer-skins ...
Removing openjdk-7-jre-lib ...
Removing python-central ...
Removing python-mako ...
Removing python-markupsafe ...
Removing rhythmbox-data ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for man-db ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing man-db (--remove):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
                                                              Processing triggers for hicolor-icon-theme ...
Processing triggers for libglib2.0-0 ...
Errors were encountered while processing:
 man-db
E: Sub-process /usr/bin/dpkg returned an error code (1)


 sudo dpkg --configure -a
Setting up man-db (2.6.1-2ubuntu1) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing man-db (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 man-db
http://askubuntu.com/questions/191235/i-cannot-install-or-remove-packages

sudo apt-get update
sudo apt-get install -f
sudo apt-get autoremove
sudo apt-get clean

https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1265262


sudo apt-get remove --purge getdeb-repositoryReading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package getdeb-repository

http://askubuntu.com/questions/191235/i-cannot-install-or-remove-packages

http://askubuntu.com/questions/440249/only-showing-3-1gb-ram-and-not-8gb

ubuntu updaTE ERROR



sudo apt-get clean
sudo apt-get update
sudo apt-get install -f

http://ubuntuforums.org/showthread.php?t=2213658












x@xe-G41x2L:~$ sudo  apt-get install -f
Reading package lists... Done
Building dependency tree    
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.2.0-43-generic-pae linux-headers-3.2.0-52-generic
  python-mako linux-headers-3.2.0-58-generic-pae
  linux-headers-3.2.0-55-generic mplayer-skins
  linux-headers-3.2.0-55-generic-pae linux-headers-3.2.0-43
  linux-headers-3.2.0-44 linux-headers-3.2.0-45 linux-headers-3.2.0-51
  linux-headers-3.2.0-52 linux-headers-3.2.0-53 linux-headers-3.2.0-48
  linux-headers-3.2.0-54 linux-headers-3.2.0-55 linux-headers-3.2.0-56
  linux-headers-3.2.0-57 linux-headers-3.2.0-58 linux-headers-3.2.0-58-generic
  linux-headers-3.2.0-52-generic-pae libvncserver0
  linux-headers-3.2.0-45-generic linux-headers-3.2.0-44-generic-pae
  rhythmbox-data libdmapsharing-3.0-2 linux-headers-3.2.0-53-generic
  linux-headers-3.2.0-48-generic python-markupsafe
  linux-headers-3.2.0-56-generic-pae linux-headers-3.2.0-56-generic
  libtelepathy-farstream2 python-central linux-headers-3.2.0-53-generic-pae
  linux-headers-3.2.0-48-generic-pae linux-headers-3.2.0-43-generic
  linux-headers-3.2.0-45-generic-pae linux-headers-3.2.0-51-generic
  linux-headers-3.2.0-54-generic linux-headers-3.2.0-57-generic-pae
  linux-headers-3.2.0-54-generic-pae linux-headers-3.2.0-57-generic
  linux-headers-3.2.0-44-generic linux-headers-3.2.0-51-generic-pae
  openjdk-7-jre-lib
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  linux-headers-3.2.0-60
The following NEW packages will be installed:
  linux-headers-3.2.0-60
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 0 B/11.7 MB of archives.
After this operation, 56.3 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 1131464 files and directories currently installed.)
Unpacking linux-headers-3.2.0-60 (from .../linux-headers-3.2.0-60_3.2.0-60.91_all.deb) ...
dpkg: error processing /var/cache/apt/archives/linux-headers-3.2.0-60_3.2.0-60.91_all.deb (--unpack):
 unable to create `/usr/src/linux-headers-3.2.0-60/arch/alpha/include/asm/kmap_types.h.dpkg-new' (while processing `./usr/src/linux-headers-3.2.0-60/arch/alpha/include/asm/kmap_types.h'): No space left on device
No apport report written because MaxReports is reached already
                                                              dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-headers-3.2.0-60_3.2.0-60.91_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)




http://askubuntu.com/questions/432369/how-to-fix-upgrade-install-failure-loop-due-to-disk-space-issue

Building dependency tree    
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 linux-headers-3.2.0-60-generic : Depends: linux-headers-3.2.0-60 but it is not installed

 sudo dpkg --configure -a
dpkg: dependency problems prevent configuration of linux-headers-3.2.0-60-generic:
 linux-headers-3.2.0-60-generic depends on linux-headers-3.2.0-60; however:
  Package linux-headers-3.2.0-60 is not installed.
dpkg: error processing linux-headers-3.2.0-60-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-3.2.0-60-generic; however:
  Package linux-headers-3.2.0-60-generic is not configured yet.
dpkg: error processing linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 3.2.0.60.71); however:
  Package linux-headers-generic is not configured yet.
dpkg: error processing linux-generic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-3.2.0-60-generic
 linux-headers-generic
 linux-generic

 sudo apt-get autoremove -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  linux-headers-3.2.0-60
The following packages will be REMOVED:
  libdmapsharing-3.0-2 libtelepathy-farstream2 libvncserver0
  linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic
  linux-headers-3.2.0-43-generic-pae linux-headers-3.2.0-44
  linux-headers-3.2.0-44-generic linux-headers-3.2.0-44-generic-pae
  linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic
  linux-headers-3.2.0-45-generic-pae linux-headers-3.2.0-48
  linux-headers-3.2.0-48-generic linux-headers-3.2.0-48-generic-pae
  linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic
  linux-headers-3.2.0-51-generic-pae linux-headers-3.2.0-52
  linux-headers-3.2.0-52-generic linux-headers-3.2.0-52-generic-pae
  linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic
  linux-headers-3.2.0-53-generic-pae linux-headers-3.2.0-54
  linux-headers-3.2.0-54-generic linux-headers-3.2.0-54-generic-pae
  linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic
  linux-headers-3.2.0-55-generic-pae linux-headers-3.2.0-56
  linux-headers-3.2.0-56-generic linux-headers-3.2.0-56-generic-pae
  linux-headers-3.2.0-57 linux-headers-3.2.0-57-generic
  linux-headers-3.2.0-57-generic-pae linux-headers-3.2.0-58
  linux-headers-3.2.0-58-generic linux-headers-3.2.0-58-generic-pae
  mplayer-skins openjdk-7-jre-lib python-central python-mako python-markupsafe
  rhythmbox-data
The following NEW packages will be installed:
  linux-headers-3.2.0-60
0 upgraded, 1 newly installed, 45 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 0 B/11.7 MB of archives.
After this operation, 895 MB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 1131464 files and directories currently installed.)
Unpacking linux-headers-3.2.0-60 (from .../linux-headers-3.2.0-60_3.2.0-60.91_all.deb) ...
dpkg: error processing /var/cache/apt/archives/linux-headers-3.2.0-60_3.2.0-60.91_all.deb (--unpack):
 unable to create `/usr/src/linux-headers-3.2.0-60/arch/alpha/include/asm/sections.h.dpkg-new' (while processing `./usr/src/linux-headers-3.2.0-60/arch/alpha/include/asm/sections.h'): No space left on device
No apport report written because MaxReports is reached already
                                                              dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-headers-3.2.0-60_3.2.0-60.91_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
http://askubuntu.com/questions/141370/how-to-fix-a-broken-package-when-apt-get-install-f-does-not-work
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1281800

sudo apt-get update
sudo apt-get upgrade && sudo apt-get dist-upgrade
sudo dpkg-reconfigure -a
sudo dpkg --configure -a
sudo update-initramfs -u