Match the Target's libc

• The single most common reason a remote exploit fails: your local libc offsets do not match the server's libc.
• Your working local chain breaks remotely because system, /bin/sh, and one-gadget offsets are all different.
• Tools that fix this:
• pwninit — given the challenge binary and the provided libc, it patches the binary to use that libc and pulls the matching loader, so local runs mirror the server.
• libc-database / libc.rip — identify the exact libc from a few leaked bytes when the organizer did not hand you one.
• Always build Stage 1 offsets against the provided libc, not your system's /lib/x86_64-linux-gnu/libc.so.6.