Help upgrading OpenSSL 1.0.1_8 to 1.0.1g

The latest version in the ports tree is 1.0.1g. So make sure your ports tree is up to date and rebuild the port using your favourite method.
 
Sorry for posting in the wrong forum.

I'm a beginner, how can I make sure the ports tree is up to date? I want to protect my VPS against the Heartbleed bug.

I don't speak English well.
 
LeventeX said:
I'm a beginner, how can I make sure the ports tree is up to date? I want to protect my VPS against the Heartbleed bug.
One question then: did you install OpenSSL from ports or packages, or are you using the version of OpenSSL that came with the operating system?

LeventeX said:
I don't speak English well.
Language is not a problem, we're quite tolerant of that. But please try to mind your writing style: proper use of punctuation and capital letters, that sort of thing.
 
LeventeX said:
I'm using OpenSSL that came with the operating system.
In that case, it's enough to update the operating system itself(*). Assuming you are running FreeBSD 10.0-RELEASE, issue the following two commands and then reboot the system:
# freebsd-update fetch
# freebsd-update install

If the FreeBSD version (type uname -r to find out) now reads 10.0-RELEASE-pX (where X is a number) you have successfully updated to the latest patchlevel.

Ad (*): Which means you were in the right forum after all :) I'll move your thread back.
 
Thx Thanks for the help.

One more question: does the pkg update command have same function as
freebsd-update fetch
freebsd-update install?
 
Yes and no. freebsd-update updates the operating system itself, pkg update (followed by pkg upgrade, by the way) updates third-party packages. So they have the same function, but operate on different parts of the system.
 
Yesterday, I typed the pkg update command, so I need to type freebsd-update fetch, freebsd-update install to protect my VPS against the Heartbleed bug? Or not?
 
LeventeX said:
Yesterday, I typed the pkg update command, so I need to type freebsd-update fetch, freebsd-update install to protect my VPS against the Heartbleed bug? Or not?
Yes, that should do it.

Mind you: pkg update alone won't do you much good. It only updates information about packages. You need to follow it up with pkg up[i]grade[/i] to actually update the packages themselves.

Edit: think of it this way:
  • pkg update and freebsd-update fetch mean asking: "So, what's new?"
  • pkg upgrade and freebsd-update install mean saying: "Okay, please do that."
 
fonz said:
LeventeX said:
I'm using OpenSSL that came with the operating system.
In that case, it's enough to update the operating system itself(*). Assuming you are running FreeBSD 10.0-RELEASE, issue the following two commands and then reboot the system:
# freebsd-update fetch
# freebsd-update install

If the FreeBSD version (type uname -r to find out) now reads 10.0-RELEASE-pX (where X is a number) you have successfully updated to the latest patchlevel.

Ad (*): Which means you were in the right forum after all :) I'll move your thread back.

Hi @fonz

I also use openssl that comes with FreeBSD..

So if uname -r returns
Code:
10.0-RELEASE-p7
does it mean that my openssl has got the latest patch for the Heartbleed bug even if openssl version returns 1.0.1e and not 1.0.1g?

Is there any advantage in installing openssl from the port and adding
Code:
WITH_OPENSSL_PORT=yes
in /etc/make.conf file?

Thank you,

Fred
 
Last edited by a moderator:
fred974 said:
So If uname -r return
Code:
10.0-RELEASE-p7
Does it mean that my openssl has got the latest patch for the heartbleed bug even if openssl version return 1.0.1e and not 1.0.1g?
Yes, http://www.freebsd.org/security/advisor ... penssl.asc

Is there any advantage in installing openssl from port and adding
Code:
WITH_OPENSSL_PORT=yes
in the /etc/make.conf file?
Not really but some ports may require the version from ports.
 
Back
Top