and got the same results as you. How can it be built on January 8th if the patch was just made today?
[EDIT] running
sudo aptitude upgrade
upgraded properly and now I'm getting a version that was compiled earlier today. I'm guessing I needed to update another package as well. Probably `libssl`?
I got a "security warning" update when I logged in to the server (good), ran apt-get and installed, did openssl version, got the string as noted above (which seemed just a tad out of date).
So... I built and installed from source, and got... the same string.
This is the standard command:
@stormbrew is correct about ubuntu, use -a or -v -b
I'm totally confused by this. I'm running ubuntu LTS 12.04 and did
and then ran
and got the same results as you. How can it be built on January 8th if the patch was just made today?
[EDIT] running
upgraded properly and now I'm getting a version that was compiled earlier today. I'm guessing I needed to update another package as well. Probably `libssl`?
3 replies →
As far as I can tell, on ubuntu this reports "OpenSSL 1.0.1 14 Mar 2012" for all ubuntu versions, including the fixed one.
With "openssl version -a" you can see the built time.
Same here.
I got a "security warning" update when I logged in to the server (good), ran apt-get and installed, did openssl version, got the string as noted above (which seemed just a tad out of date).
So... I built and installed from source, and got... the same string.
Annoying.
My Linux Mint machine (based on 13.10) went from 1.0.1e Feb 2014 to 1.01 Mar 2012 int the last 2 hours, so that's definitely new.
1 reply →
try: dpkg -s openssl