From owner-freebsd-perl@freebsd.org Sat Dec 10 18:18:56 2016 Return-Path: Delivered-To: freebsd-perl@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE4D1C70B78 for ; Sat, 10 Dec 2016 18:18:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B779A1786 for ; Sat, 10 Dec 2016 18:18:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B6E00C70B77; Sat, 10 Dec 2016 18:18:56 +0000 (UTC) Delivered-To: perl@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B690EC70B76 for ; Sat, 10 Dec 2016 18:18:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C1081784 for ; Sat, 10 Dec 2016 18:18:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBAIIuBw007233 for ; Sat, 10 Dec 2016 18:18:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 215197] security/p5-Crypt-SMIME cannot be built with LibreSSL because CMS support is disabled Date: Sat, 10 Dec 2016 18:18:56 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: z7dr6ut7gs@snkmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: perl@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2016 18:18:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215197 --- Comment #7 from John Hein --- Peter, sorry for not reading your original post closely enough and piggybac= king the FreeBSD 9 issue here. Perhaps I should open a new bug for that, but hopefully someone will pick up that patch and apply it. If not, I'll move = to a new bug. The least I can do is dig into your issue more closely. It looks like libr= essl has had CMS disabled upstream since "day one". I haven't really been follo= wing libressl much, but it seems they just have not implemented CMS. And in September they removed it from libressl-portable (commit df207699777fe7a671df25998808dac473903678). So it seems like libressl is avoiding CMS at the least. In any case, I don= 't see an easy fix. The crypt-smime change in 0.91 says: +0.19 Fri Dec 2 13:22:27 JST 2016 + - Use RFC-5652 CMS functions instead of PKCS#7 ones for better + interoperability, Suggested by Hib Engler . CMS has a backwards compatibility with + PKCS#7 so the change should introduce no compat issues. I did see another project where there was a workaround to fall back to pkcs= #7 : https://patchwork.kernel.org/patch/8463141/ In any case, I still don't know what the fix is for your issue (which seems= to perhaps be more of a problem with libressl?). If CMS is disabled by libres= sl for good reasons, perhaps Crypt-SMIME is going in the wrong direction. But= it could be that libressl is just sweeping it under the rug since they don't w= ant to deal with CMS right now. I can't read the tea leaves well enough to discern. Maybe a libressl expert could help more. Again, sorry for my too-hasty initial read of your bug report and the ensui= ng confusion. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=