[Bug 247267] mail/alpine: 2.22 after upgrade from 12.0-STABLE r345375 (openssl 1.1.1b) to 12.1-RELEASE-p6 (1.1.1d no longer produces valid S/MIME signature

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247267

--- Comment #1 from Marcin Cieślak <saper at saper.info> ---

Update:

1)

those are two distinct machines, the 12.1-RELEASE-p6 has been installed from
scratch (12.1-RELEASE plus freebsd-upgrade). alpine configuration and files hav
been copied over, including S/MIME keys and certificates.

2) 

alpine 2.22 has been built on 12.0-STABLE from ports using 

# $FreeBSD: head/mail/alpine/Makefile 523707 2020-01-21 09:14:44Z joneum $

# make showconfig
===> The following configuration options are available for alpine-2.22:
     ASPELL=on: Spell checking support via GNU Aspell
     CONS25=on: Add a patch to support color for default console
     DOCS=on: Build and/or install documentation
     IPV6=on: IPv6 protocol support
     LDAP=off: LDAP protocol support
     MAILDIR=off: Add a patch to support maildir
     MOUSE=on: Mouse support
     NLS=on: Native Language Support
     NTLM=off: Support for Windows NT Lan Manager authentication
     PASSFILE=off: Support for a stored password file
     THREADS=on: Threading support

alpine 2.22 has been built on 12.1-RELEASE using ports tree

# $FreeBSD: head/mail/alpine/Makefile 523707 2020-01-21 09:14:44Z joneum $

% make showconfig
===> The following configuration options are available for alpine-2.22:
     ASPELL=on: Spell checking support via GNU Aspell
     CONS25=off: Add a patch to support color for default console
     DOCS=on: Build and/or install documentation
     IPV6=on: IPv6 protocol support
     LDAP=off: LDAP protocol support
     MAILDIR=off: Add a patch to support maildir
     MOUSE=on: Mouse support
     NLS=on: Native Language Support
     NTLM=off: Support for Windows NT Lan Manager authentication
     PASSFILE=off: Support for a stored password file
     THREADS=on: Threading support
===> Use 'make config' to modify these settings


3) "something improper" means the value
F6256B618764C64F31EF7D22F7609D2FA328F92F574048E397FFA62E99CBC917 is not a
proper SHA-256 hash of the message

-- 
You are receiving this mail because:
You are the assignee for the bug.