You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Bernd Fondermann (JIRA)" <ji...@apache.org> on 2011/06/28 17:55:16 UTC
[jira] [Created] (VYSPER-287) No SASL auth mechanism available
suited for unencrypted XMPP connections
No SASL auth mechanism available suited for unencrypted XMPP connections
------------------------------------------------------------------------
Key: VYSPER-287
URL: https://issues.apache.org/jira/browse/VYSPER-287
Project: VYSPER
Issue Type: Bug
Components: authentication
Affects Versions: 0.7
Reporter: Bernd Fondermann
preconditions: server has requirement for TLS encryption set to FALSE. client connects and decides to not use encryption.
client tries to authenticate and requests SASL mechanisms. Vysper only presents SASL PLAIN.
the client aborts the connection handshake because no suitable SASL mechanism is available.
fix: we need more SASL mechanisms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VYSPER-287) No SASL auth mechanism available
suited for unencrypted XMPP connections
Posted by "Kaja Hovi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058252#comment-13058252 ]
Kaja Hovi commented on VYSPER-287:
----------------------------------
I might give it a try if you provide me as much information as possible.
> No SASL auth mechanism available suited for unencrypted XMPP connections
> ------------------------------------------------------------------------
>
> Key: VYSPER-287
> URL: https://issues.apache.org/jira/browse/VYSPER-287
> Project: VYSPER
> Issue Type: Bug
> Components: authentication
> Affects Versions: 0.7
> Reporter: Bernd Fondermann
>
> preconditions: server has requirement for TLS encryption set to FALSE. client connects and decides to not use encryption.
> client tries to authenticate and requests SASL mechanisms. Vysper only presents SASL PLAIN.
> the client aborts the connection handshake because no suitable SASL mechanism is available.
> fix: we need more SASL mechanisms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VYSPER-287) No SASL auth mechanism available
suited for unencrypted XMPP connections
Posted by "Bernd Fondermann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058216#comment-13058216 ]
Bernd Fondermann commented on VYSPER-287:
-----------------------------------------
Don't hold your breath... Sorry. - Unless you give it a try.
> No SASL auth mechanism available suited for unencrypted XMPP connections
> ------------------------------------------------------------------------
>
> Key: VYSPER-287
> URL: https://issues.apache.org/jira/browse/VYSPER-287
> Project: VYSPER
> Issue Type: Bug
> Components: authentication
> Affects Versions: 0.7
> Reporter: Bernd Fondermann
>
> preconditions: server has requirement for TLS encryption set to FALSE. client connects and decides to not use encryption.
> client tries to authenticate and requests SASL mechanisms. Vysper only presents SASL PLAIN.
> the client aborts the connection handshake because no suitable SASL mechanism is available.
> fix: we need more SASL mechanisms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VYSPER-287) No SASL auth mechanism available
suited for unencrypted XMPP connections
Posted by "Kaja Hovi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058013#comment-13058013 ]
Kaja Hovi commented on VYSPER-287:
----------------------------------
Any idea when will be this fixed?
> No SASL auth mechanism available suited for unencrypted XMPP connections
> ------------------------------------------------------------------------
>
> Key: VYSPER-287
> URL: https://issues.apache.org/jira/browse/VYSPER-287
> Project: VYSPER
> Issue Type: Bug
> Components: authentication
> Affects Versions: 0.7
> Reporter: Bernd Fondermann
>
> preconditions: server has requirement for TLS encryption set to FALSE. client connects and decides to not use encryption.
> client tries to authenticate and requests SASL mechanisms. Vysper only presents SASL PLAIN.
> the client aborts the connection handshake because no suitable SASL mechanism is available.
> fix: we need more SASL mechanisms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VYSPER-287) No SASL auth mechanism available
suited for unencrypted XMPP connections
Posted by "Bernd Fondermann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058269#comment-13058269 ]
Bernd Fondermann commented on VYSPER-287:
-----------------------------------------
See VYSPER-15 for the overall SASL issue. There are links to each SASL mechanisms. If we need more, we should add subtasks for them.
I've added links to the specs to VYSPER-15 and VYSPER-33.
For how to implement them in VYSPER, pls follow up on dev@mina.apache.org for any questions you might have.
> No SASL auth mechanism available suited for unencrypted XMPP connections
> ------------------------------------------------------------------------
>
> Key: VYSPER-287
> URL: https://issues.apache.org/jira/browse/VYSPER-287
> Project: VYSPER
> Issue Type: Bug
> Components: authentication
> Affects Versions: 0.7
> Reporter: Bernd Fondermann
>
> preconditions: server has requirement for TLS encryption set to FALSE. client connects and decides to not use encryption.
> client tries to authenticate and requests SASL mechanisms. Vysper only presents SASL PLAIN.
> the client aborts the connection handshake because no suitable SASL mechanism is available.
> fix: we need more SASL mechanisms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira