You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the only known bug is #101. We always specify "pgp-sha1" as "micalg" parameter for "multipart/signed" MIME type, disregarding what digest algorithm we actually use during signature calculation. Both RNP and GPGME adapters are affected, and in the latter case fixing it may be non-trivial.
This bug does not break signature in any way, however it makes one-pass verification impossible. Nevertheless, mail-gpg gem does exactly the same…
I am fixing it now, but perhaps it is not critical, and we can make a release.
Currently, the only known bug is #101. We always specify "pgp-sha1" as "micalg" parameter for "multipart/signed" MIME type, disregarding what digest algorithm we actually use during signature calculation. Both RNP and GPGME adapters are affected, and in the latter case fixing it may be non-trivial.
This bug does not break signature in any way, however it makes one-pass verification impossible. Nevertheless,
mail-gpg
gem does exactly the same…I am fixing it now, but perhaps it is not critical, and we can make a release.
cc @ronaldtse @ribose-jeffreylau
The text was updated successfully, but these errors were encountered: