db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6768) List the enabled protocols in derby.log for network server configuration
Date Fri, 14 Nov 2014 23:30:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213063#comment-14213063
] 

ASF subversion and git services commented on DERBY-6768:
--------------------------------------------------------

Commit 1639804 from [~mamtas] in branch 'code/trunk'
[ https://svn.apache.org/r1639804 ]

DERBY-6768(List the enabled protocols in derby.log for network server configuration)

With this change, we will now print the enabled protocols list in the log file when the server
starts up. A sample new line in the log will look as follows
 Wed Nov 12 21:32:21 PST 2014 : Apache Derby Network Server - 10.12.0.0 alpha - (1636020M)
Enabled Protocols are SSLv3, TLSv1, TLSv1.1, TLSv1.2

> 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
>         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)

Mime
View raw message