Got an issue where certain functions aren't being resolved and hence are
null when being invoked. Need to debug the loading of the DLL to see why
this is the case.
I am working on automating POSIX meterpreter builds, and one step is
removing the requirement to download files from external sites during
the build process. So, this incorporates the latest stable libpcap
source and updates the patches as needed.
The Makefile also moves (@wvu-r7 was amused that Makefile.pcap wasn't
actually a pcap file :) and simplifies a little build foo.
I updated and got the 64-bit kernel + 32-bit userspace TPACKET v1 patch
merged upstream, but its not in a release yet, so the patch is still
needed. See https://github.com/the-tcpdump-group/libpcap/pull/421
- try to share some bits between different makefiles, make modifying
global compiler flags not such a huge pain.
- directly specify we should be using the gold rather than bpf linker
- make compiler output largely quiet except where we care - allow
warnings to actually be visible
- don't delete downloaded tarballs with --really-clean
- add missing dependencies between libraries
(--no-add-needed/--no-copy-dt-needed-entries causes lots of trouble)
- update readme to show what to install to build
I made minimal changes to the loader makefile - it breaks easily.
-Os prevents if from being able to load libc, for instance
Meterpreter's build scripts dynamically pull in OpenSSL from the
canonical remote site, https://openssl.org.
This ensures that we pull in 0.9.8za, which is patched against the
various OpenSSL vulns described at
https://www.openssl.org/news/secadv_20140605.txt
The SHA1sum should be:
adca1eb1a103a5536b24e1ed7e45051e2939731 openssl-0.9.8za.tar.gz
The MD5sum should be:
2f989915f8fea49aa1bc37aa58500cce openssl-0.9.8za.tar.gz
The existing make file would use `pwd` to figure out the current
folder instead of using the base directory of the script. This
causes issues when running commands from different locations (such
as in the case of from the meterpreter_binds folder).
This commit fixes this problem.
Thanks MM for pointing out that this was missed. The other dirs
referenced in #183 were addressed in 134b6c874fcb363594103f082bc2bacf8a0bd2c7
[Closes#183]
This new target adds debugging symbols and doesn't strip binaries. New
bins are considerably bigger, but may be more helpful when diagnosing
problems or adding new features.
[Fixes#6343]
