[
https://issues.apache.org/jira/browse/PROTON-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437561#comment-15437561
]
ASF GitHub Bot commented on PROTON-1224:
----------------------------------------
Github user JemDay commented on the issue:
https://github.com/apache/qpid-proton/pull/79
Robbie
Thanks, i've taken a quick look and nothing leaps out at me, i'll try
pulling this down and checking locally. I will try and get to this today but it
might stretch to tomorrow.
I'd also like to discuss off-line another enhancement we'd like to make
whereby we can provide/inject an SSLContext directly - this is the way we can
conform with our in-house security constraints and mechanisms.
Jem..
> Proton-J SSL uses deprecated Bouncy Castle functionality
> --------------------------------------------------------
>
> Key: PROTON-1224
> URL: https://issues.apache.org/jira/browse/PROTON-1224
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Affects Versions: 0.12.2
> Reporter: Jem Day
>
> The BouncyCastle project deprecated functionality used by the proton-j driver
> in version 1.48. This causes run-time issues for us as our application
> containers are using newer BC versions.
> Thanks for you patience with this, hopefully this is now cleaner PR, I have
> closed the original PR #75
> Jem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
