Msfpayload output size significantly bigger in v3.3 vs. v3.2

[Raul Siles <raul.siles () gmail com>]

Hi there,
I've seen that the standard (reverse or bind) Meterpreter payload size
generated by msfpayload (for Windows .exe files) is an order of
magnitud bigger in MSF v3.3.1 vs. MSF v.3.2.

MSF v3.2:    9.728 bytes
MSF v3.3.1: 87.552 bytes

Without having gone in depth into the source code, is there any option
to reduce the size of the generated payload to a smaller one (like in
the range of v3.2)?

The reason I'm asking this is due to constraints in the integration
between sqlninja and MSF to updload bigger payloads through the
Windows debug.exe technique (max 64K) using a SQLi vulnerability.

Thanks,
--
Raul Siles
www.raulsiles.com
_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework