Ubuntu 16.04 with ssh1 and ~/.ssh/config
With Ubuntu 15.10 and before, I had a host entry with "Protocol 1" in my .ssh/config file.
Ubuntu 16.04 doesn't have support for SSH1 anymore per default.
corben@ubuntu1604:~$ ssh -1 host
ssh1 is not supported
When using the ssh client with any host entry having a "Protocol 1" line in .ssh/config it complains with:
corben@ubuntu1604:~$ ssh host
.ssh/config line <nr>: Bad protocol spec '1'.
To connect to my host using ssh1, I could install the package openssh-client-ssh1 and call ssh1 instead of ssh .
But the ssh1 client doesn't use the host entry configured in .ssh/config, when the "Protocol 1" line is omitted.
There is no man page for ssh1 and "man ssh" still lists the -1 option for protocol version 1. I want to use a host entry as I have port forwarding and ssh keys configured, which I don't want to enter each time on the command line.
How to use ssh and ssh1 in coexistence and .ssh/config?
The host is an embedded device still in service, where no firmware updates will be released. As it is used in a LAN environment the security aspect using ssh version 1 isn't an issue.
linux ubuntu ssh
asked Aug 27 '16 at 16:43
CorbenCorben
1113
add a comment |
With Ubuntu 15.10 and before, I had a host entry with "Protocol 1" in my .ssh/config file.
Ubuntu 16.04 doesn't have support for SSH1 anymore per default.
corben@ubuntu1604:~$ ssh -1 host
ssh1 is not supported
When using the ssh client with any host entry having a "Protocol 1" line in .ssh/config it complains with:
corben@ubuntu1604:~$ ssh host
.ssh/config line <nr>: Bad protocol spec '1'.
To connect to my host using ssh1, I could install the package openssh-client-ssh1 and call ssh1 instead of ssh .
But the ssh1 client doesn't use the host entry configured in .ssh/config, when the "Protocol 1" line is omitted.
There is no man page for ssh1 and "man ssh" still lists the -1 option for protocol version 1. I want to use a host entry as I have port forwarding and ssh keys configured, which I don't want to enter each time on the command line.
How to use ssh and ssh1 in coexistence and .ssh/config?
The host is an embedded device still in service, where no firmware updates will be released. As it is used in a LAN environment the security aspect using ssh version 1 isn't an issue.
linux ubuntu ssh
asked Aug 27 '16 at 16:43
CorbenCorben
1113
add a comment |
With Ubuntu 15.10 and before, I had a host entry with "Protocol 1" in my .ssh/config file.
Ubuntu 16.04 doesn't have support for SSH1 anymore per default.
corben@ubuntu1604:~$ ssh -1 host
ssh1 is not supported
When using the ssh client with any host entry having a "Protocol 1" line in .ssh/config it complains with:
corben@ubuntu1604:~$ ssh host
.ssh/config line <nr>: Bad protocol spec '1'.
To connect to my host using ssh1, I could install the package openssh-client-ssh1 and call ssh1 instead of ssh .
But the ssh1 client doesn't use the host entry configured in .ssh/config, when the "Protocol 1" line is omitted.
There is no man page for ssh1 and "man ssh" still lists the -1 option for protocol version 1. I want to use a host entry as I have port forwarding and ssh keys configured, which I don't want to enter each time on the command line.
How to use ssh and ssh1 in coexistence and .ssh/config?
The host is an embedded device still in service, where no firmware updates will be released. As it is used in a LAN environment the security aspect using ssh version 1 isn't an issue.
linux ubuntu ssh
asked Aug 27 '16 at 16:43
CorbenCorben
1113
With Ubuntu 15.10 and before, I had a host entry with "Protocol 1" in my .ssh/config file.
Ubuntu 16.04 doesn't have support for SSH1 anymore per default.
corben@ubuntu1604:~$ ssh -1 host
ssh1 is not supported
When using the ssh client with any host entry having a "Protocol 1" line in .ssh/config it complains with:
corben@ubuntu1604:~$ ssh host
.ssh/config line <nr>: Bad protocol spec '1'.
To connect to my host using ssh1, I could install the package openssh-client-ssh1 and call ssh1 instead of ssh .
But the ssh1 client doesn't use the host entry configured in .ssh/config, when the "Protocol 1" line is omitted.
There is no man page for ssh1 and "man ssh" still lists the -1 option for protocol version 1. I want to use a host entry as I have port forwarding and ssh keys configured, which I don't want to enter each time on the command line.
How to use ssh and ssh1 in coexistence and .ssh/config?
The host is an embedded device still in service, where no firmware updates will be released. As it is used in a LAN environment the security aspect using ssh version 1 isn't an issue.
linux ubuntu ssh
linux ubuntu ssh
asked Aug 27 '16 at 16:43
CorbenCorben
1113
asked Aug 27 '16 at 16:43
CorbenCorben
1113
asked Aug 27 '16 at 16:43
CorbenCorben
1113
asked Aug 27 '16 at 16:43
CorbenCorben
1113
asked Aug 27 '16 at 16:43
CorbenCorben
1113
1113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Protocol SSH1 is gone for good and it is time to accept that. It will get removed from manual pages and documentation very soon so it will not confuse users. It is pretty unclear what you are trying to do.
ssh1 should still read the ~/.ssh/config, if Ubuntu maintainers didn't break something. Can you post the verbose log (ssh1 -vvv host1) from your connection to your ssh1 host? Does using ssh1 -1 host1 change something?
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
1
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
You can create aliasalias ssh1="ssh1 -1"to simplify this work. Thessh1is nothing more than the normalsshwith ssh1 support build in (not a tool supporting onlyssh1), but I would not recommend using that for all thesshoperations.
– Jakuje
Aug 28 '16 at 7:54
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
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%2f1118293%2fubuntu-16-04-with-ssh1-and-ssh-config%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
Protocol SSH1 is gone for good and it is time to accept that. It will get removed from manual pages and documentation very soon so it will not confuse users. It is pretty unclear what you are trying to do.
ssh1 should still read the ~/.ssh/config, if Ubuntu maintainers didn't break something. Can you post the verbose log (ssh1 -vvv host1) from your connection to your ssh1 host? Does using ssh1 -1 host1 change something?
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
1
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
You can create aliasalias ssh1="ssh1 -1"to simplify this work. Thessh1is nothing more than the normalsshwith ssh1 support build in (not a tool supporting onlyssh1), but I would not recommend using that for all thesshoperations.
– Jakuje
Aug 28 '16 at 7:54
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
add a comment |
Protocol SSH1 is gone for good and it is time to accept that. It will get removed from manual pages and documentation very soon so it will not confuse users. It is pretty unclear what you are trying to do.
ssh1 should still read the ~/.ssh/config, if Ubuntu maintainers didn't break something. Can you post the verbose log (ssh1 -vvv host1) from your connection to your ssh1 host? Does using ssh1 -1 host1 change something?
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
1
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
You can create aliasalias ssh1="ssh1 -1"to simplify this work. Thessh1is nothing more than the normalsshwith ssh1 support build in (not a tool supporting onlyssh1), but I would not recommend using that for all thesshoperations.
– Jakuje
Aug 28 '16 at 7:54
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
add a comment |
Protocol SSH1 is gone for good and it is time to accept that. It will get removed from manual pages and documentation very soon so it will not confuse users. It is pretty unclear what you are trying to do.
ssh1 should still read the ~/.ssh/config, if Ubuntu maintainers didn't break something. Can you post the verbose log (ssh1 -vvv host1) from your connection to your ssh1 host? Does using ssh1 -1 host1 change something?
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
Protocol SSH1 is gone for good and it is time to accept that. It will get removed from manual pages and documentation very soon so it will not confuse users. It is pretty unclear what you are trying to do.
ssh1 should still read the ~/.ssh/config, if Ubuntu maintainers didn't break something. Can you post the verbose log (ssh1 -vvv host1) from your connection to your ssh1 host? Does using ssh1 -1 host1 change something?
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
answered Aug 27 '16 at 18:55
JakujeJakuje
7,16251929
7,16251929
1
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
You can create aliasalias ssh1="ssh1 -1"to simplify this work. Thessh1is nothing more than the normalsshwith ssh1 support build in (not a tool supporting onlyssh1), but I would not recommend using that for all thesshoperations.
– Jakuje
Aug 28 '16 at 7:54
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
add a comment |
1
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
You can create aliasalias ssh1="ssh1 -1"to simplify this work. Thessh1is nothing more than the normalsshwith ssh1 support build in (not a tool supporting onlyssh1), but I would not recommend using that for all thesshoperations.
– Jakuje
Aug 28 '16 at 7:54
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
1
1
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
As said, I have no choice with this device. It's tied to ssh1, period. The only thing that works, is removing any "Protocol 1" lines from .ssh/config as the normal ssh command is complaining about it if there is any found in the file. No matter if the entry is for this host or another. For coexistence I have to call: "ssh1 -1 host". I hoped there is a way not to add any further command line options or even use the same command for all hosts. I understand ssh1 being old and unsecure, but this is out of question.
– Corben
Aug 28 '16 at 7:52
You can create alias
alias ssh1="ssh1 -1" to simplify this work. The ssh1 is nothing more than the normal ssh with ssh1 support build in (not a tool supporting only ssh1), but I would not recommend using that for all the ssh operations.– Jakuje
Aug 28 '16 at 7:54
You can create alias
alias ssh1="ssh1 -1" to simplify this work. The ssh1 is nothing more than the normal ssh with ssh1 support build in (not a tool supporting only ssh1), but I would not recommend using that for all the ssh operations.– Jakuje
Aug 28 '16 at 7:54
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
Is the ssh1 command/package including any patches that have been integrated into the "normal" ssh command/package? I hope for compatibility reasons, the ssh1 support isn't dropped completely in the future. Imho it's okay if you have to install it explicitly.
– Corben
Aug 28 '16 at 8:02
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
It should be the same. The SSH1 support is turned on during compile time.
– Jakuje
Aug 28 '16 at 8:05
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%2f1118293%2fubuntu-16-04-with-ssh1-and-ssh-config%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
