"If I wanted to send you something and you want to make sure it came from me, I would encrypt with my private key and only my public key can decrypt". Not exactly, this is not "encryption" per se, this is called signature. You sign with your private key and the public key confirms the message came from you. The message contents might still be intercepted. If you want confidentiality, you need to encrypt the message with the recipient public key and only the recipient private key can decrypt.
yeah, thats what I was thinking. I assume he wanted to simplify to convey the general idea. Im sure the fact that RSA decryption and signing, and encryption and verification are the same fundamental algorithms respectively :p
Encrypt with your private key is not how you should call it. That operation is called signing. To encrypt something you use a public key of someone else (or establish a shared secret and use that) and you could also sign it with your private key.
Hi, David! I’m now studying IT-security and your videos help me a lot to understand the things I couldn’t catch on my lections. Thank you for your videos.
Most lecturers upload a single piece of paper with questions and expect the students to research and do the entire assignment in Harvard standards without teaching anything.
Private Key Encryption - Document signing where docs are signu using Private key and anyone can validate it with public key. Public Key Encryption- Whatsapp - Sender encrypt message with ReceiptA's public and only ReceiptA can decrypt it with their private key.
Literally same with your email Public key is your email address.. its is accessible and available Private key is your email password. when someone is sending you a message using your email address ( Public key) and only your private key can decrypt it (Your password to access and see it) and when you will need to send it using your private key (when you are connected to your email accoun and you write your email) and it uses your public key to send your message to the other person ( your email address when it appears to the messages of the other person mailbox) that is your public key.
This is how TLS is utilized in many cases; A receiver will initiate a request to a website by; ENCRYPTing their public key with the website's public key, received from their certificate. The website will then; DECRYPT the payload with their private key, Providing the website with the receivers public key. The website will then; ENCRYPT the data requested with the receivers public key, The receiver will then; DECRYPT the data received from the website with their private key.
I'm currently studying this, and it's impossible to fully explain this in 59secs. Professor Messer's video on the subject is like 15mins along and requires l like 3 video prerequisites
yeah, but how do you provide the clients with the public key without the message been intercepted because the attackers have access to the same public key?
So it goes both ways? I always thought only Data encrypted with a public key could be decripted with the corresponding private key, Not the other way around!
If I use pub key from google, then only google can see it. That's what's happening on the browser when I send data to backend, but when we get data from google?
Not quite. Unfortunately while using Google's certificate as an example of a public key is useful to set context, when it's used as part of an https (or other TLS) session it's a lot more complicated. You want to look at DH Key Exchange.
I'm studying for my Sec+, and not an expert but basically... Google is a certificate authority (a root CA), so they can issue certificates to domains including thier own, using a public/privatekey signing process. They or another CA can issue certificates to your browser as well. Then they will run the hashing algorithms, as long as the as the keys work and none of the of the certificates are on the CRL (certificate revocation list), you will be able to decrypt any info that comes from Google or any approve site.
Yes, the purpose of cryptography like this isn't to hide information but to verify that a message came from you. Going the other way, though, anybody can encrypt a message with your public key, and then you'll be the only person who can decrypt and read it (unless your private key gets stolen).
@@Soundwave-F7Z there are other types of encryption for that-essentially, information is as secure as the key needed to unlock it, so if a public key can unlock it, it's not secure. If you wanted to hide data, you'd use a key that others _don't._ Even signing it with your own public key would accomplish that.
Wrong!!! You create a session key, encrypt the message, then encrypt the session key with public key. You dont’r try to encrypt a message with a 1024/2048 public key.
Did you know this? And that digital signatures use private and public keys?
Yes
Had to learn this when I became a middleware admin. What tripped me up later in my career was cross-signed certificates.
@@mr2ti41be me 😂 my head spins
It's the central premise of the Public Key Infrastructure (PKI).
Thanks David, please make more videos on Cryptography for beginners.
Do you want more shorts? Or long form videos? Or both?
@@davidbombal A long video on this would be great!
@@davidbombalboth would be fantastic
@@davidbombalthis short was very beneficial for me as a beginner in the crypto world!
Both. But more about creating your own private keys.
I am now about 13 years in IT career, i always love your way of simplifying things, your shorts are very short and useful, thank you 😊
"If I wanted to send you something and you want to make sure it came from me, I would encrypt with my private key and only my public key can decrypt". Not exactly, this is not "encryption" per se, this is called signature. You sign with your private key and the public key confirms the message came from you. The message contents might still be intercepted. If you want confidentiality, you need to encrypt the message with the recipient public key and only the recipient private key can decrypt.
yeah, thats what I was thinking. I assume he wanted to simplify to convey the general idea. Im sure the fact that RSA decryption and signing, and encryption and verification are the same fundamental algorithms respectively :p
You may think that your explanations helped out but I only heard many times private key and public key😂
Computerphile has a very good video explaining exactly how public and private keys word with some good analogies.
This made my understanding of keys even better. Simple but effective explanation! Thank you!!
Encrypt with your private key is not how you should call it. That operation is called signing. To encrypt something you use a public key of someone else (or establish a shared secret and use that) and you could also sign it with your private key.
Hi, David! I’m now studying IT-security and your videos help me a lot to understand the things I couldn’t catch on my lections. Thank you for your videos.
Most lecturers upload a single piece of paper with questions and expect the students to research and do the entire assignment in Harvard standards without teaching anything.
Can kind of think of it as a PO box system. The post office has a public key. Individual box owners have private key
This was explained better than I've ever heard before. Well done!
Thanks excellent well explained
Private Key Encryption - Document signing where docs are signu using Private key and anyone can validate it with public key.
Public Key Encryption- Whatsapp - Sender encrypt message with ReceiptA's public and only ReceiptA can decrypt it with their private key.
better explanation than video!
That's why my private place can only be open by a public key.
_THATS WHAT SHE SAID_
ahahahahhahaha
And big tech guys then behind scenes decrypt all basically ! Lol 😅
Thank you so much , learned so much from you!!! ❤
💓 Love from Chennai, India.
Wow sir you are great love from india ❤❤
Literally same with your email
Public key is your email address.. its is accessible and available
Private key is your email password.
when someone is sending you a message using your email address ( Public key)
and only your private key can decrypt it (Your password to access and see it)
and when you will need to send it using your private key (when you are connected to your email accoun and you write your email) and it uses your public key to send your message to the other person ( your email address when it appears to the messages of the other person mailbox) that is your public key.
This is how TLS is utilized in many cases;
A receiver will initiate a request to a website by;
ENCRYPTing their public key with the website's public key, received from their certificate.
The website will then;
DECRYPT the payload with their private key,
Providing the website with the receivers public key.
The website will then;
ENCRYPT the data requested with the receivers public key,
The receiver will then;
DECRYPT the data received from the website with their private key.
Sooo a private key is kinda like your signature, and the public key is a confirmation tool for your signature
Ahhh yeah cool. Still really confusing.
I'm currently studying this, and it's impossible to fully explain this in 59secs. Professor Messer's video on the subject is like 15mins along and requires l like 3 video prerequisites
Public key = Doorlock you can hand out
Private key = Key to said door you should keep safe
Wow..thanks alot.
I think the formula is interesting as well.
Awesome thanks ❤
Quantum computers have entered the chat for deciphering encryption.
Does the public key expire or has a timeframe? Or if you give or sent the key to someone, can it be intercepted and reused?!
Okey I'm listening
This is just PGP I had to learn it for TOR
I only listened key, key, key, key, key, key, public and private
yeah, but how do you provide the clients with the public key without the message been intercepted because the attackers have access to the same public key?
So it goes both ways? I always thought only Data encrypted with a public key could be decripted with the corresponding private key, Not the other way around!
When used the other way around it's usually referred to as 'signing'.
It's how you can verify software you're unsure about
@@aronm5329Verify what aspect of the software ?
🥶
thats so true do you do java
my brain hurts 😵
If I use pub key from google, then only google can see it. That's what's happening on the browser when I send data to backend, but when we get data from google?
Not quite. Unfortunately while using Google's certificate as an example of a public key is useful to set context, when it's used as part of an https (or other TLS) session it's a lot more complicated. You want to look at DH Key Exchange.
I'm studying for my Sec+, and not an expert but basically...
Google is a certificate authority (a root CA), so they can issue certificates to domains including thier own, using a public/privatekey signing process. They or another CA can issue certificates to your browser as well. Then they will run the hashing algorithms, as long as the as the keys work and none of the of the certificates are on the CRL (certificate revocation list), you will be able to decrypt any info that comes from Google or any approve site.
We use this daily in winscp for file sharing via sftp 22 port
Proton Mail
More obviosly it will be with some commands in shell.
Could you show it that way?
So If you encrypt a message with your private key, that means anybody with your public key can decrypt it?
Yes, the purpose of cryptography like this isn't to hide information but to verify that a message came from you.
Going the other way, though, anybody can encrypt a message with your public key, and then you'll be the only person who can decrypt and read it (unless your private key gets stolen).
@@jjpaq so if it’s purpose is not to hide information and only verify, then how do you hide it?
@@Soundwave-F7Z there are other types of encryption for that-essentially, information is as secure as the key needed to unlock it, so if a public key can unlock it, it's not secure.
If you wanted to hide data, you'd use a key that others _don't._ Even signing it with your own public key would accomplish that.
@@Soundwave-F7ZYou encrypt with recipient's public key, and only the recipient can decrypt with their private key.
@@jjpaqthis is not really encryption. This is just message signature to ensure authenticity of sender
still confusing
You want to team up are you still looking for the trazor bridge
i need more of these videos!
At the end of the video , he said i encrypt with my private key & decrypt with a public key?
This looks wrong .
Desr UA-cam algorithm, please Show me more reels like this please.
1
Maybe I am asking the wrong question, but which data are shared this way?
Hi, I am trying to code sign efi file on my arch linux using my safenet code signing token but not able to do so can anyone help me with that?
😂😂 still don't understand
i listen only pub pub pub pub public key
Can we Crack wifi passwords without using any adapter?
Pgp
So if a hacker has the publoc key, he can decrypt the data?
The public key is public. Everybody can have it. You don’t need to be a hacker.
Really simple explanation for a complex topic. Thanks.
Can you fix it if I accidentally sent a private key on accident `π`|π-;
Create new keys
Public key 🗝
Wrong!!! You create a session key, encrypt the message, then encrypt the session key with public key. You dont’r try to encrypt a message with a 1024/2048 public key.
I've 46% hs rate but damn i lack confidence like yours on the omen kill
I really got the windows 10 activation key from chat gpt