Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Dealing with software with wide attack surface
- Date: Sun, 29 Aug 2021 10:26:09 +0200
- From: Christian Horn <chorn@example.com>
- Subject: Re: [tlug] Dealing with software with wide attack surface
- References: <YSoy60UpAmmK5fyo@fluxcoil.net> <29a7d3f2-613c-0ed4-070c-73938886ce29@dcook.org>
On Sat, Aug 28, 2021 at 03:54:47PM +0100, Darren Cook wrote: > > If you are going to automate updates, it is worth considering that the > "attack surface" is no different between 113 modules and a single > module: someone could build a module that hard-codes all the others. > Obviously that module still has all the same flaws. > [..] +1 > > Or I write code which constantly checks if there are > > updates for these php modules. > > That bit, at least, is trivial: run `composer update` in a cronjob. Right.. but I put less trust in the modules being properly main- tained than in the packages of the Linux distro below.. Chris
- References:
- [tlug] Dealing with software with wide attack surface
- From: Christian Horn
- Re: [tlug] Dealing with software with wide attack surface
- From: Darren Cook
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Dealing with software with wide attack surface
- Next by Date: Re: [tlug] Dealing with software with wide attack surface
- Previous by thread: Re: [tlug] Dealing with software with wide attack surface
- Next by thread: [tlug] Dealing with software with wide attack surface
- Index(es):