Encrypt Error - There is no assurance this key belongs to the named user

[Thomas Chitwood]

Robert,

This is a error that is preventing us from encrypting. The key has been 
trusted and signed.


pub  2048R/F56DBCBE  created: 2010-09-28  expires: never       usage: SC 
                     trust: full          validity: unknown
sub  2048R/CEA16A49  created: 2010-09-28  expires: never       usage: E 
[ unknown] (1). Patrick Ashbrook <pashbrook at chcw.com>

Tom Chitwood
MCP, MCSE, CNA
Wellpoint Account
Information Technology Services Americas
Global Services, IBM
818.234.4118



From:
"Robert J. Hansen" <rjh at sixdemonbag.org>
To:
gnupg-users at gnupg.org
Date:
10/05/2010 01:07 PM
Subject:
Re: Encrypt Error - There is no assurance this key belongs to the named 
user
Sent by:
gnupg-users-bounces at gnupg.org



On 10/5/2010 2:16 PM, Thomas Chitwood wrote:
> I am getting this error when trying to encrypt a file using a public key
> generated by PGP Desktop 10.0.2 (Build 13). I am using gpg (GnuPG)
> 1.4.5. I think the error is being caused by the validity setting for
> this key in my keyring which is "validity: unknown".

Is this an error (something that actually prevents you from encrypting),
or is it just a warning (letting you know about something, but not
preventing the encryption)?

> First, is there a way to set the validity parameter in the version of
> GnuPG I am using.

This is done by validating the key and signing it with your own key.

If you want to shut off all validation checks, putting "--trust-model
always" on the command line will do that.

> Second, are there any known incompatibilities between PGP Desktop 10.0.2
> (Build 13) and gpg (GnuPG) 1.4.5?

None worth mentioning, but I believe a security vulnerability has been
discovered which affects version 1.4.5.  You may want to consider
upgrading to the latest 1.4 (1.4.10 as of this writing).

_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20101005/cec62382/attachment.htm>