SYMANTEC ENCRYPTION DESKTOP VERIFY KEY FULL

Person 1 now sends an encrypted email back with word2 in it.

This combined with num2 which ensures that the email came from the person that Person 1 spoke to (namely Person 2) earlier that day comfirms to Person 1 that person he spoke to earlier owns that private key and that email address. The only way word1 could be in this email is if the person who owns the key Person 2 presented also has access to the email - they had to get the email and decrypt it.

Person 2 now sends an encrypted email back to Person 1 including word1, num2, and word2.

We'll see why word1 was included in a moment.

The fact that this email has num2 lets Person 2 know that this email came from the person he spoke to earlier that day, namely Person 1 - the only person he told the number to.

Person 1 sends an encrypted email to the email in the UID of Person 2's key.

Person 1 and Person 2 tell each other their numbers but do not tell each other their words.

Person 2 does the same, we'll call them word2 and num2.

Person 1 thinks of a number and word, which we'll call word1 and num1.

The other way is more complicated and I've only seen it practiced a few times. This ensures that the person who you are verifying has access to the private key and also owns that email address. In order for the person to get that signature and make it available (by, for example, uploading it to keyservers), they have to have both the private key and the email address. You then encrypt-email the signed UID to the email address in that UID. When signing the key (which is covered below) rather than the default of signing all UIDs on the key, you sign each UID separately. The one this site will concentrate on the simpler of the two, but in this section I'll explain both. If you sign a key for Bill Doe and verify the identity, but don't verify the email which is, say, you've now vouched for email signed by that key from that email. One of PGP's most common uses is to verify email, so verifying an email address is critical. This is one many people forget, but it's important. Ownership of their email and the private key

SYMANTEC ENCRYPTION DESKTOP VERIFY KEY FULL

In order to set full verification (3), I require two forms of ID, at least one of which is photo ID, and at least one of which is government-issued. It is up to you how much ID you want to see and to what level you will set your verification of the key during signing.

This is to be sure that this person has the legal right to use the name they are using. Even if you work with the person or know the person, it's important to do this step if you have never checked their legal identity. In order to verify their identity, you'll need them to provide at least one form of photo ID. If you or they generate this by grabbing their key from a server and comparing it to what you're about to sign, then you're not verifying anything! Think about it: if you're trying to verify the integrity of something, you can't use that something to do the verification. Therefore, this should be generated by them on the machine that holds their secret key or better yet, from their private key.

This is to check that the copy of the key you have obtained either from a keyserver or email is actually the key this person uses and you haven't somehow gotten a forged key. In order to verify the key you'll want them to bring you a hard copy of their fingerprint. So lets talk about each one of these verifications The key you are to sign That's a pretty strong statement! As such there are certain precautions you should take. I believe this key belongs to the name in it, and the email listed also belongs to that person. Signing someone's key is saying to the world I have verified the identify of this person to the extent which I put in the signing.

Symantec encryption desktop verify key