[Experimental] peek and poke environment variables
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
src
.gitignore
Cargo.lock
Cargo.toml
LICENSE
Makefile
README.md
target_python.sh
target_ruby.sh

README.md

peke_envs (peek poke environment variables)

asciicast

Concepts

  • Experimental purpose.
  • Peek(Read) current environment variables in a arbitrary process.
  • [WIP] Poke(Overwrite) environment variables in a arbitrary process.

You can do the same things more easily/safely by using gdb.

How it works

  • Specify a target process as the tracee by pid.
  • Search location for libc and __environ of the tracee.
  • Exec Ptrace Attach to the tracee.
  • By executing Ptrace Peek, read and follow pointers, and read environment variables.
  • [WIP] By executing Ptrace Peek, overwrite environment variables.

Usage

  • Peek environment variables.
$ peek <pid>
  • [WIP] Poke environment variables.
$ peek <pid> <key> <value>

License

MIT

Author

Satoshi Tajima