search

prey / prey-bash-client

DEPRECATED - Project no longer supported, please consider using https://github.com/prey/prey-node-client instead
GNU General Public License v3.0
868 stars 135 forks source link

Modules not running when ciphered instructions activated #403

Closed ivanjpg closed 11 years ago

ivanjpg commented 11 years ago

If the ciphered instructions are activated, then the modules would not run even if the device is marked as missing.

The core/pull file(at line 60) is trying to get the «Content-Type» header but the server is returning a «content-type» one. If you look at the core/functions file(line 320) the «grep» command is running without a case-insensitive flag(-i), so the header is not read correctly and prey.sh asummes that the response is not ciphered.

BTW, it is also an issue over win platform, the solution is the same.

I think to put -i flag to grep is the right solution because the RFC2616 4.2 section that claims:

«Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive»

Hope this helps, Ivan

dialex commented 11 years ago

I can verify that this is a real issue and that by turning off the "ciphered instructions" the issue is mitigated.

mcbsys commented 10 years ago

I have this identical issue with Prey 0.6.2 under 32-bit Windows 8.1. Had to turn off Ciphered instructions to get reports to work. Maybe it only happens when Ciphered is turned on from the start, i.e. when a device has never been allowed to check in unciphered? More details:

http://answers.preyproject.com/topics/marked-as-missing-running-ok-but-no-reports-prey-0-6-2