network open during boot

[GoogleCodeExporter]

Hi,

I noticed the following race condition:

During device startup the 3G net and the wifi connections may become ready 
_before_ droidwall has run and secured the device. Applications that start up 
on boot have a (short but) usable time frame to send data.

I noticed it this way:
Rommanager is blocked (by accident) by my setup but it was able to notify me of 
a CM update. Not aware that i block it, i tried to load that, which failed 
because iptables had been set up in the meantime.

This leaves a droidwall secured device vulnerable to information leakage by any 
app each boot if that app is auto started before droidwall on boot.

Is it possible to start droidwall earlier during boot?

Best regards,
Chris

Original issue reported on code.google.com by chr.eg...@gmail.com on 8 Oct 2011 at 8:59

[GoogleCodeExporter]

That is (unfortunately) an Android limitation...
All you can do is to "transform" both DroidWall and Superuser Permissions into 
system applications - using Titanium Backup, for example.
System applications *should* load faster than non-system ones, but that is not 
enforced by Android either.

Anyway, it is better than nothing... ;)

Original comment by rodrigo...@gmail.com on 10 Oct 2011 at 2:06

• Changed state: WontFix

[GoogleCodeExporter]

I thought of a workaround for this behaviour. If the developer could add an 
option for Droidwall to put the phone in airplane mode upon exit, and take it 
out of airplane mode after it is fully loaded, then other applications would 
not be able to use the bootup time to access the network.

Original comment by gofish...@gmail.com on 23 Apr 2014 at 1:29