Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95203 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91007 invoked from network); 15 Aug 2016 17:50:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Aug 2016 17:50:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.195 as permitted sender) X-PHP-List-Original-Sender: kalle.php@gmail.com X-Host-Fingerprint: 209.85.223.195 mail-io0-f195.google.com Received: from [209.85.223.195] ([209.85.223.195:33317] helo=mail-io0-f195.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/D8-36656-00102B75 for ; Mon, 15 Aug 2016 13:50:57 -0400 Received: by mail-io0-f195.google.com with SMTP id y195so6242850iod.0 for ; Mon, 15 Aug 2016 10:50:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jaVgLb8QduEtxoQmNGhIRTum2fIRlktTXObjwqxTd6Y=; b=NS6Odk95H+iKbsKWNEyDtn0hMKdXLYyfN54EARULR9JXAuFmljMjN4YQuZ0x3SWAfu dDjQkvVDg6V4XxDvIGuaZG72MgT+YZcJw62Z6BX30Uko38qPp38Koi4gj+VbyTIQ02ri yyd9u7/CwDjdku8yy48fJl8g6MaB6jCXCN/pYvOHC/t6B0QQDb9xg4pLOBStylDYW0WH w2U7MT0FnOMGkws+7rG6b4prr+truBQds6YGB4DuN9m9OCLS6bCe6W3MWJ5QGIH1P68y LW4Xcdz7yAs+lOUbHT43glkIz2bA1Mu8WqJRW66QxMII458b7FJbcYxehLnFN5Dz1VVJ 1fBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jaVgLb8QduEtxoQmNGhIRTum2fIRlktTXObjwqxTd6Y=; b=Zm40w+HvyLXoUU5sAs4AbWGjLTKmMnvre/Tb45dvJkqFS9f1IJO3g9y+DghUdmnRrn StrDusBjwMQXvhAUjWFp7Ub3aNTRPg8mLChExKWz7dww7cMaTlFsRsAf8pPf9xnmqN23 utVf4GezQrmnRogkUSzLBxHBUtHm8ng74YMdAtOSZFA1FlTgI1hwT04qmRCamz25UZ4a hdiPlVP1APE37mlj8ZjWx8cvDIlQaDuT5WHXV4Pa4ctdqLzo1yuFtumM3BsqdFKzF9mg ydqmuvYekmvbYtfjoltvTj+3UxuEiGhDfxu+sncP0cbm6IiS4FVbr4tPpPRtAmH208LM /LYA== X-Gm-Message-State: AEkoousDkvP7KvtdEuX78OnOyX7CpOjpgY0+PFFi4+L3Fe6cf9TggGZz+u1PJFiBQEJ+ZfyiM9Evcf+GFsvbFw== X-Received: by 10.107.3.35 with SMTP id 35mr34946822iod.40.1471283454502; Mon, 15 Aug 2016 10:50:54 -0700 (PDT) MIME-Version: 1.0 Sender: kalle.php@gmail.com Received: by 10.107.48.77 with HTTP; Mon, 15 Aug 2016 10:50:54 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Aug 2016 19:50:54 +0200 X-Google-Sender-Auth: xo9yqCnrb6ij2Vs50Qa1ppuGrZY Message-ID: To: Stanislav Malyshev Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] rethinking security issues in bugs db From: kalle@php.net (Kalle Sommer Nielsen) Hi Stas 2016-08-15 19:12 GMT+02:00 Stanislav Malyshev : > Hi! > > I think the way security/private issues are implemented now in bugs DB > is wrong. It allows only access to a handful of people, and many package > maintainers and people that know the code in question are excluded. This > makes promptly handling bugs very hard. I propose one of: > > 1. Adding a lot more people to trusted list > 2. Implementing functionality allowing to add people to private bug on > per-bug basis. I don't see why we cannot have both? Have active Core Developers added to the trusted-devs.inc and an option to add in additional developers that may not be on the list that could be of relation to the bug. -- regards, Kalle Sommer Nielsen kalle@php.net