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

skype: paxmark to fix execution on PaX-enabled kernels #21694

Merged
merged 1 commit into from Jan 7, 2017

Conversation

dtzWill
Copy link
Member

@dtzWill dtzWill commented Jan 5, 2017

Motivation for this change
Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

Interestingly, my first attempt had 'paxmark' occurring after patchelf touched the binary but that
resulted in an error complaining that the file was not a valid executable:

file /nix/store/9ambl5f70zjmv8q3nckf48j1ii8dl7pl-skype-4.3.0.37/libexec/skype/skype is not a valid ELF executable (invalid SHT_ entry:1)

Is this a known problem? Anyway running paxmark first seems to work properly.

@mention-bot
Copy link

@dtzWill, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @wkennington and @MarcWeber to be potential reviewers.

@joachifm
Copy link
Contributor

joachifm commented Jan 6, 2017

Is this a known problem?

Yes; patchelf and paxctl don't always play nice when dealing with pre-compiled binaries. Sometimes changing the order works, but there are cases where it doesn't work at all (tor-browser being one).

@joachifm joachifm merged commit f1dc2dd into NixOS:master Jan 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants