Re: Spam on PEAR site
| From: | Nick Sdot | Date: | Thu, 18 Jun 2026 11:17:32 +0000 |
| Subject: | Re: Spam on PEAR site | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131367@lists.php.net to get a copy of this message | ||
On 18.06.26 17:38, Derick Rethans wrote:
On 18 June 2026 09:26:01 BST, Davey Shafik <me@daveyshafik.com> wrote:I sent Ken, who is listed on the PEAR website and just lately voted on a RFC, an email to ask if he has access. My previous attempt was answering to Pierre (who has access), which was unfortunately unanswered. Let's see if Ken is able to help here.It doesn't sit behind a CDN. And I have no access to the server. I can drop the whole hostname from DNS. cheers DerickOn Jun 18, 2026, at 01:08, Derick Rethans <derick@php.net> wrote: On 18 June 2026 07:13:13 BST, Nick Sdot <php@nicksdot.dev> wrote:As a quick and dirty fix can we just deny any requests to the relevant endpoints and spam proposals at the CDN?Perhaps it would make sense to disable editing old and adding new proposals, and remove the spam.You'll have to talk to the pear team for that, as we don't have access.
I can drop the whole hostname from DNS.Given that no one from PEAR group participated in the RFC discussion, and if Ken cannot help, this perhaps is an option. I think is a very bad look to have the spammed, unmaintained PEAR website on an official subdomain If I am reading your RFC comments correctly you are for removing the PEAR website from php.net altogether anyway? What was your conclusion to whether or not the RFC is required? Cheers Nick