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:52:14 +0200
- From: Christian Horn <chorn@example.com>
- Subject: Re: [tlug] Dealing with software with wide attack surface
- References: <YSoy60UpAmmK5fyo@fluxcoil.net> <YSqPWwgCXPdJ6zaU@cobalt> <80a4eba6b1d950598ad125b53323f5eb@paddon.org>
On Sun, Aug 29, 2021 at 01:17:58PM +0900, Michael Paddon wrote: > [..] > This is good advice. More formally, you should try to implement a "reference > monitor". > > Jaegar (2011) describes the concept as "a system component, called a > reference validation mechanism, will be responsible for enforcing the > system’s access control policy over user process operations. The reference > monitor concept defines the requirements for implementing such a mechanism > in a manner that ensures that malicious users cannot circumvent policy > enforcement." > > There's a good discussion here on why this pattern is helpful. > https://www.mdpi.com/2078-2489/7/2/23/pdf That reminds me much of selinux. While Debian services in general do not come with selinux policies, the kernel is compiled for selinux. Maybe I should try to run Lychee in a container, using the UBI image from Red Hat, which can be freely distributed and should inside also nicely deal with selinux. Chris
- References:
- [tlug] Dealing with software with wide attack surface
- From: Christian Horn
- Re: [tlug] Dealing with software with wide attack surface
- From: Jens John
- Re: [tlug] Dealing with software with wide attack surface
- From: Michael Paddon
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Dealing with software with wide attack surface
- Next by Date: Re: [tlug] Call for presenters for September 11th
- Previous by thread: Re: [tlug] Dealing with software with wide attack surface
- Next by thread: Re: [tlug] Dealing with software with wide attack surface
- Index(es):