Is it expected that daemon binds to all ipv6 addresses

(Abhishek Mukherjee) #1

So posting this in Help and not creating a bug because, without knowing more about the Gradle source, I don’t know if this is expected or not. It’s also proving difficult for me to test since the networks I have access to don’t actually support ipv6. If it’s a bug I can go through those motions as necessary

Is it expected for gradle to bind to a random ipv6 port on all addresses on a host? Specifically, after firing up a Gradle 3.4.1 daemon with just an empty gradle build, I see:

[amukherjee@amukherjee-dev /tmp/d]% ps -f -p 17068 -ww
amukher+ 17068     1  1 09:50 ?        00:00:05 /usr/lib/jvm/java-8-jdk/bin/java -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 -Duser.language=en -Duser.variant -cp /home/amukherjee/.gradle/wrapper/dists/gradle-3.4.1-bin/71zneekfcxxu7l9p7nr2sc65s/gradle-3.4.1/lib/gradle-launcher-3.4.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 3.4.1
[amukherjee@amukherjee-dev /tmp/d]% sudo ss -tlnp | grep 17068
LISTEN     0      0           :::45397                   :::*                   users:(("java",pid=17068,fd=186))

As I suggested in the preamble, I can’t quite tell if I’m imagining the representation of that output or not, since I can’t connect to it for networking reasons. So would also appreciate someone telling me if I’m just reading the output of ss wrong or not :slight_smile:

(Abhishek Mukherjee) #2

Not sure if this is correct form but, ping? After a little more poking around, I do think it’s a security bug to have it open, but don’t know what is listening on the other side so may not be a big problem