The important thing here is that security is one of the few areas where it isn't safe to provide "one-size-fits-all" because people have differing requirements. By allowing evolution (and libcamel) to cope with the other micalgs it at least can coexist usefully with the PGP requirements of others. I'd settle for a variant which runs gpg and then determines what kind of signature it made, before filling out the micalg field; unfortunately that requires a larger change than the one attached.
-- Evolution data server (libcamel) can only use SHA-1 as hash https://bugs.launchpad.net/bugs/381295 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
