encrypt problem
Leigh S. Jones
kr6x@kr6x.com
Thu May 23 16:12:01 2002
This is a multi-part message in MIME format.
------=_NextPart_000_033D_01C2022A.54643310
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Re: encrypt problemI'm not exactly sure what the core problem is. =
Perhaps when
you log on via SSH your environment is different than it is
when you log on locally. I'm not quite sure you are the same
user name or whether your ~ directory is set properly. GnuPG
will look for your keyring file in ~/.gnupg -- is it able to find a=20
keyring that you have rights to?
----- Original Message -----=20
From: Charly Avital=20
To: Dmitry Gerasimov ; gnupg-users@gnupg.org=20
Sent: Thursday, May 23, 2002 6:27 AM
Subject: Re: encrypt problem
At 1:09 AM +0400 5/23/02, Dmitry Gerasimov wrote:
Hello,
I have two problems, but maybe they have the same source problem.
GnuPG 1.0.6-2
Problem 1.
When I try to encrypt via SSH i get this response:
_______________________
Could not find a valid trust path to the key. Let's see whether we
can assign some missing owner trust values.
No path leading to one of our keys found.
....
It is NOT certain that the key belongs to its owner.
If you *really* know what you are doing, you may answer
the next question with yes
Use this key anyway?
_______________________
i have only one public key in the keyring and I set Full trust to that =
key. What is the problem here? Why can't it find paths? What can I do to =
avoid that?
[...]
It seems that the trust you have set to that key refers to how you =
trust its owner to introduce other people's keys.
If you want to use that key for encryption you can:
- sign it locally. The signature will not be exportable.
- configure gpg's options to use also untrusted keys for encryption. =
Not a good idea, but possible if you can live with it.
Charly
------=_NextPart_000_033D_01C2022A.54643310
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: encrypt problem</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<STYLE type=3Dtext/css>BLOCKQUOTE {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
DL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
UL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
OL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
LI {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
</STYLE>
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'm not exactly sure what the core =
problem=20
is. Perhaps when</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>you log on via SSH your environment is =
different=20
than it is</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>when you log on locally. I'm not =
quite sure=20
you are the same</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>user name or whether your ~ directory =
is set=20
properly. G</FONT><FONT face=3DArial size=3D2>nuPG</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>will look for your keyring file in =
~/.gnupg -- is=20
it able to find a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>keyring that you have rights =
to?</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dshavital@mac.com href=3D"mailto:shavital@mac.com">Charly =
Avital</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Ddgerasimov@mtu-net.ru=20
href=3D"mailto:dgerasimov@mtu-net.ru">Dmitry Gerasimov</A> ; <A=20
title=3Dgnupg-users@gnupg.org=20
href=3D"mailto:gnupg-users@gnupg.org">gnupg-users@gnupg.org</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, May 23, 2002 =
6:27=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: encrypt =
problem</DIV>
<DIV><BR></DIV>
<DIV>At 1:09 AM +0400 5/23/02, Dmitry Gerasimov wrote:</DIV>
<DIV>Hello,</DIV>
<DIV>I have two problems, but maybe they have the same source =
problem.</DIV>
<DIV> </DIV>
<DIV>GnuPG 1.0.6-2</DIV>
<DIV> </DIV>
<DIV>Problem 1.</DIV>
<DIV>When I try to encrypt via SSH i get this response:</DIV>
<DIV>_______________________</DIV>
<DIV>Could not find a valid trust path to the key. Let's see =
whether=20
we<BR>can assign some missing owner trust values.<BR><BR>No path =
leading to=20
one of our keys found.</DIV>
<DIV>....</DIV>
<DIV>It is NOT certain that the key belongs to its owner.<BR>If you =
*really*=20
know what you are doing, you may answer<BR>the next question with=20
yes<BR><BR>Use this key anyway?</DIV>
<DIV>_______________________</DIV>
<DIV> </DIV>
<DIV>i have only one public key in the keyring and I set Full trust to =
that=20
key. What is the problem here? Why can't it find paths? What can I do =
to avoid=20
that?</DIV>
<DIV>[...]</DIV>
<DIV><BR></DIV>
<DIV>It seems that the trust you have set to that key refers to how =
you trust=20
its owner to introduce other people's keys.</DIV>
<DIV><BR></DIV>
<DIV>If you want to use that key for encryption you can:</DIV>
<DIV>- sign it locally. The signature will not be exportable.</DIV>
<DIV>- configure gpg's options to use also untrusted keys for =
encryption. Not=20
a good idea, but possible if you can live with it.</DIV>
<DIV><BR></DIV>
<DIV>Charly</DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_033D_01C2022A.54643310--