-
Improvement
-
Resolution: Fixed
-
Major
-
-
Jenkins 2.220
In 2.0 we try to turn off listeners by default, but UDPBroadcastThread and DNSMultiCast are still started.
We should
- create global settings (/configureSecurity) allowing these to be enabled or disabled
- disable them by default
- move the start and stop calls to within the associated classes using @Initializer/@Terminator
The third is to make it easier to split these off into a distinct plugin in the future. (Or fold them into the swarm plugin, which seems to be the major user of one of them, I cannot remember which.)
- is blocking
-
JENKINS-30749 Jenkins should be secure out of the box by default
- Resolved
- is duplicated by
-
JENKINS-60913 Remove network discovery services
- Resolved
-
JENKINS-50816 Disable DNS Multicast by default (and detach it to a plugin)
- Resolved
- is related to
-
JENKINS-14441 Could not initialize the host network interface
- Open
-
JENKINS-21727 FreeBSD 10, UDP Multicast traceback on startup
- Open
-
JENKINS-34730 DNSIncoming dumps in to the Log
- Open
-
JENKINS-10160 When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
- Fixed but Unreleased
-
JENKINS-25369 DNS multicast error messages
- Resolved
-
JENKINS-23186 "Got conflicting probe from ourselves" warning message on Jenkins startup
- Closed
- links to