I've generated a public key: 2976 bits …?
up vote
1
down vote
favorite
I have generated a public key via ssh-keygen -f foo. The key inside the file foo.pub is AAAAB3NzaC1yc2EAAAADAQABAAABAQDaJ1UGxfjTCzuVNvgjOyK/NF5KFDO2qUREGd9PBB+zJotS85XO9hQjq5XhdekXHfhCM/h3AeGW/xH+XfQIaNd6Lygkts3xls7FCqMVH4PxDpLTSQbbZCV+peMV6xNVv468SD07TGIp9RC0FFuR79tnz28X9RzKCUGrzpu38pAyPs4X3BGgMsc6IcPIfPnEZ61RMWiiouyShKuhD/G68DeTdokmmK0EnO2qMXgu7xsAw+2gSpotIgAPulAPpQr5+Cgit94GpN2Vy9OvhEGT3oqHsR8P4zoJ3rWppiCUDRvFZS/fQsRoNj59LRcPRVE0V8wLnpoEZOu85wBMiIfiac3F. That is 372 characters. 1 character is 8 bits, thus my key is a 372 * 8 = 2976 bit key. That cannot be true because man ssh-keygen says that the default is 2048 bits. Where am I wrong?
ssh ssh-keys public-key
asked Nov 30 at 15:54
Robert
111
add a comment |
up vote
1
down vote
favorite
I have generated a public key via ssh-keygen -f foo. The key inside the file foo.pub is AAAAB3NzaC1yc2EAAAADAQABAAABAQDaJ1UGxfjTCzuVNvgjOyK/NF5KFDO2qUREGd9PBB+zJotS85XO9hQjq5XhdekXHfhCM/h3AeGW/xH+XfQIaNd6Lygkts3xls7FCqMVH4PxDpLTSQbbZCV+peMV6xNVv468SD07TGIp9RC0FFuR79tnz28X9RzKCUGrzpu38pAyPs4X3BGgMsc6IcPIfPnEZ61RMWiiouyShKuhD/G68DeTdokmmK0EnO2qMXgu7xsAw+2gSpotIgAPulAPpQr5+Cgit94GpN2Vy9OvhEGT3oqHsR8P4zoJ3rWppiCUDRvFZS/fQsRoNj59LRcPRVE0V8wLnpoEZOu85wBMiIfiac3F. That is 372 characters. 1 character is 8 bits, thus my key is a 372 * 8 = 2976 bit key. That cannot be true because man ssh-keygen says that the default is 2048 bits. Where am I wrong?
ssh ssh-keys public-key
asked Nov 30 at 15:54
Robert
111
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have generated a public key via ssh-keygen -f foo. The key inside the file foo.pub is AAAAB3NzaC1yc2EAAAADAQABAAABAQDaJ1UGxfjTCzuVNvgjOyK/NF5KFDO2qUREGd9PBB+zJotS85XO9hQjq5XhdekXHfhCM/h3AeGW/xH+XfQIaNd6Lygkts3xls7FCqMVH4PxDpLTSQbbZCV+peMV6xNVv468SD07TGIp9RC0FFuR79tnz28X9RzKCUGrzpu38pAyPs4X3BGgMsc6IcPIfPnEZ61RMWiiouyShKuhD/G68DeTdokmmK0EnO2qMXgu7xsAw+2gSpotIgAPulAPpQr5+Cgit94GpN2Vy9OvhEGT3oqHsR8P4zoJ3rWppiCUDRvFZS/fQsRoNj59LRcPRVE0V8wLnpoEZOu85wBMiIfiac3F. That is 372 characters. 1 character is 8 bits, thus my key is a 372 * 8 = 2976 bit key. That cannot be true because man ssh-keygen says that the default is 2048 bits. Where am I wrong?
ssh ssh-keys public-key
asked Nov 30 at 15:54
Robert
111
I have generated a public key via ssh-keygen -f foo. The key inside the file foo.pub is AAAAB3NzaC1yc2EAAAADAQABAAABAQDaJ1UGxfjTCzuVNvgjOyK/NF5KFDO2qUREGd9PBB+zJotS85XO9hQjq5XhdekXHfhCM/h3AeGW/xH+XfQIaNd6Lygkts3xls7FCqMVH4PxDpLTSQbbZCV+peMV6xNVv468SD07TGIp9RC0FFuR79tnz28X9RzKCUGrzpu38pAyPs4X3BGgMsc6IcPIfPnEZ61RMWiiouyShKuhD/G68DeTdokmmK0EnO2qMXgu7xsAw+2gSpotIgAPulAPpQr5+Cgit94GpN2Vy9OvhEGT3oqHsR8P4zoJ3rWppiCUDRvFZS/fQsRoNj59LRcPRVE0V8wLnpoEZOu85wBMiIfiac3F. That is 372 characters. 1 character is 8 bits, thus my key is a 372 * 8 = 2976 bit key. That cannot be true because man ssh-keygen says that the default is 2048 bits. Where am I wrong?
ssh ssh-keys public-key
ssh ssh-keys public-key
asked Nov 30 at 15:54
Robert
111
asked Nov 30 at 15:54
Robert
111
asked Nov 30 at 15:54
Robert
111
asked Nov 30 at 15:54
Robert
111
asked Nov 30 at 15:54
Robert
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
The .pub file contains a base64 encoded version of your key as well as some additional information, which leads to seemingly more than 2048 bits, due to the encoding overhead.
answered Nov 30 at 16:10
DerFlob
214
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
The .pub file contains a base64 encoded version of your key as well as some additional information, which leads to seemingly more than 2048 bits, due to the encoding overhead.
answered Nov 30 at 16:10
DerFlob
214
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
add a comment |
up vote
2
down vote
The .pub file contains a base64 encoded version of your key as well as some additional information, which leads to seemingly more than 2048 bits, due to the encoding overhead.
answered Nov 30 at 16:10
DerFlob
214
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
add a comment |
up vote
2
down vote
up vote
2
down vote
The .pub file contains a base64 encoded version of your key as well as some additional information, which leads to seemingly more than 2048 bits, due to the encoding overhead.
answered Nov 30 at 16:10
DerFlob
214
The .pub file contains a base64 encoded version of your key as well as some additional information, which leads to seemingly more than 2048 bits, due to the encoding overhead.
answered Nov 30 at 16:10
DerFlob
214
answered Nov 30 at 16:10
DerFlob
214
answered Nov 30 at 16:10
DerFlob
214
answered Nov 30 at 16:10
DerFlob
214
214
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
add a comment |
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
oh okay I understand, it makes sense. If I had a sequence of 1's and 0's there could be an 8-bit sequence which doesn't refer to a readable ascii char, right? But since the key is supposed to be printed into a file there must be some sort of conversion which is "base64". I'll read more about it, thanks already for pointing me in the right direction!
– Robert
Nov 30 at 16:20
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.
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%2fsuperuser.com%2fquestions%2f1379777%2five-generated-a-public-key-2976-bits%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