For those kind of checks why would you look at the source? Stick a proxy between the internet and the device to see what it does.
Seems waaaay easier than looking for the mythical badCodeGoesHere function.
Seems waaaay easier than looking for the mythical badCodeGoesHere function.
The thing is this isn't just about network interactions. By taking a quick scan of the code you also (1) might learn something new, (2) can see the athors general attitudes to things, (3) might spot some other nasty activity (does this program hot load code from a remote source, try to obscure what it is doing, scan the file system? Etc)