[
https://issues.apache.org/jira/browse/DERBY-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232592#comment-14232592
]
Mamta A. Satoor commented on DERBY-6768:
----------------------------------------
I just issued a svn commit for backport to 10.11 but for some reason, all I got
is
$ svn commit --username=mamta
Sending .
Sending
java\drda\org\apache\derby\impl\drda\NetworkServerControlImpl.java
Sending java\drda\org\apache\derby\loc\drda\messages_en.properties
Transmitting file data ..
It never came back with the revision number and was hung there for a long time
so I cancelled out of it with Ctrl-C. But it seems like commit made it into svn
repository because I created a new 10.11 client and I see my changes in there.
I will appreciate if someone can do svn update on 10.11 client and if they can
see the changes for enabled protocols in NetworkServerControlImpl.java and
messages_en.properties. In the mean time, I will work on 10.10 backport.
> 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)
