Hi,
JaCoCo does not provide any security mechanisms because there are standard tools for this:
1) Make sure the agent server binds on a local interface only (loopback). This is default.
2) Use a ssh tunnel with port forwarding to get remote access. ssh provides secure communication and different authentication options.
Regards,
-marc
--
You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/197785a3-1048-4ce9-b9a7-0bb1dda88f51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,
JaCoCo does not provide any security mechanisms because there are standard tools for this:
1) Make sure the agent server binds on a local interface only (loopback). This is default.
2) Use a ssh tunnel with port forwarding to get remote access. ssh provides secure communication and different authentication options.
Regards,
-marc
On 2017-07-11 01:58, TreverW wrote:
Hello,Is it possible to secure the jacocoagent tcp stream with some form of authentication? If, for example the jacocoagent is running in a container (in our case, a kubernetes pod) with nginx in front of it. We would like to prevent just anyone from being able to connect to the tcp port and get a dump.Thank you.--
You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+unsubscribe@googlegroups.com.