Frida: Difference between revisions

From NixOS Wiki
imported>Mic92
No edit summary
imported>Mic92
improve automation of fhsuserenv
Line 37: Line 37:
       which
       which
       git
       git
       python3
       (python3.withPackages (p: [ p.setuptools ]))
       nodejs
       nodejs
       perl
       perl
       curl
       curl
       glibc_multi
       glibc_multi
      yarn
     ];
     ];
    profile = ''
      export hardeningDisable=all
      # initialize sdk
      make
      # npm does not frida-gum/bindings/gumjs/node_modules -> bug?
      (cd frida-gum/bindings/gumjs && yarn install)
      # for frida-python egg
      export FRIDA_VERSION=$(git describe --tags)
      export FRIDA_EXTENSION=$(realpath build/frida-linux-x86_64/${python3.sitePackages}/_frida.so)
    '';
   };
   };
in fhs.env
in fhs.env
</syntaxHighlight>
For some reason <code>frida-gum/bindings/gumjs/</code> does automatically install its node modules:
<syntaxHighlight lang=console>
$ cd frida-gum/bindings/gumjs/
$ nix-shell -p yarn --command "yarn install"
</syntaxHighlight>
</syntaxHighlight>


Line 63: Line 68:


<syntaxHighlight lang=console>
<syntaxHighlight lang=console>
$ export FRIDA_VERSION=11.0.13
$ export FRIDA_EXTENSION=$(realpath build/frida-linux-x86_64/lib/python3.6/site-packages/_frida.so)
$ cd frida-python/src/
$ cd frida-python/src/
$ python setup.py bdist_egg
$ python setup.py bdist_egg

Revision as of 09:02, 1 September 2018

Frida is a dynamic binary instrumentation framework.

Getting it work on NixOS

The project provides pre-compiled binaries that almost work out of the box (when installed via pip install frida) However at runtime it unpacks a helper called frida-helper-64 that uses /lib64/ld-linux-x86-64.so.2 as its link-loader. The error message will be similar to this one:

$ frida-trace -i "recv*" 1
"/run/user/1000/frida-ea4a59ca62f7c8d1d49bd898ec313eeb/frida-helper-64": No such file or directory (os error 2)

Since the helper is not accessible on the filesystem it cannot patched with patchelf. A simple hack is to symlink an arbitrary link loader to this directory:

$ ldd /bin/sh
...
/nix/store/83lrbvbmxrgv7iz49mgd42yvhi473xp6-glibc-2.27/lib/ld-linux-x86-64.so.2 => /nix/store/83lrbvbmxrgv7iz49mgd42yvhi473xp6-glibc-2.27/lib64/ld-linux-x86-64.so.2 (0x00007fa78b289000)
$ ln -s /nix/store/83lrbvbmxrgv7iz49mgd42yvhi473xp6-glibc-2.27/lib/ld-linux-x86-64.so.2 /lib64/ld-linux-x86-64.so.2

Compile from source

Frida provides a pre-compiled SDK. Since it assumes many binaries in /usr/bin/, the best option is to use buildFHSUserEnv:

with import <nixpkgs> {};
let
  fhs = pkgs.buildFHSUserEnv {
    name = "frida-env";
    targetPkgs = pkgs: with pkgs; [
      gcc_multi
      binutils
      gnumake
      which
      git
      (python3.withPackages (p: [ p.setuptools ]))
      nodejs
      perl
      curl
      glibc_multi
      yarn
    ];
    profile = ''
      export hardeningDisable=all
      # initialize sdk
      make
      # npm does not frida-gum/bindings/gumjs/node_modules -> bug?
      (cd frida-gum/bindings/gumjs && yarn install)

      # for frida-python egg
      export FRIDA_VERSION=$(git describe --tags)
      export FRIDA_EXTENSION=$(realpath build/frida-linux-x86_64/${python3.sitePackages}/_frida.so)
    '';
  };
in fhs.env

Afterwards the build system can be used as documented:

$  make python-64

The python egg can be build then like this:

$ cd frida-python/src/
$ python setup.py bdist_egg
$ easy_install dist/frida-*.egg

Mic92 has an expression that provides a pre-compiled version of frida using the compiled egg as shown.