You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mr TheSegfault (JIRA)" <ji...@apache.org> on 2019/06/25 22:06:00 UTC

[jira] [Updated] (MINIFICPP-933) Raw site to site TLS bug went unnoticed in 0.6.0

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

Mr TheSegfault updated MINIFICPP-933:
-------------------------------------
    Summary: Raw site to site TLS bug went unnoticed in 0.6.0  (was: TLS bug went unnoticed)

> Raw site to site TLS bug went unnoticed in 0.6.0
> ------------------------------------------------
>
>                 Key: MINIFICPP-933
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-933
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Bug
>            Reporter: Mr TheSegfault
>            Assignee: Mr TheSegfault
>            Priority: Blocker
>             Fix For: 0.6.0, 0.7.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> TLS bug went unnoticed until we introduced jemalloc found while running jemalloc stats and running windows tests. unit tests do not cause the problem generally but jemalloc and valgrind show the issue pretty easily. HTTP site to site isn't impacted, only Raw Site To Site. Because this is a memory issue it doesn't always fail but the error is clearly there in the code. 
> The initial problem first identified through building windows tests for MINIFICPP-796; however docker tests proved instrumental in finding it. I confirmed on a running instance. HTTP site to site does not use this code path, so it is not impacted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)