You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/06/10 16:00:00 UTC

[jira] [Closed] (SUREFIRE-1796) The session of TCP channel should be authenticated

     [ https://issues.apache.org/jira/browse/SUREFIRE-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-1796.
----------------------------------
    Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=08740026d6a2feb6746b5dcd88490f1a24b17003

> The session of TCP channel should be authenticated
> --------------------------------------------------
>
>                 Key: SUREFIRE-1796
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1796
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin, process forking
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M5
>
>
> We introduced the configuration parameter {{forkNode}} which is used to reimplement the communication channel used between the Maven process and Surefire subprocess.
> There are two embedded implementations. The TCP implementation should use authentication.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)