I recently heard about some vulnerability in older versions of OpenSSL i.e. before 1.1.1i . I checked my servers and found that most have either 1.1.0l or 1.1.1f . The recommended update version was 1.1.1i . Checked for Ubuntu DEB packages for 1.1.1i and found no mention in Ubuntu site. In Debian site the versions 1.1.1i-1 is in Testing and 1.1.1i-2 is in Unstable Stage. Found there is an official TAR package from OpenSSL  If I install the TAR file should it cause problems for any other ubuntu software dependent on OpenSSL ubuntu package? I know that by installing the TAR file I have to handle future update/upgrades manually. Should I install or upgrade 1.1.1i from the TAR file only or wait for Ubuntu to release the update for 1.1.1i?
121026
I just read a description of CVE-2020-1971, which indicates that a patch was released today for openSSL, the patched version is 1.1.1i -- my version of Ubuntu 20.04.1 LTS is running openSSL version 1.1.1f.  From last March. Software Updater says that my system is up to date.  I am hoping that this openSSL update is released by Canonical by tomorrow... can anyone confirm they are working on this?
52943
My understanding is that Ubuntu is based on Debian. For example, on the Wikipedia page for Ubuntu it states "" How can I find out what version of Debian a particular version of Ubuntu is based on (if any)?  For example, the current stable release of Ubuntu is "" (17.10) which announces that it is based on the Linux 4.13 kernel, but does not seem to say anything about the Debian version.  The current stable release of Debian is code named "" (9.2) which advertises a 4.9 kernel (on the afore-linked Stretch page). How can I find out the details of the relationship between them? Is there a particular command that will reveal this information?
35182
I try to compile the latest version but I get this error message.   $ make OPENSSL=/usr/local/ssl Makefile:82: ../aolserver/include/Makefile.module: No such file or directory make: *** No rule to make target '../aolserver/include/Makefile.module'.  Stop.   What should I do about it?
24538
So, today is July 21st and . gives me an option to download 16.04.1 LTS. However, attempting to upgrade gets me this message -  $ sudo do-release-upgrade Checking for a new Ubuntu release No new release found   What is wrong? Does it matter that I am running apt-get update behind apt-cacher-ng?  Note: Commenting out the files in apt.conf.d that used apt-cacher-ng did not make a difference.  Edit: Explanation for possible duplicates:  deals with upgrade from 12.04LTS to 14.04LTS. My question is specific to 14.04 LTS to 16.04.1 LTS upgrade. Old answers, while good for archival purposes are less relevant in a fast changing package like ubuntu. Moreover none of the answers answer what is wrong. The link  pointed out is mentioned in one of the comments. This Q &amp; A is more helpful for people upgrading today than the work around mentioned in "".
10307
I wanted to upgrade to 14.04.2 point release from 14.04.  What I did was:  sudo apt-get update &amp;&amp; sudo apt-get upgrade &amp;&amp;  sudo apt-get dist-upgrade -y   Then I wanted to upgrade to 3.16 kernel, since it wasn't done with the the above command, so what I did was:  sudo apt-get install linux-generic-lts-utopic xserver-xorg-lts-utopic libegl1-mesa-drivers-lts-utopic xserver-xorg-video-all-lts-utopic xserver-xorg-input-all-lts-utopic sudo apt-get install linux-signed-generic-lts-utopic   Now when I do:   uname -a I get   Linux Y500 3.16.0-33-generic #44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux  cat /etc/os-release | grep VERSION= I get  VERSION="14.04.2 LTS, Trusty Tahr"   And when I do lsb_release -a I get  Distributor ID: Ubuntu Description:    Ubuntu 14.04.2 LTS Release:    14.04 Codename:   trusty   I know that uname -a and lsb_release -a both refer to different info, but why does  cat /etc/os-release | grep VERSION= show different version?
59114
1.I have downloaded the linux version from  2. Right click on the file (truecrypt-7.1a-linux-x86.tar.gz), ->Open with Archive Manager. 3. Double click on the extracted file (truecrypt-7.1a-setup-x86), nothing happens.   Someone can help me installing truecrypt on ubuntu 14.04 LTS 32 bit?   SOLUTION!! The extracted file works if in the terminal is typed: ./truecrypt-7.1a-setup-x86
123285
What happens if there is a security problem in a package in the universe repository four years after the 12.04 LTS release; will the package be updated from upstream, patched, or left alone?  It's my understanding that the "5 years of support &amp; security updates" applies only to the core of Ubuntu -- anything in Main repository.  Not for things in the Universe repository.    For a more specific example -- if I install Ruby now, and want to use it for the next several years on 12.04 and it has a security vulnerability; while this might be patched in the upstream (so I could always download the latest from their website and compile it myself or use a PPA), will this upstream fix be migrated into the precise package repositories? What about backports?
13840
I read these two threads:         And I got a little bit worried, is my Ubuntu machine safe? Or am I vulnerable to this vulnerability?  The second article mentioned that:     The flaw actually resided in the way Samba handled shared libraries.   The other thing that they say is all versions from versions 3.5.0 onwards since 2010 are vulnerable.     At that time, nearly 485,000 Samba-enabled computers were found to be exposed on the Internet, and researchers predicted that the SambaCry-based attacks also have potential to spread just like WannaCry ransomware widely.   .   I don't have a samba server however I've got samba-libs package installed.  What, if anything, should I do?  I'm running Ubuntu 16.04.
35045
The ia32-libs package is no longer present in Ubuntu 12.04 repositories for a 64bit system. Are there any available replacement packages available for download?
7857
I read about a security flaw in Git, which was fixed in version 2.2.1. I currently have Git 2.1.0 on my system (Ubuntu 14.10), and tried to reinstall it with apt. However, apt told me that I currently have the latest version.  The Git website does not have prebuilt versions for Linux. They say that you can install it with package managers. Without building from source, how would I install the latest version of Git?
10885
Critical Updates there is no Update Name   (Require TLS 1.1 or higher for HTTPS connections" in that list)   any help will be appreciated
14740
I can't find any documentation on upgrading 16.04 to 16.04.1.  I'm assuming having all the package updates does it, but Details is still reporting 16.04 and there is still a 'developer options' tab in Software &amp; Updates, implying I'm still in some experimental release.
90355
I have an Ubuntu 12.04 server. I have updated the OpenSSL package in order to fix the heartbleed vulnerability. But I am still vulnerable even, even though I have restarted the web server, and even the whole server.  To check my vulnerability I used:       dpkg gives:  dpkg -l |grep openssl ii  openssl  1.0.1-4ubuntu5.12   Secure Socket Layer (SSL) binary and related cryptographic tools   (launchpad.net/ubuntu/+source/openssl/1.0.1-4ubuntu5.12)
95592
Lately whenever I run software update I get the message    suggesting that my version of Ubuntu is EOL. But when I run lsb_release -a I get  No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 14.04.5 LTS Release:    14.04 Codename:   trusty   Which of these numbers should I pay attention to? 14.04 or 14.04.5? Because according to the  support for 14.04.5 runs out on April 2019.
7933
After upgrading to 14.04, my kernel is not upgraded! it's like before:  Linux Boxi 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux  Here's what I did:  sudo apt-get update sudo apt-get dist-upgrade sudo do-release-upgrade sudo apt-get update sudo apt-get dist-upgrade     lsb_release -a  No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 14.04 LTS Release:    14.04 Codename:   trusty
41479
The snap packaging format finally frees us from dependency hell by allowing each package to have its own copy of dependencies. I'm interested in the technical details in how it does this. How does it handle:   snaps depending on the version of a library already installed via deb packages for the current release? Does it ignore the installed library? different snaps specifying the same version of the same library? Does it do deduplication somehow? updates to core libraries that are likely to be used by a lot of snaps? OpenSSL comes to mind as a huge pain point.   xdg-app has something called :     A fundamental concept in xdg-app is the runtime/application split.   Every app depends on a runtime, which supplies the core libraries that   the app relies on. Runtimes are typically shared by many applications,   but a user can have multiple runtimes installed at the same time.   It seems that in the case of OpenSSL, it would be part of the runtime in xdg-apps, so an update to OpenSSL should transparently affect all xdg-apps using the same runtime.
100332
Actually not debian, but Raspbian Wheezy to Raspbian Jessie. I upgrade it using some commands which found on Raspbian official forum.  cat /etc/debian_version = 8.0.  The problem is, I can't view any result when I restart the service.  Before upgrade(Wheezy):  # service tor restart [ok] cccc [ok] ddd # _   After upgrade(Jessie):  # service tor restart # _   And all results are written to /var/log/syslog... How can I revert this thing? I want to see actual result, not written to log.