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 #1310] Seccomp execve - Operation not permitted launching an app #893

New issue
Closed
opened 2026-05-05 07:04:39 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 07:04:39 -06:00
Owner
Copy link

Originally created by @EdoardoVignati on GitHub (May 25, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1310

hi, when I execute firejail --seccomp.eperm=execve myapp I notice that firejail blocks the app saying execvp: Operation not permitted.
How to execute myapp and block execve syscall after?

Originally created by @EdoardoVignati on GitHub (May 25, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1310 hi, when I execute `firejail --seccomp.eperm=execve myapp` I notice that firejail blocks the app saying `execvp: Operation not permitted`. How to execute myapp and block execve syscall after?
gitea-mirror 2026-05-05 07:04:39 -06:00
  • closed this issue
  • added the
    bug
         label
gitea-mirror commented 2026-05-05 07:04:47 -06:00
Author
Owner
Copy link

@reinerh commented on GitHub (May 25, 2017):

Hm, while trying to reproduce it I noticed that it's not working anymore in 0.9.46, though it's still documented in the manpage.

<!-- gh-comment-id:304054788 --> @reinerh commented on GitHub (May 25, 2017): Hm, while trying to reproduce it I noticed that it's not working anymore in 0.9.46, though it's still documented in the manpage.
gitea-mirror commented 2026-05-05 07:04:50 -06:00
Author
Owner
Copy link

@startx2017 commented on GitHub (May 26, 2017):

manpage problem - use the regular --seccomp command: "firejail --seccomp=execve:eperm myapp"

Fix: c1d43f4123

<!-- gh-comment-id:304314246 --> @startx2017 commented on GitHub (May 26, 2017): manpage problem - use the regular --seccomp command: "firejail --seccomp=execve:eperm myapp" Fix: https://github.com/netblue30/firejail/commit/c1d43f41230cdd0bc929c0050f60024fc98fc37b
gitea-mirror commented 2026-05-05 07:04:53 -06:00
Author
Owner
Copy link

@EdoardoVignati commented on GitHub (May 26, 2017):

firejail --seccomp=execve:eperm myapp causes the same problem...seems that firejail recognizes the execution of myapp in the syscall blacklist specified in the command line, so not launching it...possibile?

<!-- gh-comment-id:304321242 --> @EdoardoVignati commented on GitHub (May 26, 2017): `firejail --seccomp=execve:eperm myapp` causes the same problem...seems that firejail recognizes the execution of myapp in the syscall blacklist specified in the command line, so not launching it...possibile?
gitea-mirror commented 2026-05-05 07:04:56 -06:00
Author
Owner
Copy link

@reinerh commented on GitHub (May 26, 2017):

I can also confirm that the application is not executed if execve is blocked.

<!-- gh-comment-id:304322036 --> @reinerh commented on GitHub (May 26, 2017): I can also confirm that the application is not executed if execve is blocked.
gitea-mirror commented 2026-05-05 07:05:00 -06:00
Author
Owner
Copy link

@netblue30 commented on GitHub (May 27, 2017):

Thanks @startx2017, I changed the code and forgot to modify the manual!

Don't use --seccomp=execve, because after installing the seccomp filter the sandbox will try to start the program using execve. We end up with seccomp killing the sandbox.

<!-- gh-comment-id:304418389 --> @netblue30 commented on GitHub (May 27, 2017): Thanks @startx2017, I changed the code and forgot to modify the manual! Don't use --seccomp=execve, because after installing the seccomp filter the sandbox will try to start the program using execve. We end up with seccomp killing the sandbox.
gitea-mirror commented 2026-05-05 07:05:03 -06:00
Author
Owner
Copy link

@EdoardoVignati commented on GitHub (May 27, 2017):

Any workaround? Is there another way to spawn myapp?

<!-- gh-comment-id:304464535 --> @EdoardoVignati commented on GitHub (May 27, 2017): Any workaround? Is there another way to spawn myapp?
gitea-mirror commented 2026-05-05 07:05:05 -06:00
Author
Owner
Copy link

@netblue30 commented on GitHub (May 30, 2017):

I don't think there is any workaround.

<!-- gh-comment-id:304855008 --> @netblue30 commented on GitHub (May 30, 2017): I don't think there is any workaround.
gitea-mirror commented 2026-05-05 07:05:07 -06:00
Author
Owner
Copy link

@EdoardoVignati commented on GitHub (Jun 1, 2017):

Found a solution for seccomp here if it can be useful

<!-- gh-comment-id:305633449 --> @EdoardoVignati commented on GitHub (Jun 1, 2017): Found a solution for seccomp [here](https://stackoverflow.com/questions/40107782/how-to-seccomp-a-subprocess) if it can be useful
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#893
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?