[jira] [Commented] (JAMES-385) Allow to prevent weak ciphers when using "useTLS"

["Matthieu Baechler (JIRA)" <se...@james.apache.org>]

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

Matthieu Baechler commented on JAMES-385:
-----------------------------------------

Does this ticket still need work ?

> Allow to prevent weak ciphers when using "useTLS"
> -------------------------------------------------
>
>                 Key: JAMES-385
>                 URL: https://issues.apache.org/jira/browse/JAMES-385
>             Project: James Server
>          Issue Type: Bug
>          Components: SMTPServer
>    Affects Versions: 2.2.0, 2.3.0, 2.3.1, 2.3.2, 3.0-M1, 3.0-M2
>         Environment: Linux, jdk 1.4
>            Reporter: Ralf Hauser
>            Assignee: Eric Charles
>            Priority: Critical
>             Fix For: 3.0-beta3, 3.0.0-beta5
>
>         Attachments: Cornerstone.patch.zip
>
>
> http://james.apache.org/usingTLS_2_1.html and http://wiki.apache.org/james/UsingSSL explain how to setup a pop3s etc. describe how to secure a client connection to James.
>    openssl s_client -connect pops.mydom.com:995 -cipher EXPORT
> illustrates that this is possible with james.
> One might argue that a decent client will never ask the server to negotiate a weak cipher. But an attacker (man-in-the-middle) could remove stronger ciphers from the client's offered cipher list, and then break the weak cipher and e.g. obtain the user password to later hijack the account.
> Please amend the documentation how prevent this from happening by forcing james to only negotiate sessions with 128+ bit session key strength



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org