[
https://issues.apache.org/jira/browse/DERBY-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232609#comment-14232609
]
Bryan Pendleton commented on DERBY-6768:
----------------------------------------
When I look here:
https://svn.apache.org/viewvc/db/derby/code/branches/10.11/java/drda/org/apache/derby/impl/drda/NetworkServerControlImpl.java?view=log
The newest revision I see is:
https://svn.apache.org/viewvc?view=revision&revision=1643057
Which I think is the revision you are referring to. It seems to me to have made
it to the server correctly.
> List the enabled protocols in derby.log for network server configuration
> ------------------------------------------------------------------------
>
> Key: DERBY-6768
> URL: https://issues.apache.org/jira/browse/DERBY-6768
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 10.12.0.0
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Fix For: 10.11.1.3, 10.12.0.0
>
> Attachments: DERBY-6768_patch1_diff.txt
>
>
> DERBY-6764 is the result of poodle security alert in SSLv3 and SSLv2Hello
> protocols. For future, it will be good to know the protocols that are enabled
> on the server side so it is easier to know if the product may be impacted by
> a security issue with any specific protocol. To achieve this, at the server
> boot up time, we should list these enabled protocols in derby.log
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
