SSH authorized_keys and newline
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am trying to configure SSH with public-key authentication on Debian.
I can't seem to get it to work because auth.log keeps saying that can't read key type:...(key line)n.
It keeps complaining about the newline and i can't remove it. I open the file, i delete the newline but it's added again.
Thank you in advance
Edit:I managed to remove the newline, but now i have the same error i had last night. I started with a 4096 RSA key but given this error i thought ssh did not accept 4096 bit keys (i know it is stupid but i had to try). Here is the error from auth.log:
Sep 11 08:36:18 fortknox sshd[5002]: error: buffer_get_string_ret: bad string length 813826338
Sep 11 08:36:18 fortknox sshd[5002]: error: key_from_blob: can't read key type
Sep 11 08:36:18 fortknox sshd[5002]: error: key_read: key_from_blob MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvGOorkMkY7OX6iQrTWm+JeFxysPm02PRTcOMQlIrAkYSkCody07Y5+e7IPFXoRIHgzecpZ/KeA13T6qa7x5pRu65xAyvsnkvW5YFxVkv/JNvS3EBKpOE22dkO2xC5Dv7id/Aw3QtnzdwZhllczmOoSRbtPfJK4oxLNcy6lAqiN1XQLWl/2I7GglTawJCAsXpqXdXsJGFqnQkMPWkVo3LTlcZVgzH+ChURJTRutNJCeEm8d+FzGfTICCoPveOhlytJTAXtsDLKGgEoK2XoGfUH3OGRsBq0WssINXvopfhrfhTaBxKZ7kr3WLQSHHy6A/xxlTwA81wNuiXNBdGUGSaVwIDAQAB cryptosec@fortknox.sec failed
ssh debian openssh authorized-keys
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
add a comment |
I am trying to configure SSH with public-key authentication on Debian.
I can't seem to get it to work because auth.log keeps saying that can't read key type:...(key line)n.
It keeps complaining about the newline and i can't remove it. I open the file, i delete the newline but it's added again.
Thank you in advance
Edit:I managed to remove the newline, but now i have the same error i had last night. I started with a 4096 RSA key but given this error i thought ssh did not accept 4096 bit keys (i know it is stupid but i had to try). Here is the error from auth.log:
Sep 11 08:36:18 fortknox sshd[5002]: error: buffer_get_string_ret: bad string length 813826338
Sep 11 08:36:18 fortknox sshd[5002]: error: key_from_blob: can't read key type
Sep 11 08:36:18 fortknox sshd[5002]: error: key_read: key_from_blob MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvGOorkMkY7OX6iQrTWm+JeFxysPm02PRTcOMQlIrAkYSkCody07Y5+e7IPFXoRIHgzecpZ/KeA13T6qa7x5pRu65xAyvsnkvW5YFxVkv/JNvS3EBKpOE22dkO2xC5Dv7id/Aw3QtnzdwZhllczmOoSRbtPfJK4oxLNcy6lAqiN1XQLWl/2I7GglTawJCAsXpqXdXsJGFqnQkMPWkVo3LTlcZVgzH+ChURJTRutNJCeEm8d+FzGfTICCoPveOhlytJTAXtsDLKGgEoK2XoGfUH3OGRsBq0WssINXvopfhrfhTaBxKZ7kr3WLQSHHy6A/xxlTwA81wNuiXNBdGUGSaVwIDAQAB cryptosec@fortknox.sec failed
ssh debian openssh authorized-keys
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
Could you add the relevant line from authorized_keys to your question? Feel free to munge the long hexidecimal part.
– Kenster
Sep 12 '14 at 23:22
let's see some extracts from the command line that demonstrate what is going on
– barlop
Sep 13 '14 at 0:39
add a comment |
I am trying to configure SSH with public-key authentication on Debian.
I can't seem to get it to work because auth.log keeps saying that can't read key type:...(key line)n.
It keeps complaining about the newline and i can't remove it. I open the file, i delete the newline but it's added again.
Thank you in advance
Edit:I managed to remove the newline, but now i have the same error i had last night. I started with a 4096 RSA key but given this error i thought ssh did not accept 4096 bit keys (i know it is stupid but i had to try). Here is the error from auth.log:
Sep 11 08:36:18 fortknox sshd[5002]: error: buffer_get_string_ret: bad string length 813826338
Sep 11 08:36:18 fortknox sshd[5002]: error: key_from_blob: can't read key type
Sep 11 08:36:18 fortknox sshd[5002]: error: key_read: key_from_blob MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvGOorkMkY7OX6iQrTWm+JeFxysPm02PRTcOMQlIrAkYSkCody07Y5+e7IPFXoRIHgzecpZ/KeA13T6qa7x5pRu65xAyvsnkvW5YFxVkv/JNvS3EBKpOE22dkO2xC5Dv7id/Aw3QtnzdwZhllczmOoSRbtPfJK4oxLNcy6lAqiN1XQLWl/2I7GglTawJCAsXpqXdXsJGFqnQkMPWkVo3LTlcZVgzH+ChURJTRutNJCeEm8d+FzGfTICCoPveOhlytJTAXtsDLKGgEoK2XoGfUH3OGRsBq0WssINXvopfhrfhTaBxKZ7kr3WLQSHHy6A/xxlTwA81wNuiXNBdGUGSaVwIDAQAB cryptosec@fortknox.sec failed
ssh debian openssh authorized-keys
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
I am trying to configure SSH with public-key authentication on Debian.
I can't seem to get it to work because auth.log keeps saying that can't read key type:...(key line)n.
It keeps complaining about the newline and i can't remove it. I open the file, i delete the newline but it's added again.
Thank you in advance
Edit:I managed to remove the newline, but now i have the same error i had last night. I started with a 4096 RSA key but given this error i thought ssh did not accept 4096 bit keys (i know it is stupid but i had to try). Here is the error from auth.log:
Sep 11 08:36:18 fortknox sshd[5002]: error: buffer_get_string_ret: bad string length 813826338
Sep 11 08:36:18 fortknox sshd[5002]: error: key_from_blob: can't read key type
Sep 11 08:36:18 fortknox sshd[5002]: error: key_read: key_from_blob MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvGOorkMkY7OX6iQrTWm+JeFxysPm02PRTcOMQlIrAkYSkCody07Y5+e7IPFXoRIHgzecpZ/KeA13T6qa7x5pRu65xAyvsnkvW5YFxVkv/JNvS3EBKpOE22dkO2xC5Dv7id/Aw3QtnzdwZhllczmOoSRbtPfJK4oxLNcy6lAqiN1XQLWl/2I7GglTawJCAsXpqXdXsJGFqnQkMPWkVo3LTlcZVgzH+ChURJTRutNJCeEm8d+FzGfTICCoPveOhlytJTAXtsDLKGgEoK2XoGfUH3OGRsBq0WssINXvopfhrfhTaBxKZ7kr3WLQSHHy6A/xxlTwA81wNuiXNBdGUGSaVwIDAQAB cryptosec@fortknox.sec failed
ssh debian openssh authorized-keys
ssh debian openssh authorized-keys
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
edited Sep 13 '14 at 11:01
BrunoMCBraga
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
asked Sep 12 '14 at 22:38
BrunoMCBragaBrunoMCBraga
12016
12016
Could you add the relevant line from authorized_keys to your question? Feel free to munge the long hexidecimal part.
– Kenster
Sep 12 '14 at 23:22
let's see some extracts from the command line that demonstrate what is going on
– barlop
Sep 13 '14 at 0:39
add a comment |
Could you add the relevant line from authorized_keys to your question? Feel free to munge the long hexidecimal part.
– Kenster
Sep 12 '14 at 23:22
let's see some extracts from the command line that demonstrate what is going on
– barlop
Sep 13 '14 at 0:39
Could you add the relevant line from authorized_keys to your question? Feel free to munge the long hexidecimal part.
– Kenster
Sep 12 '14 at 23:22
Could you add the relevant line from authorized_keys to your question? Feel free to munge the long hexidecimal part.
– Kenster
Sep 12 '14 at 23:22
let's see some extracts from the command line that demonstrate what is going on
– barlop
Sep 13 '14 at 0:39
let's see some extracts from the command line that demonstrate what is going on
– barlop
Sep 13 '14 at 0:39
add a comment |
1 Answer
1
active
oldest
votes
Use the original .pub file that was generated (or generate a new key pair) and then add it to authorized_keys this way:
cat id_rsa.pub >> .ssh/authorized_keys
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
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%2f811063%2fssh-authorized-keys-and-newline%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
Use the original .pub file that was generated (or generate a new key pair) and then add it to authorized_keys this way:
cat id_rsa.pub >> .ssh/authorized_keys
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
add a comment |
Use the original .pub file that was generated (or generate a new key pair) and then add it to authorized_keys this way:
cat id_rsa.pub >> .ssh/authorized_keys
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
add a comment |
Use the original .pub file that was generated (or generate a new key pair) and then add it to authorized_keys this way:
cat id_rsa.pub >> .ssh/authorized_keys
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
Use the original .pub file that was generated (or generate a new key pair) and then add it to authorized_keys this way:
cat id_rsa.pub >> .ssh/authorized_keys
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
answered Sep 12 '14 at 23:03
TysonTyson
1,264811
1,264811
add a comment |
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%2f811063%2fssh-authorized-keys-and-newline%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
Could you add the relevant line from authorized_keys to your question? Feel free to munge the long hexidecimal part.
– Kenster
Sep 12 '14 at 23:22
let's see some extracts from the command line that demonstrate what is going on
– barlop
Sep 13 '14 at 0:39