Hi I have an application I'm writing that uses SNMP and unfortunately, that protocol expects the application's host system to have port 162 binded to receive requested data. That doesn't work on stock android with apps without root permission. To me, this limit makes absolutely no sense these days, especially on an android phone. So I figured I'd ask here rather than the general LKML where they might have more legacy concerns - can it be removed from android kernels going forward? It's as simple as changing PROT_SOCK to 0 but it completely depends on upstream/vendors doing this. It also depends and possibly becomes even more pointless with 5.0+ using selinux in enforcing mode.
I seem to have no recourse at the moment as I cannot inject another node to translate the port between the systems I want to talk to and I cannot root the phone or provide a custom images. But I'll tell you what odd thing I can do... I can use the USB Host api to steal the ethernet device I'm sending packets over - not that I want to do that at all, but I am amazed I can hijack the device yet not bind to port 162. Advice/ideas? Acceptance of nuking PROT_SOCK? -Jason -- -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-kernel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
