Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106362 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 25940 invoked from network); 31 Jul 2019 06:56:07 -0000 Received: from unknown (HELO mail-qk1-f174.google.com) (209.85.222.174) by pb1.pair.com with SMTP; 31 Jul 2019 06:56:07 -0000 Received: by mail-qk1-f174.google.com with SMTP id r6so48282664qkc.0 for ; Tue, 30 Jul 2019 21:21:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=X1fktLxoZTdc0fQcQASoYzanyYS1zpLUt3JNq8myNfI=; b=BTF9dtVO2/bb3rLO5HRUDqOiypEnQPhVfhwS/QqKVjOAkbDTsOhOsk5ukNCEyDjnt9 3Wq0/Vx+JJ+Eo6iYcHcVBXBpEoK6vNEvjrGMGwi6pxQ1bi4UvnDd9O1SaZ7f3EDNgfLc kGWhAlzLVPpIswhv0EO6BqqOUB7PSdCJFpklUj1jotgFBPM/pXuwb0Mm8A0u/+da2wmI 9vzJ/Mc54iTFhaQraNUIs2cMw8mBFvn4WAm8nqtdeSyS0xvjWPKlTOjjFV1F6oqbFoxq vYPDp63Yss6pAnl78DXaSU3iTE5SNjxLMpXkajTGg1upE5/d+67PXIVHXR+iSElmKmmi 1MCQ== X-Gm-Message-State: APjAAAXNoFrtiHjCogOkKenWApVV9eXRrPfVXET1mAuLzxbSpeWCKNAf 86SiY5WDqU5y7mTqdDNIsirPZBlJ71yiZFSEcLo= X-Google-Smtp-Source: APXvYqz0TmbjAtCN+PKcnsBZUuchqSS11CE014ahbZC6SBWZPdkMmxJOm0xK79eX97iSnnWyqRBW/NukNY7S3mhE3rk= X-Received: by 2002:a05:620a:16c6:: with SMTP id a6mr43094035qkn.413.1564546870451; Tue, 30 Jul 2019 21:21:10 -0700 (PDT) MIME-Version: 1.0 References: <35af7db3-5cba-fe59-1d04-960eacb5aba7@gmail.com> <0f60226d2d6aaf9fc044644a16c0ad7390ed3752.camel@schlueters.de> In-Reply-To: <0f60226d2d6aaf9fc044644a16c0ad7390ed3752.camel@schlueters.de> Reply-To: bishop@php.net Date: Wed, 31 Jul 2019 00:20:45 -0400 Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= , Stanislav Malyshev Cc: PHP Internals Content-Type: multipart/alternative; boundary="00000000000072a367058ef274ba" Subject: Re: [PHP-DEV] Merging fuzzing SAPI into core From: bishop@php.net (Bishop Bettini) --00000000000072a367058ef274ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jul 30, 2019 at 6:15 PM Johannes Schl=C3=BCter wrote: > On Tue, 2019-07-30 at 13:28 -0400, Bishop Bettini wrote: > > On the other, I've found it refreshing working in a > > slender repo that doesn't have all the history and process rules. > > This is good for external (non-core and non-extension) collaborators, > > particularly allowing write access to those who wouldn't want or need > > write access to engine code. > > > I am also not sure having this independent makes it simpler for > outsiders to contribute. You maybe ease the submission process, but > setting it up becomes harder as you need to clone to repos, put it in > the right place, make sure you are in compatible branches (on next PHP > 7 like API change this might become relevant, maybe even sooner as it > goes into different extension's APIs where we observe BC a bit less) > > I think merging it into PHP makes the most sense, also for signaling to > the outside that we care about security by having fuzzing routines as > core part of the thing. > Fair points, Johannes and Stas. I've no objection to moving the SAPI into php/php-src. --00000000000072a367058ef274ba--