[NA-Discuss] [ALAC] Fwd: [Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan

Fri Apr 20 19:08:18 UTC 2018

I don't know what discussions have taken place.  But we tried using Zoom this week in one of the ICANN working groups I am involved with.  It was definitely harder to use, and either lacked some of the functionality of Adobe Connect or, if it had it, we didn't manage to find it. 
Bill Jouris

      From: Evan Leibovitch <evan at telly.org>
 To: Judith Hellerstein <judith at jhellerstein.com> 
Cc: ICANN ALAC list <alac at atlarge-lists.icann.org>; ttf at atlarge-lists.icann.org; NARALO Discussion List <na-discuss at atlarge-lists.icann.org>
 Sent: Friday, April 20, 2018 11:34 AM
 Subject: Re: [NA-Discuss] [ALAC] Fwd: [Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan

Funny how they've already come to the conclusion that it would be preferred to revert to Adobe Connect.I don't recall any attempt to use Zoom as a point of comparison, let alone comment on it.
The fact that ICANN needs an integrator (CoSo) for its use of what should be a simple service speaks volumes to an outsider.Just imagine what will happen as austerity kicks in and such extravagances won't be sustainable.
- Evan

On 20 April 2018 at 14:20, Judith Hellerstein <judith at jhellerstein.com> wrote:

Hi All,
Very interesting blog by Ash Rangan.  Forwarding this email widely so others could read it and discuss it.
Best,Judith
Sent from my iPad judith at jhellerstein.com Skype ID:JudithHellerstein
Begin forwarded message:

From: Nathalie Peregrine <nathalie.peregrine at icann.org>
Date: April 20, 2018 at 2:16:27 PM EDT
To: "ccwg-auctionproceeds at icann. org" <ccwg-auctionproceeds at icann. org>
Subject: [Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan

Dear all: Please take a look at this blog on Adobe Connect.  And note the request: Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here:RP-tool at icann.org Best regards,        David  https://www.icann.org/news/ blog/adobe-connect-what-next[ icann.org] ADOBE CONNECT – WHAT NEXT?As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response toreported issues[icann.org] with this service. Concurrently, we began to conduct our own forensic analysis of the reported incident and began working with our Adobe cloud service provider, CoSo Cloud LLC, and through them with Adobe to learn more. Shortly thereafter, we rolled out instances of Zoom and WebEx for the community to support remote participation (RP) and collaboration. Here's where we are now: The Forensics InvestigationWith respect to our forensics work, we received application logfiles from CoSo Cloud, going back for a period of one year. ICANN Engineering and Security teams have examined these application log files and the results of our investigation clearly show "fingerprints of incursion" by the researcher who reported the issue. We were unable to find any other indication that anyone else either identified or exploited this issue. Thanks to the person who found the bug again.Working closely with CoSo Cloud, we were able to recreate the reported issue, and understand the conditions required to trigger it. This information has been communicated to Adobe, and Adobe is working on a software fix to address the root cause of the issue.We have also been working with CoSo on options to re-enable Adobe Connect in the shorter term. We have determined there are two viable paths to accomplish this goal. They are:   
   - Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or
   - Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited.
With respect to the first option, we attempted to hack the hardened configuration in a test environment last week, and were not able to do so over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted similar tests and confirmed that this configuration is protected from exploitation of the issue. Community Feedback and Next StepsFor the last three weeks, we have been gathering limited feedback regarding users' experiences with WebEx and Zoom. So far, we have input from about 200 people, including ICANN org meeting organizers and the ICANN community. Our analysis of this feedback indicates a desire to revert back to an Adobe Connect, providing the security of the service is ensured.Accordingly, we would like to propose the following plan to the broader community for consideration:   
   - We would like to restore Adobe Connect services with both the new hardened configuration and the programmatic fix discussed above. Our intent would be to restore service by 3 May. This would allow us to use Adobe Connect during several upcoming events including the Board Workshop, the GDD Industry Summit, and ICANN62.
   - Once Adobe releases a new version of the software with a fix for this issue from their perspective, and provides assurance the update has been adequately tested, we will move toward that release of Adobe Connect in a prudent manner, with the help of CoSo Cloud.
 We believe that this approach will ensure the security of our content, and of our community interactions, while also enabling our community to use the collaboration tools of their choice. Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here:RP-tool at icann.org Meanwhile, we will continue to offer WebEx and Zoom for RP and collaboration purposes. We will also continue to follow industry developments, including the research ALAC is doing on the RP and collaboration space, to ensure we are using secure and cost-effective tools that are appropriate for our needs. I look forward to your comments!   David A. Olive
Senior Vice PresidentPolicy Development Support
Internet Corporation for Assigned Names and Numbers (ICANN) 

______________________________ _________________
SOAC-Leaders-ICANNMeeting- Planning mailing list
SOAC-Leaders-ICANNMeeting- Planning at icann.org
https://mm.icann.org/mailman/ listinfo/soac-leaders- icannmeeting-planning

______________________________ _________________
Gnso-igo-ingo-crp mailing list
Gnso-igo-ingo-crp at icann.org
https://mm.icann.org/mailman/ listinfo/gnso-igo-ingo-crp

______________________________ _________________
gnso-rpm-wg mailing list
gnso-rpm-wg at icann.org
https://mm.icann.org/mailman/ listinfo/gnso-rpm-wg

______________________________ _________________
Ccwg-auctionproceeds mailing list
Ccwg-auctionproceeds at icann.org
https://mm.icann.org/mailman/ listinfo/ccwg-auctionproceeds

______________________________ _________________
ALAC mailing list
ALAC at atlarge-lists.icann.org
https://atlarge-lists.icann. org/mailman/listinfo/alac

At-Large Online: http://www.atlarge.icann.org
ALAC Working Wiki: https://community.icann.org/ display/atlarge/At-Large+ Advisory+Committee+(ALAC)

-- 
Evan Leibovitch, Toronto Canada at evanleibovitch or @el56------
NA-Discuss mailing list
NA-Discuss at atlarge-lists.icann.org
https://atlarge-lists.icann.org/mailman/listinfo/na-discuss

Visit the NARALO online at http://www.naralo.org
------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/na-discuss/attachments/20180420/6a63dfb1/attachment-0001.html>