github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #6915] swww: Error: "/run/user/1000/wayland-1-swww-daemon..sock" is an invalid filename #3418

New issue
Closed
opened 2026-05-05 09:59:25 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 09:59:25 -06:00
Owner
Copy link

Originally created by @amano-kenji on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6915

Description

Whitelisting /run/user/1000/wayland-1-swww-daemon..sock is impossible.

Steps to Reproduce

Execute

firejail --include=/etc/firejail/whitelist-runuser-common.inc --whitelist=/run/user/1000/wayland-1-swww-daemon..sock --noprofile bash

Expected behavior

No error

Actual behavior

$ firejail --include=/etc/firejail/whitelist-runuser-common.inc --whitelist=/run/user/1000/wayland-1-swww-daemon..sock --noprofile bash
Reading profile /etc/firejail/whitelist-runuser-common.inc
Error: "/run/user/1000/wayland-1-swww-daemon..sock" is an invalid filename

Environment

  • Name/version/arch of the Linux kernel (uname -srm): Linux 6.6.101-gentoo x86_64
  • Name/version of the Linux distribution (e.g. "Ubuntu 20.04" or "Arch Linux"): Gentoo Linux
  • Version of Firejail (firejail --version):
firejail version 0.9.74

Compile time support:
        - always force nonewprivs support is disabled
        - AppArmor support is disabled
        - AppImage support is enabled
        - chroot support is enabled
        - D-BUS proxy support is enabled
        - file transfer support is enabled
        - IDS support is disabled
        - Landlock support is enabled
        - networking support is enabled
        - output logging is enabled
        - overlayfs support is disabled
        - private-home support is enabled
        - private-lib support is disabled
        - private-cache and tmpfs as user enabled
        - sandbox check is enabled
        - SELinux support is disabled
        - user namespace support is enabled
        - X11 sandboxing support is enabled
Originally created by @amano-kenji on GitHub (Sep 29, 2025). Original GitHub issue: https://github.com/netblue30/firejail/issues/6915 ### Description Whitelisting `/run/user/1000/wayland-1-swww-daemon..sock` is impossible. ### Steps to Reproduce Execute ``` firejail --include=/etc/firejail/whitelist-runuser-common.inc --whitelist=/run/user/1000/wayland-1-swww-daemon..sock --noprofile bash ``` ### Expected behavior No error ### Actual behavior ``` $ firejail --include=/etc/firejail/whitelist-runuser-common.inc --whitelist=/run/user/1000/wayland-1-swww-daemon..sock --noprofile bash Reading profile /etc/firejail/whitelist-runuser-common.inc Error: "/run/user/1000/wayland-1-swww-daemon..sock" is an invalid filename ``` ### Environment - Name/version/arch of the Linux kernel (`uname -srm`): Linux 6.6.101-gentoo x86_64 - Name/version of the Linux distribution (e.g. "Ubuntu 20.04" or "Arch Linux"): Gentoo Linux - Version of Firejail (`firejail --version`): ``` firejail version 0.9.74 Compile time support: - always force nonewprivs support is disabled - AppArmor support is disabled - AppImage support is enabled - chroot support is enabled - D-BUS proxy support is enabled - file transfer support is enabled - IDS support is disabled - Landlock support is enabled - networking support is enabled - output logging is enabled - overlayfs support is disabled - private-home support is enabled - private-lib support is disabled - private-cache and tmpfs as user enabled - sandbox check is enabled - SELinux support is disabled - user namespace support is enabled - X11 sandboxing support is enabled ```
gitea-mirror 2026-05-05 09:59:25 -06:00
gitea-mirror commented 2026-05-05 09:59:28 -06:00
Author
Owner
Copy link

@JohnyTheCarrot commented on GitHub (Nov 5, 2025):

Same here.

<!-- gh-comment-id:3492659330 --> @JohnyTheCarrot commented on GitHub (Nov 5, 2025): Same here.
gitea-mirror commented 2026-05-05 09:59:28 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Nov 7, 2025):

firejail version 0.9.74

Note that we do not maintain that version of firejail:

Versions other than the latest usually have outdated profiles and may contain
bugs and security vulnerabilities that were fixed in later versions.

See also:

Whitelisting /run/user/1000/wayland-1-swww-daemon..sock is impossible.

$ firejail --include=/etc/firejail/whitelist-runuser-common.inc --whitelist=/run/user/1000/wayland-1-swww-daemon..sock --noprofile bash
Reading profile /etc/firejail/whitelist-runuser-common.inc
Error: "/run/user/1000/wayland-1-swww-daemon..sock" is an invalid filename

That is a rather unusual filename.

What program creates this file?

As can be seen in #6958, the checks are meant to catch attempts at relative
directory traversal (see CWE-23).

I think it would make more sense to change the relevant program to remove the
extra dot than to increase the risk of a malicious traversal happening.

<!-- gh-comment-id:3502467664 --> @kmk3 commented on GitHub (Nov 7, 2025): > firejail version 0.9.74 Note that we do not maintain that version of firejail: * <https://github.com/netblue30/firejail/blob/master/SECURITY.md> Versions other than the latest usually have outdated profiles and may contain bugs and security vulnerabilities that were fixed in later versions. See also: * <https://github.com/netblue30/firejail#installing> > Whitelisting `/run/user/1000/wayland-1-swww-daemon..sock` is impossible. > ``` > $ firejail --include=/etc/firejail/whitelist-runuser-common.inc --whitelist=/run/user/1000/wayland-1-swww-daemon..sock --noprofile bash > Reading profile /etc/firejail/whitelist-runuser-common.inc > Error: "/run/user/1000/wayland-1-swww-daemon..sock" is an invalid filename > ``` That is a rather unusual filename. What program creates this file? As can be seen in #6958, the checks are meant to catch attempts at relative directory traversal (see CWE-23). I think it would make more sense to change the relevant program to remove the extra dot than to increase the risk of a malicious traversal happening.
gitea-mirror commented 2026-05-05 09:59:29 -06:00
Author
Owner
Copy link

@amano-kenji commented on GitHub (Nov 7, 2025):

It is created by swww which is a wayland wallpaper engine. I don't control swww.

<!-- gh-comment-id:3502946269 --> @amano-kenji commented on GitHub (Nov 7, 2025): It is created by `swww` which is a wayland wallpaper engine. I don't control swww.
gitea-mirror commented 2026-05-05 09:59:29 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Nov 7, 2025):

It is created by swww which is a wayland wallpaper engine. I don't control
swww.

Presumably you can report bugs/suggestions and send patches to it, just like in
this thread.

Apparently swww has been renamed to awww and moved to Codeberg, so the
above would apply to its successor:

<!-- gh-comment-id:3503144174 --> @kmk3 commented on GitHub (Nov 7, 2025): > It is created by `swww` which is a wayland wallpaper engine. I don't control > swww. Presumably you can report bugs/suggestions and send patches to it, just like in this thread. Apparently `swww` has been renamed to `awww` and moved to Codeberg, so the above would apply to its successor: * <https://github.com/LGFae/swww> * <https://codeberg.org/LGFae/awww>
gitea-mirror commented 2026-05-05 09:59:30 -06:00
Author
Owner
Copy link

@amano-kenji commented on GitHub (Nov 8, 2025):

I created an issue on https://codeberg.org/LGFae/awww/issues/508

But, https://github.com/netblue30/firejail/pull/6958 seems good enough.

<!-- gh-comment-id:3506437146 --> @amano-kenji commented on GitHub (Nov 8, 2025): I created an issue on https://codeberg.org/LGFae/awww/issues/508 But, https://github.com/netblue30/firejail/pull/6958 seems good enough.
gitea-mirror commented 2026-05-05 09:59:30 -06:00
Author
Owner
Copy link

@kmk3 commented on GitHub (Nov 11, 2025):

I created an issue on https://codeberg.org/LGFae/awww/issues/508

Nice, thanks.

Closing, as it looks like the issue will be fixed directly upstream.

Edit: For future reference, see also:

<!-- gh-comment-id:3514962023 --> @kmk3 commented on GitHub (Nov 11, 2025): > I created an issue on https://codeberg.org/LGFae/awww/issues/508 Nice, thanks. Closing, as it looks like the issue will be fixed directly upstream. Edit: For future reference, see also: * https://github.com/netblue30/firejail/pull/6958#pullrequestreview-3446203624
gitea-mirror commented 2026-05-05 09:59:30 -06:00
Author
Owner
Copy link

@amano-kenji commented on GitHub (Nov 11, 2025):

I don't know whether upstream will recognize it as an issue. It's not confirmed, yet.

<!-- gh-comment-id:3517272701 --> @amano-kenji commented on GitHub (Nov 11, 2025): I don't know whether upstream will recognize it as an issue. It's not confirmed, yet.
gitea-mirror commented 2026-05-05 09:59:31 -06:00
Author
Owner
Copy link

@amano-kenji commented on GitHub (Nov 12, 2025):

The upstream said it's probably going to remove two consecutive dots in the socket file.

<!-- gh-comment-id:3521253701 --> @amano-kenji commented on GitHub (Nov 12, 2025): The upstream said it's probably going to remove two consecutive dots in the socket file.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear labels   
LTS merge

   
LTS merge

   
bug

   
bug

   
converted-to-discussion

   
doc-todo

   
documentation

   
duplicate

   
enhancement

   
file-transfer

   
firecfg

   
firejail-in-firejail

   
firetools

   
graphics

   
help wanted

   
information_old

   
installation

   
invalid

   
modif

   
moved

   
needinfo

   
networking

   
notabug

   
notourbug

   
old-version

   
overlayfs

   
packaging

   
profile-request

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#3418
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?