Kevin J. McCarthy writes: > On Sat, Jan 29, 2022 at 10:03:33PM +0000, isdtor wrote: > > > >> ! contrib/smime.rc now uses the cms utility for SMIME > >> encryption/decryption. > > > >Kevin, can you please clarify - what is the cms utility? > > See > <https://gitlab.com/muttmua/mutt/-/commit/f0ff78a5d98ee65f7501fbce3231fbe5c886f623> > > for the commit. It changed the openssl command parameter from "smime" > to "cms" for encryption and decryption. > > >I cannot find it on my system. What does it replace in this context? > >And, is this relevant for the "set crypt_use_gpgme=yes" use case? > > No this doesn't affect gpgme. I thought so. And I did figure out that this is about openssl, about 1m after posting ;)
> >> + --with-gsasl allows configuration with the GNU SASL library, as an > >> alternative to Cyrus. > > > > >Cyrus has been around for a long time and it seems that development has > >either ceased or is proceeding at a glacial pace. Which is fine by me > >if the software is feature-complete and mature enough to have slowed > >the discovery of new bugs to a trickle. Are there any opinions on the > >list whether switching to gsasl is worthwhile for day-to-day users? It > >seems there are more than those two implementations out there, too. > > I did this in response to > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999672>. Since the > code is new, I invite you to test it. But there are certainly going to > be issues to work through, so don't feel obliged to use it. :-) Thanks, I will take a look at this bug report.
