When receiving a clear text mail, no header is added by
GPG relay. It is therefore trivial to forge a GPG relay
header pretending that a mail is signed by someone key.
This mail cannot be distinguished by user from a truly
signed email.
Well, there is currenty already one (alot less intrusive) way to
tell if a mail is forged or not: If it does not start with a "X-
GPGrelay-Received:"-line (double check: it _MUST_ be the
very first line!).
Well, maybe you're right and I should add a "also mark passed-
through mail-bodies"-option.
I should point out, that there are also some machine-readable
header-fields generated by GPGrelay, which will also be
checked when receiving to detect forged mails.
These fields can be used by your email-client to e.g. "color"
the mails (of course your client has to have that feature).
But think primarily of GPGrelay as a privacy-tool!
In case you really need to rely on signatures, you shouldn't
believe in automatic signing/verifying anyway...
Bye!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=130931
Hi!
Well, there is currenty already one (alot less intrusive) way to
tell if a mail is forged or not: If it does not start with a "X-
GPGrelay-Received:"-line (double check: it _MUST_ be the
very first line!).
Well, maybe you're right and I should add a "also mark passed-
through mail-bodies"-option.
I should point out, that there are also some machine-readable
header-fields generated by GPGrelay, which will also be
checked when receiving to detect forged mails.
These fields can be used by your email-client to e.g. "color"
the mails (of course your client has to have that feature).
But think primarily of GPGrelay as a privacy-tool!
In case you really need to rely on signatures, you shouldn't
believe in automatic signing/verifying anyway...
Bye!