Can't open an SSH session because of OpenSSL version mismatch
I just ran apt-get upgrade
, and according to /var/log/apt/history.log, openssl has been updated to version 1.0.1e-2+rvt+deb7u7. Now I have one SSH session still open, but I can't open another one. I restarted SSH, which returned OpenSSL version mismatch. Built against 1000105f, you have 10001080
.
I tried apt-get remove openssl && apt-get install openssl
with no luck. I'm running debian on a raspberry pi.
Edit: I should mention that I'm running wheezy, and used the jessie repository to get the latest PHP5 version. I forgot to switch back before apt-get upgrade
-ing.
Edit 2: problem solved;
apt-get update
apt-get upgrade
apt-get dist-upgrade
Did the trick (source).
ssh debian apt-get openssl
add a comment |
I just ran apt-get upgrade
, and according to /var/log/apt/history.log, openssl has been updated to version 1.0.1e-2+rvt+deb7u7. Now I have one SSH session still open, but I can't open another one. I restarted SSH, which returned OpenSSL version mismatch. Built against 1000105f, you have 10001080
.
I tried apt-get remove openssl && apt-get install openssl
with no luck. I'm running debian on a raspberry pi.
Edit: I should mention that I'm running wheezy, and used the jessie repository to get the latest PHP5 version. I forgot to switch back before apt-get upgrade
-ing.
Edit 2: problem solved;
apt-get update
apt-get upgrade
apt-get dist-upgrade
Did the trick (source).
ssh debian apt-get openssl
raspberrypi.stackexchange.com
– alexus
Jun 7 '14 at 14:16
3
You should post your solution as an answer and then mark it as accepted.
– Doktoro Reichard
Jul 3 '14 at 16:02
add a comment |
I just ran apt-get upgrade
, and according to /var/log/apt/history.log, openssl has been updated to version 1.0.1e-2+rvt+deb7u7. Now I have one SSH session still open, but I can't open another one. I restarted SSH, which returned OpenSSL version mismatch. Built against 1000105f, you have 10001080
.
I tried apt-get remove openssl && apt-get install openssl
with no luck. I'm running debian on a raspberry pi.
Edit: I should mention that I'm running wheezy, and used the jessie repository to get the latest PHP5 version. I forgot to switch back before apt-get upgrade
-ing.
Edit 2: problem solved;
apt-get update
apt-get upgrade
apt-get dist-upgrade
Did the trick (source).
ssh debian apt-get openssl
I just ran apt-get upgrade
, and according to /var/log/apt/history.log, openssl has been updated to version 1.0.1e-2+rvt+deb7u7. Now I have one SSH session still open, but I can't open another one. I restarted SSH, which returned OpenSSL version mismatch. Built against 1000105f, you have 10001080
.
I tried apt-get remove openssl && apt-get install openssl
with no luck. I'm running debian on a raspberry pi.
Edit: I should mention that I'm running wheezy, and used the jessie repository to get the latest PHP5 version. I forgot to switch back before apt-get upgrade
-ing.
Edit 2: problem solved;
apt-get update
apt-get upgrade
apt-get dist-upgrade
Did the trick (source).
ssh debian apt-get openssl
ssh debian apt-get openssl
edited Nov 18 '14 at 21:41
user391035
30619
30619
asked Jun 7 '14 at 13:32
NiekNiek
14314
14314
raspberrypi.stackexchange.com
– alexus
Jun 7 '14 at 14:16
3
You should post your solution as an answer and then mark it as accepted.
– Doktoro Reichard
Jul 3 '14 at 16:02
add a comment |
raspberrypi.stackexchange.com
– alexus
Jun 7 '14 at 14:16
3
You should post your solution as an answer and then mark it as accepted.
– Doktoro Reichard
Jul 3 '14 at 16:02
raspberrypi.stackexchange.com
– alexus
Jun 7 '14 at 14:16
raspberrypi.stackexchange.com
– alexus
Jun 7 '14 at 14:16
3
3
You should post your solution as an answer and then mark it as accepted.
– Doktoro Reichard
Jul 3 '14 at 16:02
You should post your solution as an answer and then mark it as accepted.
– Doktoro Reichard
Jul 3 '14 at 16:02
add a comment |
2 Answers
2
active
oldest
votes
From Stack Overflow:
Try
apt-get install openssh-server openssh-client
.
I had the same issue when I updated my system to Debian Testing. Even though SSH was already installed, in my case it wasn't pulled in for updating when I ran apt-get update && apt-get upgrade and so the system still had the same SSH binaries with the now-outdated libraries linked against it, hence the version mismatch.
add a comment |
Sounds like your ssh is having a port conflict. From searching around i found 3 commands that might be able to help. SIGHUP, SIGKILL and SIGTERM. From what the article i found on it was SIGTERM is the safest way to kill the process blocking the port.
When i programmed in python, it wouldn't kill the process even when i exited the gui. so those might work for ya.
Reference from
http://www.cyberciti.biz/faq/kill-process-in-linux-or-terminate-a-process-in-unix-or-linux-systems/
1
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f764873%2fcant-open-an-ssh-session-because-of-openssl-version-mismatch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
From Stack Overflow:
Try
apt-get install openssh-server openssh-client
.
I had the same issue when I updated my system to Debian Testing. Even though SSH was already installed, in my case it wasn't pulled in for updating when I ran apt-get update && apt-get upgrade and so the system still had the same SSH binaries with the now-outdated libraries linked against it, hence the version mismatch.
add a comment |
From Stack Overflow:
Try
apt-get install openssh-server openssh-client
.
I had the same issue when I updated my system to Debian Testing. Even though SSH was already installed, in my case it wasn't pulled in for updating when I ran apt-get update && apt-get upgrade and so the system still had the same SSH binaries with the now-outdated libraries linked against it, hence the version mismatch.
add a comment |
From Stack Overflow:
Try
apt-get install openssh-server openssh-client
.
I had the same issue when I updated my system to Debian Testing. Even though SSH was already installed, in my case it wasn't pulled in for updating when I ran apt-get update && apt-get upgrade and so the system still had the same SSH binaries with the now-outdated libraries linked against it, hence the version mismatch.
From Stack Overflow:
Try
apt-get install openssh-server openssh-client
.
I had the same issue when I updated my system to Debian Testing. Even though SSH was already installed, in my case it wasn't pulled in for updating when I ran apt-get update && apt-get upgrade and so the system still had the same SSH binaries with the now-outdated libraries linked against it, hence the version mismatch.
edited May 23 '17 at 12:41
Community♦
1
1
answered Jul 23 '14 at 7:40
ChenthurijChenthurij
93
93
add a comment |
add a comment |
Sounds like your ssh is having a port conflict. From searching around i found 3 commands that might be able to help. SIGHUP, SIGKILL and SIGTERM. From what the article i found on it was SIGTERM is the safest way to kill the process blocking the port.
When i programmed in python, it wouldn't kill the process even when i exited the gui. so those might work for ya.
Reference from
http://www.cyberciti.biz/faq/kill-process-in-linux-or-terminate-a-process-in-unix-or-linux-systems/
1
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
add a comment |
Sounds like your ssh is having a port conflict. From searching around i found 3 commands that might be able to help. SIGHUP, SIGKILL and SIGTERM. From what the article i found on it was SIGTERM is the safest way to kill the process blocking the port.
When i programmed in python, it wouldn't kill the process even when i exited the gui. so those might work for ya.
Reference from
http://www.cyberciti.biz/faq/kill-process-in-linux-or-terminate-a-process-in-unix-or-linux-systems/
1
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
add a comment |
Sounds like your ssh is having a port conflict. From searching around i found 3 commands that might be able to help. SIGHUP, SIGKILL and SIGTERM. From what the article i found on it was SIGTERM is the safest way to kill the process blocking the port.
When i programmed in python, it wouldn't kill the process even when i exited the gui. so those might work for ya.
Reference from
http://www.cyberciti.biz/faq/kill-process-in-linux-or-terminate-a-process-in-unix-or-linux-systems/
Sounds like your ssh is having a port conflict. From searching around i found 3 commands that might be able to help. SIGHUP, SIGKILL and SIGTERM. From what the article i found on it was SIGTERM is the safest way to kill the process blocking the port.
When i programmed in python, it wouldn't kill the process even when i exited the gui. so those might work for ya.
Reference from
http://www.cyberciti.biz/faq/kill-process-in-linux-or-terminate-a-process-in-unix-or-linux-systems/
answered May 11 '15 at 3:15
Sammy WestSammy West
11
11
1
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
add a comment |
1
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
1
1
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
Also there may be other programs trying to use the same port, i would reccomend using the command i posted below to view running processes on your system. # ps aux | less
– Sammy West
May 11 '15 at 3:17
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f764873%2fcant-open-an-ssh-session-because-of-openssl-version-mismatch%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
raspberrypi.stackexchange.com
– alexus
Jun 7 '14 at 14:16
3
You should post your solution as an answer and then mark it as accepted.
– Doktoro Reichard
Jul 3 '14 at 16:02