Hi Nicolai, all-- On 04/20/2014 09:30 AM, Nicolai Josuttis wrote:
> a first implementation to provide the ability to
> automatically encrypt messages if all valid keys are known
this is a neat idea, but...
> without the need to have a rule for it
> into the sub-branch (derived from master):
> AutoSendEncrypted
>
> In fact, you can choose between:
>> Automatically send encrypted?
>> - Never
>> No automatically encrypted sending except explicitly triggered by rules
>> - With full trust
>> Automatically send encrypted when all keys are known and valid and have
>> full trust
>> - With marginal trust
>> Automatically send encrypted when all keys are known and valid and have at
>> least marginal trust
>> - With unknown trust
>> Automatically send encrypted when all keys are known and valid and have no
>> explicit mistrust
the above terms are deeply confusing. "valid keys" are not the same as
"trusted keys". In OpenPGP, a "valid" certificate means that we believe
that the key belongs to the person named in the User ID. a "trusted"
key means that we're willing to believe OpenPGP certifications made by
this key.
I think it's a really bad idea to make encryption contingent on trust
settings; it should only be contingent on validity.
Can you clarify this?
regards,
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
