[asterisk-bugs] [JIRA] (ASTERISK-23099) Asterisk WSS ( Secure WebSocket) patch

[El Rusty Newtron (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213839#comment-213839 ] 

El Rusty Newtron edited comment on ASTERISK-23099 at 1/9/14 10:49 AM:
----------------------------------------------------------------------

Sorry about the confusion. I misread your profile, it does say "Has Valid License Agreement: False" Which means the license hasn't been accepted. That is likely due to the reasons sent to you in the E-mail from Digium's general counsel.

Basically. If you are submitting code on behalf of your company, then the license agreement and your E-mail should all be your company details, and if you are submitting code on behalf of yourself, it should all be your personal details.

If you need to modify the E-mail address in your profile, the easiest way will be to login with your current account to https://wiki.asterisk.org (which shares a user database with other Asterisk community sites) and edit your profile there. That change will be reflected for issues.asterisk.org, wiki.asterisk.org and code.asterisk.org. At the moment it doesn't appear you can edit your E-mail address from JIRA for whatever reason.

After you change your E-mail at wiki.asterisk.org, give it ten minutes or so to sync before you come back and fill out the license form in JIRA.

When your JIRA profile finally shows the "Has Valid License Agreement: True" then re-attach the patch to the JIRA issue. Then the patch will show up on the main view of the issue and be properly marked as submitted under license.

We'll look into making this easier in the future!
                
      was (Author: anothertestuser):
    Sorry about the confusion. I misread your profile, it does say "Has Valid License Agreement: False" Which means the license hasn't been accepted. That is likely due to the reasons sent to you in the E-mail from Digium's general counsel.

If you need to modify the E-mail address in your profile, the easiest way will be to login with your current account to https://wiki.asterisk.org (which shares a user database with other Asterisk community sites) and edit your profile there. That change will be reflected for issues.asterisk.org, wiki.asterisk.org and code.asterisk.org.

Basically. If you are submitting code on behalf of your company, then the license agreement and your E-mail should all be your company details, and if you are submitting code on behalf of yourself, it should all be your personal details.

After you change your E-mail at wiki.asterisk.org, give it ten minutes or so to sync before you come back and fill out the license form in JIRA.

When your JIRA profile finally shows the "Has Valid License Agreement: True" then re-attach the patch to the JIRA issue. Then the patch will show up on the main view of the issue and be properly marked as submitted under license.

We'll look into making this easier in the future!
                  
> Asterisk WSS ( Secure WebSocket) patch 
> ---------------------------------------
>
>                 Key: ASTERISK-23099
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23099
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_http_websocket
>    Affects Versions: 11.5.1
>         Environment: Linux, Chrome
>            Reporter: Thava Iyer
>            Assignee: Thava Iyer
>         Attachments: ast_wss_r404720_v11_5_0.patch, ast_wss_r404720_v11_5_0.patch
>
>
> Asterisk websocket interface (res/res_http_websocket.c) works well for normal websockets (ws) but fails on secure - websockets (wss). The ast_websocket_read() function, first reads the header (14) bytes using first fread() call and then , for the remaining payload,  in a while loop, it first polls the raw-socket for the date before further reads. In the normal websocket, it is fine. But for the secure-websocket case, the underlying ssl_read() would have read the whole data, in the first fread() call (of course to decrypt ) and emptied the socket-fd. This would make the ast_websocket_read() to wait for data to appear on the socket.
> This patch enables the ast_websocket_read() function to read the whole available data at first and then wait for any fragmented packets. This makes the secure-websocket connection to work properly.
> This has been tested with  Chrome 31.0.1650.63.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira