Vagrant: Problem with old (SHA-1) ssh key exchange when connecting to old server
I am using Vagrant to create hosts in network simulations. Recently, I re-installed an old pet-computer (ACME Foxboard, if you're interested) that still ran a very old Linux version. So old, that it required me to put
Host foxboard
KexAlgorithms +diffie-hellman-group1-sha1
in my .ssh/config, which is valid syntax from ssh version 7 on. However, since I did that, vagrant ssh started to refuse access to my machines:
$ vagrant ssh
/home/ljm/.ssh/config line 2: Bad SSH2 KexAlgorithms '+diffie-hellman-group1-sha1'.
Now, Vagrant states on its website:
SSH client usage
Vagrant will attempt to use the local SSH client installed on the host machine. On POSIX machines, an SSH client must be installed and available on the PATH.
So, I would expect things to work, especially because:
$ ssh -p 2222 vagrant@127.0.0.1
vagrant@127.0.0.1's password:
seems to work. But that means I have to distribute keys to all my machines to log-in.
Also, during boot, Vagrant seems to be able to ssh into the machine and, for example, change the ssh-keys.
Is there a solution that allows me to ssh into my personal computer museum and use a simple vagrant ssh?
ssh vagrant
edited 10 mins ago
Ned64
2,57911336
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
add a comment |
I am using Vagrant to create hosts in network simulations. Recently, I re-installed an old pet-computer (ACME Foxboard, if you're interested) that still ran a very old Linux version. So old, that it required me to put
Host foxboard
KexAlgorithms +diffie-hellman-group1-sha1
in my .ssh/config, which is valid syntax from ssh version 7 on. However, since I did that, vagrant ssh started to refuse access to my machines:
$ vagrant ssh
/home/ljm/.ssh/config line 2: Bad SSH2 KexAlgorithms '+diffie-hellman-group1-sha1'.
Now, Vagrant states on its website:
SSH client usage
Vagrant will attempt to use the local SSH client installed on the host machine. On POSIX machines, an SSH client must be installed and available on the PATH.
So, I would expect things to work, especially because:
$ ssh -p 2222 vagrant@127.0.0.1
vagrant@127.0.0.1's password:
seems to work. But that means I have to distribute keys to all my machines to log-in.
Also, during boot, Vagrant seems to be able to ssh into the machine and, for example, change the ssh-keys.
Is there a solution that allows me to ssh into my personal computer museum and use a simple vagrant ssh?
ssh vagrant
edited 10 mins ago
Ned64
2,57911336
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
add a comment |
I am using Vagrant to create hosts in network simulations. Recently, I re-installed an old pet-computer (ACME Foxboard, if you're interested) that still ran a very old Linux version. So old, that it required me to put
Host foxboard
KexAlgorithms +diffie-hellman-group1-sha1
in my .ssh/config, which is valid syntax from ssh version 7 on. However, since I did that, vagrant ssh started to refuse access to my machines:
$ vagrant ssh
/home/ljm/.ssh/config line 2: Bad SSH2 KexAlgorithms '+diffie-hellman-group1-sha1'.
Now, Vagrant states on its website:
SSH client usage
Vagrant will attempt to use the local SSH client installed on the host machine. On POSIX machines, an SSH client must be installed and available on the PATH.
So, I would expect things to work, especially because:
$ ssh -p 2222 vagrant@127.0.0.1
vagrant@127.0.0.1's password:
seems to work. But that means I have to distribute keys to all my machines to log-in.
Also, during boot, Vagrant seems to be able to ssh into the machine and, for example, change the ssh-keys.
Is there a solution that allows me to ssh into my personal computer museum and use a simple vagrant ssh?
ssh vagrant
edited 10 mins ago
Ned64
2,57911336
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
I am using Vagrant to create hosts in network simulations. Recently, I re-installed an old pet-computer (ACME Foxboard, if you're interested) that still ran a very old Linux version. So old, that it required me to put
Host foxboard
KexAlgorithms +diffie-hellman-group1-sha1
in my .ssh/config, which is valid syntax from ssh version 7 on. However, since I did that, vagrant ssh started to refuse access to my machines:
$ vagrant ssh
/home/ljm/.ssh/config line 2: Bad SSH2 KexAlgorithms '+diffie-hellman-group1-sha1'.
Now, Vagrant states on its website:
SSH client usage
Vagrant will attempt to use the local SSH client installed on the host machine. On POSIX machines, an SSH client must be installed and available on the PATH.
So, I would expect things to work, especially because:
$ ssh -p 2222 vagrant@127.0.0.1
vagrant@127.0.0.1's password:
seems to work. But that means I have to distribute keys to all my machines to log-in.
Also, during boot, Vagrant seems to be able to ssh into the machine and, for example, change the ssh-keys.
Is there a solution that allows me to ssh into my personal computer museum and use a simple vagrant ssh?
ssh vagrant
ssh vagrant
edited 10 mins ago
Ned64
2,57911336
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
edited 10 mins ago
Ned64
2,57911336
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
edited 10 mins ago
Ned64
2,57911336
edited 10 mins ago
Ned64
2,57911336
edited 10 mins ago
Ned64
2,57911336
2,57911336
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
asked 1 hour ago
Ljm DullaartLjm Dullaart
739212
739212
add a comment |
add a comment |
0
active
oldest
votes
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',
autoActivateHeartbeat: false,
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%2f506669%2fvagrant-problem-with-old-sha-1-ssh-key-exchange-when-connecting-to-old-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f506669%2fvagrant-problem-with-old-sha-1-ssh-key-exchange-when-connecting-to-old-server%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
