Don't do any requests if the libc currently in use on the system running the exploit matches already. This is a small short circuit optimization when the remote target uses the same libc as the local one.
This looks at the libc loaded by the local shell binary. This appears more dynamic than hardcoding library paths but only considers one architecture. It'd be possible to look at other local architectures like i386 on an amd64 host in the future.
Don't do any requests if the libc currently in use on the system running the exploit matches already. This is a small short circuit optimization when the remote target uses the same libc as the local one.
This looks at the libc loaded by the local shell binary. This appears more dynamic than hardcoding library paths but only considers one architecture. It'd be possible to look at other local architectures like i386 on an amd64 host in the future.
Refs #983