Last I knew of the webSockets security issue it was a specification-level vuln. In that intermediate caches could be poisoned. Such that traffic could be re-directed or intercepted. Have not tracked it close enough to be more specific. I find eJabberd + strophe a working technique. Difference is likely to be if sending messages, then xmpp. Sending raw data, webSockets. <<-----------???
MarkT [Non-text portions of this message have been removed] ------------------------------------ ----- To unsubscribe send a message to: [email protected] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ----Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
