Upgrade OpenSSH 7.4 to later on RHEL
up vote
0
down vote
favorite
I have a Red Hat Enterprise Linux server (7.5 x86_64). I have OpenSSH version 7.4. I was asked to upgrade it to a later version for security reasons: Nessus states that OpenSSH should be ugraded from 7.4 to 7.6 or later. However the Red Hat software and downloads does not have the latest package RPM.
I found some clues on where to get the latest package for OpenSSH. I found this link, however, I do not know on how to upgrade it and trust this website. I do not want the SSH and other configuration to be modified by the ugrade.
I did find links but however they are not useful, for example this one.
I would like to know how to upgrade OpenSSH without using yum.
ssh rhel upgrade openssh
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
asked Dec 5 at 13:43
Abdullah Naina
143
|
show 1 more comment
up vote
0
down vote
favorite
I have a Red Hat Enterprise Linux server (7.5 x86_64). I have OpenSSH version 7.4. I was asked to upgrade it to a later version for security reasons: Nessus states that OpenSSH should be ugraded from 7.4 to 7.6 or later. However the Red Hat software and downloads does not have the latest package RPM.
I found some clues on where to get the latest package for OpenSSH. I found this link, however, I do not know on how to upgrade it and trust this website. I do not want the SSH and other configuration to be modified by the ugrade.
I did find links but however they are not useful, for example this one.
I would like to know how to upgrade OpenSSH without using yum.
ssh rhel upgrade openssh
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
asked Dec 5 at 13:43
Abdullah Naina
143
4
Were you given specific reasons for the upgrade? If it’s about security, the OpenSSH 7.4p1-16 package is fully patched.
– Stephen Kitt
Dec 5 at 14:26
1
RedHat will backport relevant security patches to the versions they ship. For this issue, a fix was released in April: access.redhat.com/security/cve/cve-2017-15906
– Ulrich Schwarz
Dec 5 at 14:37
1
Reviewers: this is not a request for learning materials.
– Stephen Kitt
Dec 5 at 14:38
1
If there is no available package from RHEL you are best off, imo, building the version you want from source code. Only you can decide if it is worth the effort to do so vs accepting the packages in RHEL repos
– Panther
Dec 5 at 16:02
1
@AbdullahNaina I would build it from sources and put it somewhere else instead of messing with the distro's files (eg. build it with./config --prefix=/some/path/elsewhere; make installand then point apps that need the new version there viaLD_LIBRARY_PATH=/some/path/elsewhere).
– mosvy
Dec 5 at 19:30
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a Red Hat Enterprise Linux server (7.5 x86_64). I have OpenSSH version 7.4. I was asked to upgrade it to a later version for security reasons: Nessus states that OpenSSH should be ugraded from 7.4 to 7.6 or later. However the Red Hat software and downloads does not have the latest package RPM.
I found some clues on where to get the latest package for OpenSSH. I found this link, however, I do not know on how to upgrade it and trust this website. I do not want the SSH and other configuration to be modified by the ugrade.
I did find links but however they are not useful, for example this one.
I would like to know how to upgrade OpenSSH without using yum.
ssh rhel upgrade openssh
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
asked Dec 5 at 13:43
Abdullah Naina
143
I have a Red Hat Enterprise Linux server (7.5 x86_64). I have OpenSSH version 7.4. I was asked to upgrade it to a later version for security reasons: Nessus states that OpenSSH should be ugraded from 7.4 to 7.6 or later. However the Red Hat software and downloads does not have the latest package RPM.
I found some clues on where to get the latest package for OpenSSH. I found this link, however, I do not know on how to upgrade it and trust this website. I do not want the SSH and other configuration to be modified by the ugrade.
I did find links but however they are not useful, for example this one.
I would like to know how to upgrade OpenSSH without using yum.
ssh rhel upgrade openssh
ssh rhel upgrade openssh
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
asked Dec 5 at 13:43
Abdullah Naina
143
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
asked Dec 5 at 13:43
Abdullah Naina
143
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
edited Dec 5 at 14:52
Stephen Kitt
162k24358436
162k24358436
asked Dec 5 at 13:43
Abdullah Naina
143
asked Dec 5 at 13:43
Abdullah Naina
143
asked Dec 5 at 13:43
Abdullah Naina
143
143
4
Were you given specific reasons for the upgrade? If it’s about security, the OpenSSH 7.4p1-16 package is fully patched.
– Stephen Kitt
Dec 5 at 14:26
1
RedHat will backport relevant security patches to the versions they ship. For this issue, a fix was released in April: access.redhat.com/security/cve/cve-2017-15906
– Ulrich Schwarz
Dec 5 at 14:37
1
Reviewers: this is not a request for learning materials.
– Stephen Kitt
Dec 5 at 14:38
1
If there is no available package from RHEL you are best off, imo, building the version you want from source code. Only you can decide if it is worth the effort to do so vs accepting the packages in RHEL repos
– Panther
Dec 5 at 16:02
1
@AbdullahNaina I would build it from sources and put it somewhere else instead of messing with the distro's files (eg. build it with./config --prefix=/some/path/elsewhere; make installand then point apps that need the new version there viaLD_LIBRARY_PATH=/some/path/elsewhere).
– mosvy
Dec 5 at 19:30
|
show 1 more comment
4
Were you given specific reasons for the upgrade? If it’s about security, the OpenSSH 7.4p1-16 package is fully patched.
– Stephen Kitt
Dec 5 at 14:26
1
RedHat will backport relevant security patches to the versions they ship. For this issue, a fix was released in April: access.redhat.com/security/cve/cve-2017-15906
– Ulrich Schwarz
Dec 5 at 14:37
1
Reviewers: this is not a request for learning materials.
– Stephen Kitt
Dec 5 at 14:38
1
If there is no available package from RHEL you are best off, imo, building the version you want from source code. Only you can decide if it is worth the effort to do so vs accepting the packages in RHEL repos
– Panther
Dec 5 at 16:02
1
@AbdullahNaina I would build it from sources and put it somewhere else instead of messing with the distro's files (eg. build it with./config --prefix=/some/path/elsewhere; make installand then point apps that need the new version there viaLD_LIBRARY_PATH=/some/path/elsewhere).
– mosvy
Dec 5 at 19:30
4
4
Were you given specific reasons for the upgrade? If it’s about security, the OpenSSH 7.4p1-16 package is fully patched.
– Stephen Kitt
Dec 5 at 14:26
Were you given specific reasons for the upgrade? If it’s about security, the OpenSSH 7.4p1-16 package is fully patched.
– Stephen Kitt
Dec 5 at 14:26
1
1
RedHat will backport relevant security patches to the versions they ship. For this issue, a fix was released in April: access.redhat.com/security/cve/cve-2017-15906
– Ulrich Schwarz
Dec 5 at 14:37
RedHat will backport relevant security patches to the versions they ship. For this issue, a fix was released in April: access.redhat.com/security/cve/cve-2017-15906
– Ulrich Schwarz
Dec 5 at 14:37
1
1
Reviewers: this is not a request for learning materials.
– Stephen Kitt
Dec 5 at 14:38
Reviewers: this is not a request for learning materials.
– Stephen Kitt
Dec 5 at 14:38
1
1
If there is no available package from RHEL you are best off, imo, building the version you want from source code. Only you can decide if it is worth the effort to do so vs accepting the packages in RHEL repos
– Panther
Dec 5 at 16:02
If there is no available package from RHEL you are best off, imo, building the version you want from source code. Only you can decide if it is worth the effort to do so vs accepting the packages in RHEL repos
– Panther
Dec 5 at 16:02
1
1
@AbdullahNaina I would build it from sources and put it somewhere else instead of messing with the distro's files (eg. build it with
./config --prefix=/some/path/elsewhere; make install and then point apps that need the new version there via LD_LIBRARY_PATH=/some/path/elsewhere).– mosvy
Dec 5 at 19:30
@AbdullahNaina I would build it from sources and put it somewhere else instead of messing with the distro's files (eg. build it with
./config --prefix=/some/path/elsewhere; make install and then point apps that need the new version there via LD_LIBRARY_PATH=/some/path/elsewhere).– mosvy
Dec 5 at 19:30
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
4
down vote
RHEL 7 ships OpenSSH 7.4p1 with any patches necessary to fix security issues. RHEL 7 is fully supported until 2024 (and longer with extended support contracts).
This means that all known vulnerabilities in your version of OpenSSH are fixed, and newly-discovered vulnerabilities which are discovered in the future will be fixed — there’s no need to upgrade to the latest version of OpenSSH to avoid vulnerabilities.
That’s one of the points of using a supported distribution: you can rely on your distributor to take care of upstream vulnerabilities for you (as long as you keep your systems up-to-date).
To upgrade to a version of OpenSSH later than 7.4 you’d have to upgrade to RHEL 8 (which is currently in beta and has OpenSSH 7.8), or build it yourself for RHEL 7 (and take on support for future vulnerabilities).
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486153%2fupgrade-openssh-7-4-to-later-on-rhel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
RHEL 7 ships OpenSSH 7.4p1 with any patches necessary to fix security issues. RHEL 7 is fully supported until 2024 (and longer with extended support contracts).
This means that all known vulnerabilities in your version of OpenSSH are fixed, and newly-discovered vulnerabilities which are discovered in the future will be fixed — there’s no need to upgrade to the latest version of OpenSSH to avoid vulnerabilities.
That’s one of the points of using a supported distribution: you can rely on your distributor to take care of upstream vulnerabilities for you (as long as you keep your systems up-to-date).
To upgrade to a version of OpenSSH later than 7.4 you’d have to upgrade to RHEL 8 (which is currently in beta and has OpenSSH 7.8), or build it yourself for RHEL 7 (and take on support for future vulnerabilities).
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
add a comment |
up vote
4
down vote
RHEL 7 ships OpenSSH 7.4p1 with any patches necessary to fix security issues. RHEL 7 is fully supported until 2024 (and longer with extended support contracts).
This means that all known vulnerabilities in your version of OpenSSH are fixed, and newly-discovered vulnerabilities which are discovered in the future will be fixed — there’s no need to upgrade to the latest version of OpenSSH to avoid vulnerabilities.
That’s one of the points of using a supported distribution: you can rely on your distributor to take care of upstream vulnerabilities for you (as long as you keep your systems up-to-date).
To upgrade to a version of OpenSSH later than 7.4 you’d have to upgrade to RHEL 8 (which is currently in beta and has OpenSSH 7.8), or build it yourself for RHEL 7 (and take on support for future vulnerabilities).
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
add a comment |
up vote
4
down vote
up vote
4
down vote
RHEL 7 ships OpenSSH 7.4p1 with any patches necessary to fix security issues. RHEL 7 is fully supported until 2024 (and longer with extended support contracts).
This means that all known vulnerabilities in your version of OpenSSH are fixed, and newly-discovered vulnerabilities which are discovered in the future will be fixed — there’s no need to upgrade to the latest version of OpenSSH to avoid vulnerabilities.
That’s one of the points of using a supported distribution: you can rely on your distributor to take care of upstream vulnerabilities for you (as long as you keep your systems up-to-date).
To upgrade to a version of OpenSSH later than 7.4 you’d have to upgrade to RHEL 8 (which is currently in beta and has OpenSSH 7.8), or build it yourself for RHEL 7 (and take on support for future vulnerabilities).
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
RHEL 7 ships OpenSSH 7.4p1 with any patches necessary to fix security issues. RHEL 7 is fully supported until 2024 (and longer with extended support contracts).
This means that all known vulnerabilities in your version of OpenSSH are fixed, and newly-discovered vulnerabilities which are discovered in the future will be fixed — there’s no need to upgrade to the latest version of OpenSSH to avoid vulnerabilities.
That’s one of the points of using a supported distribution: you can rely on your distributor to take care of upstream vulnerabilities for you (as long as you keep your systems up-to-date).
To upgrade to a version of OpenSSH later than 7.4 you’d have to upgrade to RHEL 8 (which is currently in beta and has OpenSSH 7.8), or build it yourself for RHEL 7 (and take on support for future vulnerabilities).
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
answered Dec 5 at 14:41
Stephen Kitt
162k24358436
162k24358436
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
add a comment |
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
The greater point here is that the easier part is having the tools. You have to use your grey matter to process, filter and validate the extra information they provide you with. Asking someone else is just the easy way out.
– Rui F Ribeiro
Dec 5 at 15:04
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486153%2fupgrade-openssh-7-4-to-later-on-rhel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
Were you given specific reasons for the upgrade? If it’s about security, the OpenSSH 7.4p1-16 package is fully patched.
– Stephen Kitt
Dec 5 at 14:26
1
RedHat will backport relevant security patches to the versions they ship. For this issue, a fix was released in April: access.redhat.com/security/cve/cve-2017-15906
– Ulrich Schwarz
Dec 5 at 14:37
1
Reviewers: this is not a request for learning materials.
– Stephen Kitt
Dec 5 at 14:38
1
If there is no available package from RHEL you are best off, imo, building the version you want from source code. Only you can decide if it is worth the effort to do so vs accepting the packages in RHEL repos
– Panther
Dec 5 at 16:02
1
@AbdullahNaina I would build it from sources and put it somewhere else instead of messing with the distro's files (eg. build it with
./config --prefix=/some/path/elsewhere; make installand then point apps that need the new version there viaLD_LIBRARY_PATH=/some/path/elsewhere).– mosvy
Dec 5 at 19:30