First, the program needs to use a starting key to start trust paths, the "from" key. Because most people probably are not connected to the web of trust (or, more specifically, to the "strong set" of the web of trust), it tries to set a reasonable default.
This default is probably the best-connected key, the "c't crypto campaign" key. The connections are analyzed and shown here:
http://www.lysator.liu.se/~jc/wotsap/leafoftrust.html
The connections are so strong because c't is a German magazine (website www.heise.de) which has been promoting the use of PGP for years, and worked as kind of an ad hoc CA for tech people.
The "FROM" key can be set by configuration options, and in fact anyone who uses this should set it a an own key he trusts, because it is not a good idea to introduce single points of failure in the trust web.
Said all that, the program should NOT, under NO circumstance, change the local trust DB of the user, because this could affect trust decisions. If it does that, this is a significant and serious error, which I will fix as soon as possible. Please, do not use this for production purposes before it's checked and fixed.
I'll check and if required fix that today (can't do it right now), please have a bit of patience.
And thanks for the feedback!
I apologize! To remedy the issue, please clear the trust value of key with ID "DAFFB000" by calling
gpg edit-key DAFFB000
and then command "trust", set value to "unknown", save and quit. After that, the trust value should be "unknown". If in any doubt, restore your trustdb from backup.
Update follows soon.