Re: Encrypting Messages

thank you for all your answers. I guess i was really confused on the public
and private key situation, but that cleared it up. thanks again.


"Vanguard" <vanguard.news@xxxxxxxxxxxx> wrote in message
news:exsYpx3IGHA.3100@xxxxxxxxxxxxxxxxxxxxxxx
> "Rome" <coolromeo29@xxxxxxxxx> wrote in message
> news:OKq9bkvIGHA.3816@xxxxxxxxxxxxxxxxxxxxxxx
> I recently purchased a Email Certificate from Verisign for Encryption and
> Digitally Signing My email and it works fine with everybody who has
> outlook. Why is it that i cant send an encrypted email with someone thats
> using yahoo? i was messing with sending myself an encrypted email, and got
> it to work an hour later. why is it that in order for me to send an
> encrypted message to someone i have to have their certificated stored in
> my adress book?
>
>
> --- REPLY SEPARATOR ---
> (only needed because the OP use quoted-printable format in their post)
>
> Because you did not train yourself by researching on how certificates
> work. You encrypt a messages using SOMEONE ELSE's public key. The only
> person that can decrypt that message is the one that has the matching
> private key. You digitally sign a message so you can give your PUBLIC key
> to someone else, who can then use that public key to encrypt a message
> they send to you whereupon you use your private key to decrypt their
> message. Similarly, for you to send someone else an encrypted message
> means you have to get their public key used to encrypt the message.
>
> You want to send them a digitally signed message:
> Use the public key from your certificate.
>
> You want to send them an encrypted message:
> Use THEIR *public* key in THEIR certificate.
> They decrypt using THEIR *private* key.
>
> They want to send you a digitally signed message:
> They use their public key from their certificate.
>
> They want to send you an encrypte message:
> They need to use YOUR public key from YOUR certificate.
> You decrypt using YOUR *private* key.
>
> The certicate owner retains safety of their certificate by NOT divulging
> their private key. The certificate owner gets a public and private key.
> Everyone else only gets the public key. Since no one but the certificate
> owner has the private key, no one else can [easily] decrypt a message
> encrypted with their public key (i.e., everyone else only gets half of the
> key).
>
> --
> __________________________________________________
> Post replies to the newsgroup. Share with others.
> For e-mail: Remove "NIX" and add "#VN" to Subject.
> __________________________________________________
>


.

Relevant Pages

  • [OT] Re: Basic question about Public Private Key Pairs
    ... > and private keys allow me to decrypt, but vice versa is not possible (or ... a public key and a corresponding private key. ... You can encrypt something with each key; ...
    (microsoft.public.dotnet.security)
  • Re: Back Doors
    ... >> Design into the system a master key. ... Encrypt that with public key. ... Decrypt random symmetric key with private key. ...
    (sci.crypt)
  • Re: DRA is Decrypting Files when it shouldnt be!!!
    ... > EFS is allowing the RA to decrypt 200 files that were encrypted BEFORE an RA ... > encryption to get the RA to decrypt encrypted files. ... the default RA certificate was used. ... certificate and private key only when needed). ...
    (microsoft.public.windowsxp.security_admin)
  • Re: More on learning "Public Key Authentication"
    ... let me say that in public key ... >> encrypt the result with Alice's public key. ... >> is sent to Alice who decrypts the message with her private key (which ... > encrypted with my private key and they can then decrypt it with the ...
    (comp.sys.mac.system)
  • Re: Encryption Problem
    ... the private key associated to that public key to decrypt that message. ... private key associated to the public key you are using to encrypt on the ... > certificate present in the certificate store. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)