qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael H. Schloming (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PROTON-553) Proton-C does not URLdecode password before doing SASL-PLAIN
Date Fri, 04 Apr 2014 19:04:15 GMT

     [ https://issues.apache.org/jira/browse/PROTON-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafael H. Schloming resolved PROTON-553.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7
         Assignee: Rafael H. Schloming

> Proton-C does not URLdecode password before doing SASL-PLAIN
> ------------------------------------------------------------
>
>                 Key: PROTON-553
>                 URL: https://issues.apache.org/jira/browse/PROTON-553
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>            Reporter: James Birdsall
>            Assignee: Rafael H. Schloming
>             Fix For: 0.7
>
>         Attachments: sasl.c
>
>
> This is a serious issue using Proton-C against ServiceBus because our passwords are base64-encoded
keys and frequently contain '/'. Previous versions of Proton-C didn't care about technically
illegal forward slashes in the URL, but 0.7 sure does. URL encoding the password gets around
that, but then the encoded password is presented to our broker and is rejected. Since Proton
is the one dealing with a URL and enforcing URL rules, it should do the decoding before passing
the pieces on to other layers.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message