| |||||||||||||
Prey: Open source theft recoveryPrey: Open source theft recoveryPosted Jul 7, 2011 9:33 UTC (Thu) by akumria (subscriber, #7773)In reply to: Prey: Open source theft recovery by pcampe Parent article: Prey: Open source theft recovery
Or, just as simple, ensure that the target domain never resolves to anything useful.
(Log in to post comments)
Prey: Open source theft recovery Posted Jul 7, 2011 10:26 UTC (Thu) by pcampe (guest, #28223) [Link]
Title: Prey disabling howto
1. rm -f usual_path_of_prey/usual_file_1
It's also true that, before issuing 1. and 2., the system is up and running, and so there is a small window of opportunity for Prey to call the target domain and downloading instructions (if there is some network connectivity, and it's a big if) but it's not bullet-proof; so it seems to me that some kind of obfuscating executables is worth of; am I missing something?
|
|||||||||||||