Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87152
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.171 as permitted sender)
MIME-Version: 1.0
Date: Mon, 13 Jul 2015 19:23:20 +0100
Message-ID: <CAEZfaM7CJZhNzZBSWwSuEwXLzyELHe+JQrU0aQgMn1cqsCLVVQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a114dcba0f6f254051ac5d04d
Subject: Introductions
From: matt.tait@gmail.com (Matt Tait)

--001a114dcba0f6f254051ac5d04d
Content-Type: text/plain; charset=UTF-8

Hi all,

I'm Matt Tait; a security researcher at Google, and I'm quite interested in
looking at and helping to build new security-related features within PHP;
i.e. features that reduce the likelihood that deployments of PHP end up
being hacked.

In the short term, I'm quite interested in looking at ensuring that all of
the compiler and operating-system security features are enabled by default,
and later I hope to be looking at both hardening the PHP core against
various categories of memory-corruption vulnerability. Hopefully this work
will also end up improving the performance and security of various parts of
PHP core.

In the longer-term I'm also interested in building user-visible features
for PHP that would allow developers who want or need to deploy PHP to
sensitive environments to prevent certain categories of error across their
entire codebase (such as SQL injection and so on) that are commonly used by
hackers. This would be particularly useful for many less-technical
companies who are worried about hackers, but unable to ensure that every
component they plug in to their website is coded with security-in-mind.

I look forward to working with you all to make PHP a better product for PHP
developers and website owners!

Cheers,
Matt

--001a114dcba0f6f254051ac5d04d--