Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USE_FILE_CMD: seccomp Bad system call #4219

Closed
mc-butler opened this issue Mar 18, 2021 · 4 comments
Closed

USE_FILE_CMD: seccomp Bad system call #4219

mc-butler opened this issue Mar 18, 2021 · 4 comments
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress res: invalid The ticket is not a bug, or is a support request ver: 4.8.25 Reproducible in version 4.8.25

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/4219
Reporter anton_kg (anton.bugs@….com)

Hi, I'm getting and error message when trying to "enter" into zip archive.
The error is the following:
file -L -z xxx.zip
xxx.zip: Bad system call

The call is here:
https://github.com/MidnightCommander/mc/blob/master/src/filemanager/ext.c#L75
"file -z"

A quick workaround is to add "-S" option:

-S, --no-sandbox

On systems where libseccomp (https://github.com/seccomp/libseccomp) is available, the -S flag
disables sandboxing which is enabled by default. This option is needed for file to execute ex‐
ternal decompressing programs, i.e. when the -z flag is specified and the built-in decompressors
are not available. On systems where sandboxing is not available, this option has no effect.

You might know a better solution

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Mar 18, 2021 at 5:42 UTC (comment 1)

-S is tested and used if available:
https://github.com/MidnightCommander/mc/blob/master/configure.ac#L159

[1ed638d]

Please show your config.log and config.h.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Mar 28, 2021 at 13:01 UTC (comment 2)

ping

@mc-butler
Copy link
Author

Changed by anton_kg (anton.bugs@….com) on Apr 1, 2021 at 1:42 UTC (comment 3)

sorry, I did not receive a notification about your comment. It seems you have fixed it, see ticket #4180 too.

Please close the ticket (this ticketing system is really confusing, looks like a software from 90x).

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Apr 1, 2021 at 5:34 UTC (comment 4)

  • Version changed from master to 4.8.25
  • Status changed from new to closed
  • Resolution set to invalid
  • Milestone Future Releases deleted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress res: invalid The ticket is not a bug, or is a support request ver: 4.8.25 Reproducible in version 4.8.25
Development

No branches or pull requests

1 participant