Nice catch, as I'm starting to think how on earth I'd use the Asymmetric method to enc/dec reports I'm going to send to the user through email if I have to hold the private key to be able to encrypt. How would I manage millions of keys for my users on my servers for this to work. Your message removes the confusion. Thank you
This just came in the perfect time for me. I'm adding a feature to the app I'm working on to encrypt a generated PDF using GPG key before emailing it to the user. Thank you.
@DJ Ware what I understand from your video is that the Asymmetrical encryption can be only done using the private key then the receiver can use the public key to decrypt the document. So, I'd like to know if it's a viable approach to use this method to encrypt those PDF reports before sending them to user using Asymmetric method. In this scenario, I suppose we'd have to generate a key-pair for each user on our servers, then use those keys to encrypt the PDF. We would then show the Public key to the user in their settings page. They will then be able to use that public key to decrypt the PDF. I believe the issue that would come with this method is how to manage hundreds of thousands of GPG keys or even millions on the server side keyring. So, what would you propose for this to be scalable and easier to do while being secure.
19:05 Isn't it the other way around. Public key to encrypt, private key to decrypt. I think signing is the way you described. Great video anyway, I always learn something from them.
I put a pinned comment in to correct this if I had a senior moment. Signatures is true, except Microsoft reverses the order on their web services...just because they have to do it backwards like they do everything else :D
Thanks for going over this. I've used this to generate keys for 3rd parties, but I've never really learned how to use it. Do you prefer zsh or did it come with your kde setup?
I've used gpg for years and i still get confused. I thought async used the public key to encrypt and the private key to decrypt. That way you need a private key to access the file
I hope this wasn't a senior moment: For asymmetric keys: the Public Key is used to encrypt, the Private Key is used to decrypt
Nice catch, as I'm starting to think how on earth I'd use the Asymmetric method to enc/dec reports I'm going to send to the user through email if I have to hold the private key to be able to encrypt. How would I manage millions of keys for my users on my servers for this to work. Your message removes the confusion. Thank you
This just came in the perfect time for me. I'm adding a feature to the app I'm working on to encrypt a generated PDF using GPG key before emailing it to the user. Thank you.
@DJ Ware what I understand from your video is that the Asymmetrical encryption can be only done using the private key then the receiver can use the public key to decrypt the document. So, I'd like to know if it's a viable approach to use this method to encrypt those PDF reports before sending them to user using Asymmetric method. In this scenario, I suppose we'd have to generate a key-pair for each user on our servers, then use those keys to encrypt the PDF. We would then show the Public key to the user in their settings page. They will then be able to use that public key to decrypt the PDF.
I believe the issue that would come with this method is how to manage hundreds of thousands of GPG keys or even millions on the server side keyring.
So, what would you propose for this to be scalable and easier to do while being secure.
19:05 Isn't it the other way around. Public key to encrypt, private key to decrypt.
I think signing is the way you described.
Great video anyway, I always learn something from them.
I put a pinned comment in to correct this if I had a senior moment. Signatures is true, except Microsoft reverses the order on their web services...just because they have to do it backwards like they do everything else :D
Thank you so much for creating this lecture.
Thank you sir.
I’ve been using PGP since the original incarnation, and use GPG quite a bit. It’s still complicated.
Why? Four applications, two of which (sign and decrypt) require a private key (insert password), two of which (verify and encrypt) don't.
Informative video, as always.
Great video ty very much, I was hoping it would include the new ADSK feature, I've seen no other video approaching it...
Thanks for going over this. I've used this to generate keys for 3rd parties, but I've never really learned how to use it. Do you prefer zsh or did it come with your kde setup?
Prefer it and you are welcome
Excellent tutorial. Thank you for sharing @CyberGizmo
I've used gpg for years and i still get confused. I thought async used the public key to encrypt and the private key to decrypt. That way you need a private key to access the file
That is correct, public key encrypts, private key decrypts
AI generated thumbnail? 🤔 looks pretty cool
Partially, yes, just the image part, I did the text part and thanks
wonderful thumbnail for this video ! do you have a link for that desktopwallpaper? love it too !
I made it, and sorry I do not have a public link to it yet, may do that in the future if enough people are interested
Thoughts on Sequoia (Rust) for PGP?
Well, "Only from You" actually means "Anyone who has access to your private part."
👍👍
👍
DJ? Where?
Incorrect with respect to asymmetric messages
I can only encrypt a message to YOU using YOUR public key
You decrypt it with YOUR private key
Pinned comment posted day of the video addressed already corrected that mistake