From owner-freebsd-ports-bugs@freebsd.org Tue Sep 20 18:31:33 2016 Return-Path: Delivered-To: freebsd-ports-bugs@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 66F30BE263B for ; Tue, 20 Sep 2016 18:31:33 +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 3D950DB6 for ; Tue, 20 Sep 2016 18:31:33 +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 u8KIVWIp008606 for ; Tue, 20 Sep 2016 18:31:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212863] security/vault: update 5.3 to 6.1 Date: Tue, 20 Sep 2016 18:31:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new 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 Only Me X-Bugzilla-Who: dch@skunkwerks.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: swills@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name attachments.created Message-ID: 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-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 18:31:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212863 Bug ID: 212863 Summary: security/vault: update 5.3 to 6.1 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: swills@FreeBSD.org Reporter: dch@skunkwerks.at Assignee: swills@FreeBSD.org Flags: maintainer-feedback?(swills@FreeBSD.org) Created attachment 175012 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175012&action= =3Dedit v1 patch # update & fixes - use upstream mlock (verified to work) - add vault tag in process name to daemon(8) - update version tag from portstree Makefile In the end I left the daemon restart & pid management flags alone, until I = can replicate the issue I had in production -- changing it seem to make matters worse and the vault is anyway sealed until admins re-open it. # qa - poudriere OK (11.0-RC3 amd64, 10.3R amd64 & i386, 9.3R amd64 & i386) - portlint OK - confirmed mlock works when using daemon & dropped privileges: ``` # limits -C daemon su -m vault -c 'sh -c "/usr/local/bin/vault server -config=3D/usr/local/etc/vault.hcl | tee -a /var/log/vault/console.log"' =3D=3D> Vault server configuration: Backend: s3 Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "", t= ls: "enabled") Log Level: info Mlock: supported: true, enabled: true Version: Vault v0.6.1 =3D=3D> Vault server started! Log data will stream in below: ``` incidentally if there is a logrotation friendly way to grab console data instead of tee(1) please let me know, the actual steps above did work, just= no response from SIGHUP et al. --=20 You are receiving this mail because: You are the assignee for the bug.=