From owner-freebsd-security@freebsd.org Mon Jan 4 13:01:11 2016 Return-Path: Delivered-To: freebsd-security@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 C508DA6088D for ; Mon, 4 Jan 2016 13:01:11 +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 9AC79136C for ; Mon, 4 Jan 2016 13:01:11 +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 u04D1Ada032448 for ; Mon, 4 Jan 2016 13:01:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-security@FreeBSD.org Subject: [Bug 193871] Certificates in /etc/ssl/certs not considered by pkg and fetch Date: Mon, 04 Jan 2016 13:01:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: feature, needs-patch, needs-qa, security X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: john@saltant.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: des@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? X-Bugzilla-Changed-Fields: attachments.created 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-Mailman-Approved-At: Mon, 04 Jan 2016 13:55:32 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2016 13:01:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193871 --- Comment #6 from John W. O'Brien --- Created attachment 165049 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D165049&action= =3Dedit test for /etc/ssl/cert.pem existence to avoid masking SSL_CA_CERT_PATH I have tested this and it works as intended. If you would like evidence, I would need to boil down the test results to a form suitable for sharing. In the course of testing, I realized that while the fallback to OpenSSL defaults is good, the inconsistency between the semantics of the libfetch l= ayer of environment variables (SSL_CA_CERT_FILE, SSL_CA_CERT_PATH) and the defau= lts in their absence and the libcrypto layer of environment variables (SSL_CERT_FILE, SSL_CERT_DIR) and the defaults in their absence is not so g= ood. To wit, libfetch has a default file---two, in fact---but no default path, whereas libcrypto has both, and the existence of either of the libfetch def= ault files will prevent the fallback to the OpenSSL defaults. As I understand it, the reason that libfetch has a default to begin with, rather than always using the OpenSSL default behavior, is mainly (solely?) = to allow the bundle from security/cs-nss-root to be picked up as the system default, at least for libfetch and its consumers (like pkg), merely by virt= ue of its installing a /usr/local/etc/ssl/cert.pem symlink, which is not a pla= ce OpenSSL looks by default. I don't have a recommendation at the moment, but when I do, it might be to = add /usr/local/etc/certs as a path default for libfetch. --=20 You are receiving this mail because: You are on the CC list for the bug.=