Apps are allowed when installed even when they are not checked in the settings

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install new app
2. Check settings in droidwall (app has no rights)
3. Start app. Access internet (adds, ... )
4. Check settings in droidwall (everything still ok)
5. Apply settings again
6. App doesn't have access anymore

What is the expected output? What do you see instead?
No internet access expected but app has internet access.

What version of the product are you using? On what operating system?
droidwall 1.4.7 and previous.
I'm using Android 2.2 (LeeDroiD 2.3d ROM on HTC Desire)

Original issue reported on code.google.com by will_d...@gmx.net on 2 Feb 2011 at 9:51

[GoogleCodeExporter]

I tried to reproduce this many times without success... these are the steps I 
tried:

1. Select White-list mode
2. Allow just the the following: "Market"; "Media Storage, DRM Protected 
Content Storage, Download Manager" and "Calendar Sync Adapter, Google Services 
Framework, Contacts Sync Adapter" (for download)
3. Apply rules
4. Installed app with ads from the Market (tried four different apps)
5. Right after installing, and without opening DroidWall, executed the 
installed app

Result: No ads are shown, DroidWall logs confirms that app has been blocked 
several packets.

I did this test on three different devices, with Android 2.3 and 2.2

Am I doing something different than you?

Original comment by rodrigo...@gmail.com on 2 Feb 2011 at 1:00

[GoogleCodeExporter]

I tried it again and the exact same procedure and the app has access. I tried 
it this time with Posterous. Installed it, checked rules (no checks for 
Posterous), started it and I could post messages. I opened DW -> apply rules 
and Posterous was blocked. Very strange.

Original comment by will_d...@gmx.net on 2 Feb 2011 at 1:58

[GoogleCodeExporter]

I believe this should be fixed on the latest version, since DroidWall now 
handles apps installation/removal in a better way.
Fell free to comment here if not, an I will reopen.

Original comment by rodrigo...@gmail.com on 21 Mar 2011 at 12:02

• Changed state: Fixed

[GoogleCodeExporter]

Sorry but this bug isn't fixed. I don't know how I can help you fixing this 
serious bug. You need any logs?

I've installed Opera and can access internet without any problems. I need to 
start DW, apply changes even I didn't change anything and then Opera was 
blocked.

Original comment by will_d...@gmx.net on 21 Mar 2011 at 3:13

[GoogleCodeExporter]

Can you please post the iptables rules right after the app successfully got 
Internet access (when it shouldn't)? Please also post the application ID (the 
number displayed by DroidWall in the list).

To get iptables rules, either use the "Show Rules" button on DroidWall, or type 
the following command on a root shell:
iptables -L -v

Thanks!

Original comment by rodrigo...@gmail.com on 21 Mar 2011 at 4:58

• Changed state: New

[GoogleCodeExporter]

Opera Mini 10206

Original comment by will_d...@gmx.net on 21 Mar 2011 at 5:30

Attachments:

• before_install.txt
• after_install.txt

[GoogleCodeExporter]

When I have applied the rules without changing them, Opera is blocked and I get 
a much longer list for iptables

Original comment by will_d...@gmx.net on 21 Mar 2011 at 5:31

[GoogleCodeExporter]

The rules you posted are completely empty (even before installation). Are you 
sure the issue is related to installing applications?

There are some other applications (e.g.: Tether) that remove ALL iptables 
rules, so they effectively break DroidWall functionality.

Original comment by rodrigo...@gmail.com on 21 Mar 2011 at 7:47

[GoogleCodeExporter]

I think there is another problem.

1. I reboot. NO rules are set. I can apply rules.
2. I install a new app and it doesn't have access.

The question is why the rules aren't applied after reboot.

Original comment by will_d...@gmx.net on 21 Mar 2011 at 10:50

[GoogleCodeExporter]

Now we are getting somewhere!
Can you please post a "logcat" output right after rebooting? (wait around 30 
seconds to get the logcat, just to make sure DroidWall has run)
Thanks

Original comment by rodrigo...@gmail.com on 22 Mar 2011 at 12:13

[GoogleCodeExporter]

How can I create the logcat you need? aLogCat doesn't work the first minutes 
after reboot

Original comment by will_d...@gmx.net on 22 Mar 2011 at 4:01

[GoogleCodeExporter]

use the following command on a terminal emulator, for example:
logcat > /sdcard/locat.txt

Original comment by rodrigo...@gmail.com on 22 Mar 2011 at 4:35

[GoogleCodeExporter]

This is the log after reboot

Original comment by will_d...@gmx.net on 22 Mar 2011 at 8:36

Attachments:

• logcat.txt

[GoogleCodeExporter]

Interesting... do you use any startup blocker app?
It seems DroidWall didn't even run on startup. It must be able to run in order 
to apply the rules on boot.

Original comment by rodrigo...@gmail.com on 22 Mar 2011 at 8:57

[GoogleCodeExporter]

I don't run any blockers

Original comment by will_d...@gmx.net on 22 Mar 2011 at 9:08

[GoogleCodeExporter]

I uninstalled DW and installed it again. Same result.

Original comment by will_d...@gmx.net on 22 Mar 2011 at 9:45

[GoogleCodeExporter]

I fixed it.
It was app2sd. DW was installed on the ext3 partition on my sd card and 
couldn't start. I moved it to the internal memory and everything is ok now

Original comment by will_d...@gmx.net on 11 Apr 2011 at 10:16

[GoogleCodeExporter]

Oh, mystery solved :D
Thanks for letting me know.

Original comment by rodrigo...@gmail.com on 12 Apr 2011 at 12:02

• Changed state: Invalid

[GoogleCodeExporter]

Is it possible that you check it DW is not installed on the internal memory?
So you can show a warning message when you open DW.

Original comment by will_d...@gmx.net on 12 Apr 2011 at 1:31