On 6/24/23 21:39, Nikita Popov wrote:
> On Fri, Dec 30, 2022, at 22:39, Christoph M. Becker wrote:
>> On 30.12.2022 at 22:12, Nikita Popov wrote:
>>
>>> On Thu, Nov 10, 2022, at 14:29, Christoph M. Becker wrote:
>>>
On 09.11.2022 at 23:27, Nikita Popov wrote:
> It looks like GitHub
On Sat, Jun 24, 2023, at 21:39, Nikita Popov wrote:
> On Fri, Dec 30, 2022, at 22:39, Christoph M. Becker wrote:
> > On 30.12.2022 at 22:12, Nikita Popov wrote:
> >
> > > On Thu, Nov 10, 2022, at 14:29, Christoph M. Becker wrote:
> > >
> > >> On 09.11.2022 at 23:27, Nikita Popov wrote:
> > >>
> >
On Fri, Dec 30, 2022, at 22:39, Christoph M. Becker wrote:
> On 30.12.2022 at 22:12, Nikita Popov wrote:
>
> > On Thu, Nov 10, 2022, at 14:29, Christoph M. Becker wrote:
> >
> >> On 09.11.2022 at 23:27, Nikita Popov wrote:
> >>
> >>> It looks like GitHub has just added support for private
Hi!
I had enabled that some weeks ago, since there has been a spam attack on
bugsnet, so we could test the new feature. I probably should have
written to list right away, or at least have kept an eye on it, but I've
assumed to be notified about reported issues.
I'll have a closer look at the
On 30.12.2022 at 22:12, Nikita Popov wrote:
> On Thu, Nov 10, 2022, at 14:29, Christoph M. Becker wrote:
>
>> On 09.11.2022 at 23:27, Nikita Popov wrote:
>>
>>> It looks like GitHub has just added support for private security reports:
>>>
On Thu, Nov 10, 2022, at 14:29, Christoph M. Becker wrote:
> On 09.11.2022 at 23:27, Nikita Popov wrote:
>
> > It looks like GitHub has just added support for private security reports:
> > https://github.blog/changelog/2022-11-09-privately-report-vulnerabilities-to-repository-maintainers/
> >
> >
On 09.11.2022 at 23:27, Nikita Popov wrote:
> It looks like GitHub has just added support for private security reports:
> https://github.blog/changelog/2022-11-09-privately-report-vulnerabilities-to-repository-maintainers/
>
> I haven't looked into the details, but it probably makes sense to
On Fri, Nov 19, 2021 at 9:44 PM Stanislav Malyshev
wrote:
> Hi!
>
> > With Laminas, we use an email alias to allow researchers to report to
> us.
> > We then post the full report as a security issue on GitHub - it's a
> feature
> > they rolled out late 2019/early 2020 that restricts
Hi!
> With Laminas, we use an email alias to allow researchers to report to us.
> We then post the full report as a security issue on GitHub - it's a
feature
> they rolled out late 2019/early 2020 that restricts visibility to
> maintainers initially, but allows inviting others to collaborate
On 18.11.2021 at 15:19, Nikita Popov wrote:
> On Thu, Nov 18, 2021 at 2:53 PM Matthew Weier O'Phinney <
> mweierophin...@gmail.com> wrote:
>
>> With Laminas, we use an email alias to allow researchers to report to us.
>> We then post the full report as a security issue on GitHub - it's a feature
On Thu, Nov 18, 2021 at 2:53 PM Matthew Weier O'Phinney <
mweierophin...@gmail.com> wrote:
>
>
> On Thu, Nov 18, 2021, 7:32 AM Nikita Popov wrote:
>
>> On Thu, Nov 18, 2021 at 2:07 PM Patrick ALLAERT
>> wrote:
>>
>> > Le mer. 17 nov. 2021 à 13:30, Christoph M. Becker a
>> > écrit :
>> > >
On 18.11.2021 at 14:53, Matthew Weier O'Phinney wrote:
> With Laminas, we use an email alias to allow researchers to report to us.
> We then post the full report as a security issue on GitHub - it's a feature
> they rolled out late 2019/early 2020 that restricts visibility to
> maintainers
On Thu, Nov 18, 2021, 7:32 AM Nikita Popov wrote:
> On Thu, Nov 18, 2021 at 2:07 PM Patrick ALLAERT
> wrote:
>
> > Le mer. 17 nov. 2021 à 13:30, Christoph M. Becker a
> > écrit :
> > > Right. An alternative might be to let users report security issues to
> > > the security mailing list,
On Thu, Nov 18, 2021 at 2:07 PM Patrick ALLAERT
wrote:
> Le mer. 17 nov. 2021 à 13:30, Christoph M. Becker a
> écrit :
> > Right. An alternative might be to let users report security issues to
> > the security mailing list, where, if the issue turns out not to be a
> > security issue, the
Le mer. 17 nov. 2021 à 13:30, Christoph M. Becker a écrit :
> Right. An alternative might be to let users report security issues to
> the security mailing list, where, if the issue turns out not to be a
> security issue, the reporter could still be asked to submit a GH issue
> about the bug. In
On 17.11.2021 at 13:01, Nikita Popov wrote:
> On Mon, Nov 15, 2021 at 9:18 PM Björn Larsson
> wrote:
>
>> Den 2021-11-02 kl. 15:19, skrev Nikita Popov:
>>> Hi internals,
>>>
>>> The migration from bugs.php.net to GitHub issues has already been
>> discussed
>>> in
On Mon, Nov 15, 2021 at 9:18 PM Björn Larsson
wrote:
> Den 2021-11-02 kl. 15:19, skrev Nikita Popov:
> > Hi internals,
> >
> > The migration from bugs.php.net to GitHub issues has already been
> discussed
> > in https://externals.io/message/114300 and has already happened for
> > documentation
Den 2021-11-02 kl. 15:19, skrev Nikita Popov:
Hi internals,
The migration from bugs.php.net to GitHub issues has already been discussed
in https://externals.io/message/114300 and has already happened for
documentation issues.
I'd like to formally propose to use GitHub for PHP implementation
On Tue, Nov 2, 2021 at 3:19 PM Nikita Popov wrote:
> Hi internals,
>
> The migration from bugs.php.net to GitHub issues has already been
> discussed in https://externals.io/message/114300 and has already happened
> for documentation issues.
>
> I'd like to formally propose to use GitHub for PHP
19 matches
Mail list logo
