[
https://issues.apache.org/jira/browse/NIFI-16549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141150#comment-18141150
]
ASF subversion and git services commented on NIFI-16549:
--------------------------------------------------------
Commit 6b7c3938042025a88c19aeaa9ca92db832d6fde2 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6b7c3938042 ]
NIFI-16549 Added Hostname Verification description for Splunk SSL (#11891)
> Add Hostname Verification Description to Splunk SSL Context Service Property
> ----------------------------------------------------------------------------
>
> Key: NIFI-16549
> URL: https://issues.apache.org/jira/browse/NIFI-16549
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Fix For: 2.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Splunk Processors support a custom {{SSL Context Service}} property to
> configure specific Certificate Authorities for TLS connnections. Recent
> changes applied this configuration to all current Splunk Processors, which
> included a custom Trust Manager implementation that limits hostname
> verification to check the configured Hostname against the connected Peer
> Host. This does not provide the same level of protection as standard
> verification described in RFC 9525 Section 6, so the property description
> should be updated.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
