--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Unless you're connected directly to the internet (not through a router/NAT device), adbd will not be accessible outside your LAN. Still insecure though.If you don't need debugging, you can always disable adbd from init or just delete/rename adbd binary.
On Dec 15, 2017 2:29 AM, "Andrei Mikhailov" <a.m...@gmail.com> wrote:
No, this does not work. Setting `service.adb.tcp.port` to `-1` just makes it listening on 0.0.0.0:5555--Looks like a backdoorIf adbd cannot be disabled, then this is a grave issue, making the system only useful as a toy
Em quinta-feira, 14 de dezembro de 2017 19:43:18 UTC-2, Andrei Mikhailov escreveu:That could be turned off by setting `service.adb.tcp.port` to `-1`.Problem solved.Sorry for bothering.
Em quinta-feira, 14 de dezembro de 2017 00:44:22 UTC-2, Andrei Mikhailov escreveu:I am using Android-x86 6.0-r3adbd is listening on all interfaces, and there seems to be no way to restrict itthis would seem to be very insecure, because anybody from the Internet can do almost whatever they want on my device...Is there any way to disable adbd, or maybe put some constraints on where it can listen?
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com.