Page MenuHome GnuPG

Explaining why there are 2 fields
Closed, ResolvedPublic

Description

When using the --export-ownertrust, it writes the trust value (integer) only to
one field out of two in total.

Example:

Instead of having:
ABCDABCD....ABCD:6:6

I get:
ABCDABCD....ABCD:6:

So when using --import-ownertrust, it doesn't update the trust properly.

Details

Version
1.4.10

Event Timeline

dor set Version to 1.4.10.
dor added a subscriber: dor.

I am not sure how you get the idea that there are 3 fields. The ownertrust is
merely the fingerprint of the primary key and the ownertrust value.

@werner:

See this example where I change the trust value to "2" as the program currently
enables (with one field):

$ echo "ABCDABCD....ABCD:3:" | gpg --import-ownertrust
gpg: changing ownertrust from 6 to 3
$ gpg --edit-key "Dor"
gpg (GnuPG) 1.4.10; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Secret key is available.

gpg: checking the trustdb
gpg: no ultimately trusted keys found
pub <key_size>R/<key_id> created: 2013-09-25 expires: never usage: SC

trust: never         validity: unknown

sub <key_size>R/<key_id> created: 2013-09-25 expires: never usage: E
[ unknown] (1). <Full name> (<nickname>) <email@addr.com>

---------------

There's a string written "unknown" - why is that? Maybe something's missing?

See another example when I set the trust value to Ultimate with two fields:

$ echo "ABCDABCD....ABCD:6:6" | gpg --import-ownertrust
gpg: changing ownertrust from 3 to 6
$ gpg --edit-key "Dor"
gpg (GnuPG) 1.4.10; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Secret key is available.

gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
pub <key_size>R/<key_id> created: 2013-09-25 expires: never usage: SC

trust: ultimate      validity: ultimate

sub <key_size>R/<key_id> created: 2013-09-25 expires: never usage: E
[ultimate] (1). <Full name> (<nickname>) <email@addr.com>

---------------

Now we can see the string "ultimate" instead of "unknown".

This is why I think there are 2 fields in the --export-ownertrust command.

dor renamed this task from --export-ownertrust lacks data to Explaining why there are 2 fields.Sep 27 2013, 10:00 AM

The trustdb is only recomputed if required. It is not done by--edit-key thus
the info there might me incorrect. Run "gpg --check-trustdb" to force an update.
Please take such discussions to a ML - it is not appropriate for a bug tracker.

No, there is no third field - check the code.

werner claimed this task.
werner added a project: Not A Bug.