jng | tribbletron
jng | tribbletron
  • About
  • CTFs
    • Target x WiCyS CTF 2024
      • D2 Look for Insider Threats
      • D8 YARA Analysis
      • O3 Constructing your Phish
      • O7 Bypass the EDR
      • O8 Performing an Exfil of a Filesystem
      • O9.1 Escalate your Privileges
    • US CyberGames IV 2024
      • USCG IV: Forensics
      • USCG IV: Web
    • DoD Cyber Sentinel 2024
    • Amazon x WiCyS CTF 2023
    • PicoCTF.org
      • PicoCTF 2024
      • PicoCTF 2023
  • Links
    • Readings
  • Tools
  • Notes
    • To Burp or Not to Burp
    • Common issues
    • Rankings
Powered by GitBook
On this page
  1. Notes

Common issues

Last updated 9 months ago

- StackOverFlow by The problem on Linux is that pip install ... drops scripts into ~/.local/bin and this is not on the default Debian/Ubuntu $PATH.

Here's a GitHub issue going into more detail: https://github.com/pypa/pip/issues/3813

To fix, just add ~/.local/bin to your $PATH, for example by adding the following line to your .bashrc file:

export PATH="$HOME/.local/bin:$PATH"

---

In Linux, run "dpkg --print-architecture" to find out what your hardware is.If it's arm64, you can't run x86 binaries.

See: Doing the "Install necessary packages" portion of this guide got it working for my Mac/VMWare/Kali setup:

pip installs packages successfully, but executables not found from command line
James Hibbard
https://www.reddit.com/r/mac/comments/180x8yp/kali_linux_vm_wont_run_binary_m1_macbook_pro/
https://www.kali.org/docs/arm/x86-on-arm/