Repository navigation
Replies: 1 comment
|
Hi @innologi, Here is the current status:
I'm documenting all of this in #2865. Regarding system dependencies such as PHP, Docker base images, etc.:
Regarding security fixes:
Regarding the breaking change introduced in 1.13.5: it reverts changes introduced in the previous releases (1.13.2 and 1.13.4) that turned out to be a security and maintenance nightmare. I made the call to revert them as soon as possible, in a patch version, to stop giving security guarantees that are not true, and not desirable (#2790).
Yes. Today, it wasn't possible: the build pipeline needed a new tag to be fixed anyway, which is why we released v1.13.6.
As explained, the static binaries of the latest release are rebuilt and replaced each night. Git tags never move, and Docker images can be pinned by digest. We currently don't have a better solution, as GitHub releases don't provide a good way to version assets, and static-php-cli doesn't publish v3 tags we could pin yet (#2784). |
Uh oh!
There was an error while loading. Please reload this page.
Hi, let me prefix the subject by saying I've been loving FrankenPHP worker mode performance for a few years now. A big thank you to all the contributors for all the work you've put into the project! I appreciate your support.
I would like to open a discussion on how FrankenPHP security fixes get released, and I'm hoping to elicit a response from developers contributing to the project, without any pressure (this is not posted as an issue or poll). For anyone else who shares similar concerns, I ask you to simply upvote or contribute with anything helpful, but not to muddy the discussion with related subjects.
As the project matured, and especially since the official PHP adoption, we see an increase in organizations who implement FrankenPHP as a building block to their production sites and apps. At this point in time, I would like to ask if you see opportunities or roadblocks to revisit your approach to security fixes:
FrankenPHP security fixes are regularly combined with any number of other changes that seem to be ready at that time, including potentially breaking ones, as was implied in the recent v1.13.5 release notes. Depending on the severity and urgency of deploying those security fixes, project owners face complications in their path towards applying them, as the inclusion of high impact changes increases risks for side effects in such a crucial building block to their sites and applications.
In the face of yet another round of another round of PHP security releases for one or more critical severity issues today, I feel obligated to my clients to open up these questions to the FrankenPHP project maintainers:
Would FrankenPHP maintainers:
Despite the preamble, I am very much aware we cannot discuss this request without touching on several closely related subjects, that may invite both solutions to and distractions from the main questions at hand:
Regardless, a project that supports only the latest version, and/or follows any alternative versioning convention, is not blocked from introducing dedicated security fix releases and simultaneous (or later) additional releases with minor or additional patch version increments.
Note
The project maintainers have shown a willingness to compromise on its supported versions policy, such as by rebuilding and retagging an existing version for a critical security issue like php2shell without updating its release notes, while the new version with those security fixes explicitly announced in its release notes was already underway. This is not a critique: It's good to be flexible, especially with the pressure as high as it was with php2shell.
But it invites additional arguments to the main request in this discussion:
All reactions