#selinux
애플리케이션별로, 호스트 사용자 매핑을 통해 허용 여부를 결정해야 하지. rhosts혹은, pg_hba 같은것을 동원.

4. 망내 호스트간 포트 및 접근 사용자 제어에, 접근 가능한 파일까지 제어 : 이제 비이성적인 수준에 도달. ㅋ 파일 접근 제어도, linux에서 당연히, rwxrwxrwx 수준에서부터 selinux급 파일접근제어가 가능하게 되긴 하지. 이 수준을 방화벽 관리하던 사용자가 다 관리하라고 하면, 과연, 파일 수준까지 다 트래킹해서 차단 혹은 허용 가능하겠냐? 라는..
October 28, 2026 at 12:15 PM
🚨 EUVD-2026-111881
📊 n/a
🏢 Linux

📝 In the Linux kernel, the following vulnerability has been resolved:

selinux: fix BPF token permission checks

Avoid multiple lookups of the bpffs creator SI...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-111881

#cybersecurity #infosec #cve #euvd
October 28, 2026 at 11:10 AM
ホームサーバーでMisskeyを入れたはいいものの、なぜかメモアプリとして活用するフェリーさん…SELinuxめんどくさかった…ひと月前にFedora IoT選んだ自分を問い詰めたい。
Fedoraなのでほぼ毎日更新が入るけど、こいつはImmutableなので毎回再起動。ガバガバ稼働率の牧歌的なホームサーバーには結構向いてるんだよなあ…
October 27, 2026 at 2:28 PM
The current deluge of exploits found with the assistance of LLMs should in theory best be mitigated by diligent application of SELinux policies.

Accept that attackers _will_ find an entrypoint. Make sure everything after that becomes extremely difficult and requires per-target probing […]
Original post on swecyb.com
swecyb.com
October 26, 2026 at 10:12 PM
Got the AMD Radeon iGPU passed through to a Windows 11 VM. With SELinux set to enforcing mode and secure boot enabled on host.

DarkSouls (optional) boss fight energy.
October 25, 2026 at 8:20 PM
A solução se chama defesa em profundidade: camadas de proteção, assumindo que a primeira vai falhar.

Container isolado, AppArmor/SELinux, rede segmentada e detecção. O atacante precisa passar por todas, sem ser notado.
October 25, 2026 at 3:00 PM
"Linux is so much more secure than [insert OS]"

>Disables secure boot
>Doesn't use SELinux
>Doesn't use service isolation
>Doesn't use flatpak
Troll Face Phonk Mango Phonk
Alt: Troll Face Kendrick Mustard 67 Kid King Von Mango Phonk Edit
static.klipy.com
October 25, 2026 at 1:07 PM
i wonder if most of this tailscale vulnerability could've been mitigated by user using 1. systemd service isolation / doc.. i mean podman 2. SELinux
October 25, 2026 at 12:43 PM
반대로 NSA(그 미국 안기부 맞음)가 리눅스 커뮤니티에 무상으로 기증한 SELinux 같은 사례도 있습니다.
October 24, 2026 at 1:46 PM
ともあれ、php2shell問題で最初に思ったのは、AI時代の脆弱性管理や防御のあり方は変わるのかもしれない、守る側もAIのフルの活用が必要なのかもしれないということだった...

が、少し考えて、いや違うな?と整理できてきた。

結局は、侵入や攻撃は起こる、という前提でシステムを設計すべきだという話に落ち着いた。

以下はやや単語が専門的なので、わからない人はAIにでも聞くと多分説明してくれる。
必要なのは結局はRCEされた時の影響を最小化すること。
(1) root権限で動かさない。最小権限で
(2) SELinuxなどで想定されないファイルアクセスや通信を拒否する
(3) コンテナ化する
October 24, 2026 at 5:38 AM
SELinuxみたいなことWindowsでもしたい
October 24, 2026 at 3:11 AM
🚨 EUVD-2026-108847
📊 n/a
🏢 Linux

📝 In the Linux kernel, the following vulnerability has been resolved:

selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts

When an NFSv4...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-108847

#cybersecurity #infosec #cve #euvd
October 23, 2026 at 1:04 PM
Rootless Dockerと学ぶSELinux【初心者向け】
SELinuxのTypeは1対1ではなく、AttributeとTypeが多対多で結ばれています。Attributeへの許可で、多数のプロセスとファイルをまとめて制御できます。

許可を個々の相手ではなく、所属する集合に対して書けるので、新しい相手を一つずつ登録しなくても、集合に入れば同じ許可が届きます。
Rootless Dockerと学ぶSELinux【初心者向け】
zenn.dev
October 23, 2026 at 1:47 AM
今日のZennトレンド

Rootless Dockerと学ぶSELinux【初心者向け】
Rocky LinuxでRootless Dockerを運用し、SELinuxの基礎を学習した記録です。
アクセス制御の鍵となるTypeに着目し、ls -alZコマンドでディレクトリのTypeを確認する方法や、sesearchコマンドを用いて特定のTypeにアクセス権を持つプロセスを調査する手順を解説しています。
Rootless Dockerと学ぶSELinux【初心者向け】
!この記事の作成にあたって、図の生成、調査、校正に生成AIを使用していますが、本文は人の手で書かれたものです。 環境Rocky Linux 10.2 あらすじ私の自宅サーバーでは、/var/composeにDocker Composeのファイル一式を格納し、composeユーザーでRootless Dockerを動かしています。Rocky Linux(というかRHEL)ではデフォルトでrootで動
zenn.dev
October 23, 2026 at 12:04 AM
Rootless Dockerと学ぶSELinux【初心者向け】
https://zenn.dev/nexryai/articles/afb828d7dda6b7
Rootless Dockerと学ぶSELinux【初心者向け】
zenn.dev
October 22, 2026 at 11:34 PM
come on it's pwn week can someone finally publish a selinux vuln or smth so that i can finally root those fucking toughbook android phones
October 22, 2026 at 2:42 PM
📢 New #updates · 22 Oct #6.2

· ProjectSend v2.7.1 — Security fixes for PHP, email encryption, SELinux, MariaDB/MySQL, and branding

Browse everything at https://selfhost.directory?utm_source=bluesky&utm_medium=social

#linux #webhooks #opensource #accessibility
October 22, 2026 at 5:55 AM
Most secure & private desktop OS for daily usage
KeenFox44: > linux generally is not recommended as its less secure than windows/macOS Linux can be very unsafe, sometimes even by default, but can also be the most secure OS. It all depends on your configuration. After all Linux is a kernel and an overall term for a huge ecosystem. If you have widely covered Mandatory Access Control like SELinux or TOMOYO, firewall like opensnitch, sandbox like bubblejail, your system is already much more secure than normal Windows and MacOS. These improves security the most with least effort. The next steps of hardening can include LUKS, use bootloader like limine and TPM verified boot chain, switch to linux-hardened or custom kernel, use Wayland and modern software, Desktop Environment with small attack surface, some auditd logging, encrypted backup, sysctl and kernel cmdline hardening, module pinning, allowlist of everything, etc. There are much more, I cannot list all of them here. If you setup your Linux like this in a consistent way (most likely require some professional knowledge in security) you can get a Linux **suitable for daily use** that is much more secure than average Windows and MacOS. (of course a system designed for special use cases can still be more secure than this, e.g. QubeOS and Android) Most modern Linux software can work on such a system, including Steam. If you want to customize like this, I recommend starting from Fedora (Fedora Atomic maybe?) or Arch (more convenient, easier to customize, smaller codebase, but requires extra hardening in supply chain).
discuss.privacyguides.net
October 22, 2026 at 1:19 AM
Use SELinux / AppArmor,
set apparmor_hat,
set fatal_error_backtraces=0 and
hide the presence of PHP with expose_php=0. [2/2]
October 21, 2026 at 8:32 PM
Most secure & private desktop OS for daily usage
I’ve been pretty impressed with the permissions management on the latest versions of MacOS. You can manage aspects like which programs may screen share, which programs can get full or partial access disk access (meaning no full disk access for terminal if you don’t use it), etc in the main settings menu. If something needs access, you get a popup and can enable it with fingerprint or password. This is possible in Linux with flatpak and SELinux, but it’s a helluva a lot more work to do this for every single program. There are also some vulnerabilties like username space in linux that SecureBlue tries to minimize, but since linux isn’t designed to be used like that it can create a lot of difficulties. MacOS is more of a cohesive whole where you can have these features without impacting usability or requiring a lot of time. This, of course, says nothing about privacy, closed versus open source, or the implications of supporting apple financially. With no apple ID, more private than windows or chromeos for sure though. I want to push people toward linux, but I don’t feel comfortable doing that with everyone given the current state of Macos and linux. If OP is successful with fedora and has no threat of targeted attacks, I don’t think they need to panic, buy a new PC, and switch to macos though.
discuss.privacyguides.net
October 21, 2026 at 7:20 PM
I did the following cutting edge things in 2003:
- SeLinux and Grsecurity for stronger access controls
- Having users run their own http servers
- Providing reverse proxy to users servers with SSL termination
- Began investigating virtual machines

This solved *why* users would chmod 777
October 21, 2026 at 4:50 PM
i want to try using nixos on my server (laptop at home). what kind of setup would you all recommend nowadays
October 21, 2026 at 3:37 PM
Linux Kernel Daily: Security Hardening, Filesystem Fixes, and New Hardware Support

Today's mainline kernel changes include SELinux policy hardening, XFS and bt…

#ConfidentialComputing #Crypto #Filesystems #HardwareSupport #Performance #Security

https://kerneldispatch.com/posts/mainline-2026-10-21
October 21, 2026 at 2:27 PM
And yes, selinux blocks still generate Incidents. You still have to take action and investigate because it is easier to prove what selinux blocked than what might have slipped past it.
October 21, 2026 at 12:40 PM