Symmetric and Asymmetric EncryptionWhat is the difference between encrypting and signing in asymmetric encryption?Preventing MITM attacks on serverIs there a way to alter a public key in a way that the decryption can still be done with the private key after some alteration?Asymmetric EncryptionTwo-way encryption: I need to store passwords that can be retrievedCreating a secure, web-based password management system with the ability to share data between usersDifference between asymmetric and symmetric encryption methods?SSL use symmetric or asymmetric?Exchange keys using RSA and certificateAsymmetric encryption method in dotnetnuke
Large drywall patch supports
Valid Badminton Score?
How to Reset Passwords on Multiple Websites Easily?
Can the discrete variable be a negative number?
Is exact Kanji stroke length important?
Do sorcerers' Subtle Spells require a skill check to be unseen?
Why does indent disappear in lists?
How does it work when somebody invests in my business?
Is there a problem with hiding "forgot password" until it's needed?
when is out of tune ok?
Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?
How does buying out courses with grant money work?
A Rare Riley Riddle
Implement the Thanos sorting algorithm
Avoiding estate tax by giving multiple gifts
Replace character with another only if repeated and not part of a word
Did Dumbledore lie to Harry about how long he had James Potter's invisibility cloak when he was examining it? If so, why?
Efficient way to transport a Stargate
What is paid subscription needed for in Mortal Kombat 11?
Sequence of Tenses: Translating the subjunctive
How do I go from 300 unfinished/half written blog posts, to published posts?
Sort a list by elements of another list
What is the intuitive meaning of having a linear relationship between the logs of two variables?
How can I quit an app using Terminal?
Symmetric and Asymmetric Encryption
What is the difference between encrypting and signing in asymmetric encryption?Preventing MITM attacks on serverIs there a way to alter a public key in a way that the decryption can still be done with the private key after some alteration?Asymmetric EncryptionTwo-way encryption: I need to store passwords that can be retrievedCreating a secure, web-based password management system with the ability to share data between usersDifference between asymmetric and symmetric encryption methods?SSL use symmetric or asymmetric?Exchange keys using RSA and certificateAsymmetric encryption method in dotnetnuke
How is key shared between 2 people in symmetric encryption?
While i was studying about alice and bob example - (asymmetric )
- case 1
when alice encrypts using bob's private key how do alice know bob's private key
- case 2
when alice encrypts using bob's public key how do alice know bob's public key
- How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
encryption
add a comment |
How is key shared between 2 people in symmetric encryption?
While i was studying about alice and bob example - (asymmetric )
- case 1
when alice encrypts using bob's private key how do alice know bob's private key
- case 2
when alice encrypts using bob's public key how do alice know bob's public key
- How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
encryption
I'm voting to close this question as off-topic because this is purely about cryptography and not about programming.
– Maarten Bodewes
Mar 12 at 1:54
add a comment |
How is key shared between 2 people in symmetric encryption?
While i was studying about alice and bob example - (asymmetric )
- case 1
when alice encrypts using bob's private key how do alice know bob's private key
- case 2
when alice encrypts using bob's public key how do alice know bob's public key
- How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
encryption
How is key shared between 2 people in symmetric encryption?
While i was studying about alice and bob example - (asymmetric )
- case 1
when alice encrypts using bob's private key how do alice know bob's private key
- case 2
when alice encrypts using bob's public key how do alice know bob's public key
- How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
encryption
encryption
asked Mar 7 at 13:08
B LuthraB Luthra
122
122
I'm voting to close this question as off-topic because this is purely about cryptography and not about programming.
– Maarten Bodewes
Mar 12 at 1:54
add a comment |
I'm voting to close this question as off-topic because this is purely about cryptography and not about programming.
– Maarten Bodewes
Mar 12 at 1:54
I'm voting to close this question as off-topic because this is purely about cryptography and not about programming.
– Maarten Bodewes
Mar 12 at 1:54
I'm voting to close this question as off-topic because this is purely about cryptography and not about programming.
– Maarten Bodewes
Mar 12 at 1:54
add a comment |
1 Answer
1
active
oldest
votes
How is key shared between 2 people in symmetric encryption?
Via "a secure channel." There is no official definition of "a secure channel." Key sharing is outside the scope of the encryption algorithm and is simply assumed to happen. In practice, there are many mechanisms, from simple "Alice tells Bob the key" to elaborate key-exchange and key-agreement algorithms like Diffie-Hellman.
when alice encrypts using bob's private key how do alice know bob's private key
Alice never knows Bob's private key. That's why it's called "private."
when alice encrypts using bob's public key how do alice know bob's public key
There are many ways. Public keys are not secrets, so they can be broadly published. Exchanging public keys is trivial. The difficult part of public keys is trusting that they come from whom you think they come from. That is an entire field of study, but is generally handled by things like Certificate Authorities who everyone trusts, and who sign the keys vouching for them.
How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
The public key is sent as part of the initial handshake, and it is signed by a Certificate Authority. Then a symmetric key is agreed upon and used to encrypt session. The precise algorithm depends on the configuration, and the configurations are exchanged during the early handshakes. The reason you don't see any of this is that most HTTPS libraries do all of this for you and just show you the final result. Fundamentally, HTTPS is "HTTP over TLS" (plus a little bit of handshaking to get the TLS session started). See RFC 2817 for how TLS gets started, and see RFC 8446 for the latest version of TLS if you're interested in the details. You can also search for "Introduction to TLS" for numerous articles on the details.
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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%2fstackoverflow.com%2fquestions%2f55044577%2fsymmetric-and-asymmetric-encryption%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
How is key shared between 2 people in symmetric encryption?
Via "a secure channel." There is no official definition of "a secure channel." Key sharing is outside the scope of the encryption algorithm and is simply assumed to happen. In practice, there are many mechanisms, from simple "Alice tells Bob the key" to elaborate key-exchange and key-agreement algorithms like Diffie-Hellman.
when alice encrypts using bob's private key how do alice know bob's private key
Alice never knows Bob's private key. That's why it's called "private."
when alice encrypts using bob's public key how do alice know bob's public key
There are many ways. Public keys are not secrets, so they can be broadly published. Exchanging public keys is trivial. The difficult part of public keys is trusting that they come from whom you think they come from. That is an entire field of study, but is generally handled by things like Certificate Authorities who everyone trusts, and who sign the keys vouching for them.
How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
The public key is sent as part of the initial handshake, and it is signed by a Certificate Authority. Then a symmetric key is agreed upon and used to encrypt session. The precise algorithm depends on the configuration, and the configurations are exchanged during the early handshakes. The reason you don't see any of this is that most HTTPS libraries do all of this for you and just show you the final result. Fundamentally, HTTPS is "HTTP over TLS" (plus a little bit of handshaking to get the TLS session started). See RFC 2817 for how TLS gets started, and see RFC 8446 for the latest version of TLS if you're interested in the details. You can also search for "Introduction to TLS" for numerous articles on the details.
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
add a comment |
How is key shared between 2 people in symmetric encryption?
Via "a secure channel." There is no official definition of "a secure channel." Key sharing is outside the scope of the encryption algorithm and is simply assumed to happen. In practice, there are many mechanisms, from simple "Alice tells Bob the key" to elaborate key-exchange and key-agreement algorithms like Diffie-Hellman.
when alice encrypts using bob's private key how do alice know bob's private key
Alice never knows Bob's private key. That's why it's called "private."
when alice encrypts using bob's public key how do alice know bob's public key
There are many ways. Public keys are not secrets, so they can be broadly published. Exchanging public keys is trivial. The difficult part of public keys is trusting that they come from whom you think they come from. That is an entire field of study, but is generally handled by things like Certificate Authorities who everyone trusts, and who sign the keys vouching for them.
How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
The public key is sent as part of the initial handshake, and it is signed by a Certificate Authority. Then a symmetric key is agreed upon and used to encrypt session. The precise algorithm depends on the configuration, and the configurations are exchanged during the early handshakes. The reason you don't see any of this is that most HTTPS libraries do all of this for you and just show you the final result. Fundamentally, HTTPS is "HTTP over TLS" (plus a little bit of handshaking to get the TLS session started). See RFC 2817 for how TLS gets started, and see RFC 8446 for the latest version of TLS if you're interested in the details. You can also search for "Introduction to TLS" for numerous articles on the details.
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
add a comment |
How is key shared between 2 people in symmetric encryption?
Via "a secure channel." There is no official definition of "a secure channel." Key sharing is outside the scope of the encryption algorithm and is simply assumed to happen. In practice, there are many mechanisms, from simple "Alice tells Bob the key" to elaborate key-exchange and key-agreement algorithms like Diffie-Hellman.
when alice encrypts using bob's private key how do alice know bob's private key
Alice never knows Bob's private key. That's why it's called "private."
when alice encrypts using bob's public key how do alice know bob's public key
There are many ways. Public keys are not secrets, so they can be broadly published. Exchanging public keys is trivial. The difficult part of public keys is trusting that they come from whom you think they come from. That is an entire field of study, but is generally handled by things like Certificate Authorities who everyone trusts, and who sign the keys vouching for them.
How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
The public key is sent as part of the initial handshake, and it is signed by a Certificate Authority. Then a symmetric key is agreed upon and used to encrypt session. The precise algorithm depends on the configuration, and the configurations are exchanged during the early handshakes. The reason you don't see any of this is that most HTTPS libraries do all of this for you and just show you the final result. Fundamentally, HTTPS is "HTTP over TLS" (plus a little bit of handshaking to get the TLS session started). See RFC 2817 for how TLS gets started, and see RFC 8446 for the latest version of TLS if you're interested in the details. You can also search for "Introduction to TLS" for numerous articles on the details.
How is key shared between 2 people in symmetric encryption?
Via "a secure channel." There is no official definition of "a secure channel." Key sharing is outside the scope of the encryption algorithm and is simply assumed to happen. In practice, there are many mechanisms, from simple "Alice tells Bob the key" to elaborate key-exchange and key-agreement algorithms like Diffie-Hellman.
when alice encrypts using bob's private key how do alice know bob's private key
Alice never knows Bob's private key. That's why it's called "private."
when alice encrypts using bob's public key how do alice know bob's public key
There are many ways. Public keys are not secrets, so they can be broadly published. Exchanging public keys is trivial. The difficult part of public keys is trusting that they come from whom you think they come from. That is an entire field of study, but is generally handled by things like Certificate Authorities who everyone trusts, and who sign the keys vouching for them.
How is Https a type of asymmetric encryption? I never see keys generating? Even if keys are generated then where are they stored?And how do i never decrypt those encryptions?
The public key is sent as part of the initial handshake, and it is signed by a Certificate Authority. Then a symmetric key is agreed upon and used to encrypt session. The precise algorithm depends on the configuration, and the configurations are exchanged during the early handshakes. The reason you don't see any of this is that most HTTPS libraries do all of this for you and just show you the final result. Fundamentally, HTTPS is "HTTP over TLS" (plus a little bit of handshaking to get the TLS session started). See RFC 2817 for how TLS gets started, and see RFC 8446 for the latest version of TLS if you're interested in the details. You can also search for "Introduction to TLS" for numerous articles on the details.
answered Mar 7 at 13:41
Rob NapierRob Napier
206k28303431
206k28303431
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
add a comment |
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
1. Where are these public keys published?
– B Luthra
Mar 8 at 12:50
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
Which public keys? In TLS interactions, the public key is just sent as part of the handshake. In PGP-derived systems, they're generally stored on keyservers. There's no single way this is done, and there may be no particular place they're published.
– Rob Napier
Mar 8 at 14:33
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
"Exchanging public keys is trivial." - good thing that you immediately contradict that at length.
– Henk Holterman
Mar 9 at 21:42
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
@HenkHolterman Exchanging public keys is trivial. It's a few kB of data that requires no confidentiality, and carries its own integrity check. It's as easy to exchanging a small GIF. Trusting public keys is hard, but that's all done outside of the public key itself, and far outside the exchange step.
– Rob Napier
Mar 10 at 14:41
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f55044577%2fsymmetric-and-asymmetric-encryption%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
I'm voting to close this question as off-topic because this is purely about cryptography and not about programming.
– Maarten Bodewes
Mar 12 at 1:54