<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I, for one, would be happy to go back to Adobe - I have had real difficulties with webex - I just couldn’t access it. And I miss having the visibility of the text, the sound of the speaker and the availability of chat (both public and private<div><br></div><div>Holly<br><div><div>On 21 Apr 2018, at 4:20 am, Judith Hellerstein <<a href="mailto:judith@jhellerstein.com">judith@jhellerstein.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="auto" style="font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div>Hi All,</div><div><br></div><div>Very interesting blog by Ash Rangan. Forwarding this email widely so others could read it and discuss it.</div><div><br></div><div>Best,</div><div>Judith</div><div><br>Sent from my iPad<span style="font-size: 13pt;"> </span><div><span style="font-size: 13pt;"><a href="mailto:judith@jhellerstein.com" style="color: purple; text-decoration: underline;">judith@jhellerstein.com</a> </span></div><div><span style="font-size: 13pt;">Skype ID:JudithHellerstein</span></div></div><div><br>Begin forwarded message:<br><br></div><blockquote type="cite"><b>From:</b><span class="Apple-converted-space"> </span>Nathalie Peregrine <<a href="mailto:nathalie.peregrine@icann.org" style="color: purple; text-decoration: underline;">nathalie.peregrine@icann.org</a>><br><b>Date:</b><span class="Apple-converted-space"> </span>April 20, 2018 at 2:16:27 PM EDT<br><b>To:</b><span class="Apple-converted-space"> </span>"<a href="mailto:ccwg-auctionproceeds@icann.org" style="color: purple; text-decoration: underline;">ccwg-auctionproceeds@icann.org</a>" <<a href="mailto:ccwg-auctionproceeds@icann.org" style="color: purple; text-decoration: underline;">ccwg-auctionproceeds@icann.org</a>><br><b>Subject:</b><span class="Apple-converted-space"> </span><b>[Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan</b><br><br></blockquote><blockquote type="cite"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a name="_MailOriginalBody">Dear all:<o:p></o:p></a></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>Please take a look at this blog on Adobe Connect. And note the request:<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b>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:<span class="Apple-converted-space"> </span></b></span><a href="mailto:RP-tool@icann.org" style="color: purple; text-decoration: underline;"><span><b>RP-tool@icann.org</b></span><span></span></a><span><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b> </b><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>Best regards, David<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_adobe-2Dconnect-2Dwhat-2Dnext&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=UHqgHAAbiJp4NHOIUqHcg1Y57R0_ZBkAKlNnZW-FMt4&s=lFkfL9p571e1ygGDpMHtzFBnK57qJfDmiC0yWwyGwII&e=" style="color: purple; text-decoration: underline;"><span>https://www.icann.org/news/blog/adobe-connect-what-next[icann.org]</span><span></span></a><span><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b>ADOBE CONNECT – WHAT NEXT?</b><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to<span class="Apple-converted-space"> </span></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_issues-2Dwith-2Dadobe-2Dconnect-2Dat-2Dicann61&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=UHqgHAAbiJp4NHOIUqHcg1Y57R0_ZBkAKlNnZW-FMt4&s=iO8NyGh9T2oO7mc2eo1jcmmpFO-uSsIlTLqKsypb0qM&e=" style="color: purple; text-decoration: underline;"><span>reported issues[icann.org]</span><span></span></a><span><span class="Apple-converted-space"> </span>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:<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b> </b><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b>The Forensics Investigation</b><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>With 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.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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:<o:p></o:p></span></div><ol start="1" type="1" style="margin-bottom: 0in; margin-top: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or<o:p></o:p></span></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited.<o:p></o:p></span></li></ol><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b> </b><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><b>Community Feedback and Next Steps</b><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>For 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.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>Accordingly, we would like to propose the following plan to the broader community for consideration:<o:p></o:p></span></div><ol start="1" type="1" style="margin-bottom: 0in; margin-top: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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.<o:p></o:p></span></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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.<o:p></o:p></span></li></ol><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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:<span class="Apple-converted-space"> </span></span><a href="mailto:RP-tool@icann.org" style="color: purple; text-decoration: underline;"><span>RP-tool@icann.org</span><span></span></a><span><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>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.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span>I look forward to your comments!<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div><div><div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 12pt;"> </span><o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 9pt;">David A. Olive<br>Senior Vice President</span><o:p></o:p></span></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span><span style="font-size: 9pt;">Policy Development Support</span></span><span><span style="font-size: 9pt; font-family: PMingLiU, serif;"><br></span></span><span><span style="font-size: 9pt;">Internet Corporation for Assigned Names and Numbers (ICANN)</span><o:p></o:p></span></p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span> <o:p></o:p></span></div></div></div></blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>SOAC-Leaders-ICANNMeeting-Planning mailing list</span><br><span><a href="mailto:SOAC-Leaders-ICANNMeeting-Planning@icann.org" style="color: purple; text-decoration: underline;">SOAC-Leaders-ICANNMeeting-Planning@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning</a></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>Gnso-igo-ingo-crp mailing list</span><br><span><a href="mailto:Gnso-igo-ingo-crp@icann.org" style="color: purple; text-decoration: underline;">Gnso-igo-ingo-crp@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp</a></span></blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>gnso-rpm-wg mailing list</span><br><span><a href="mailto:gnso-rpm-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rpm-wg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a></span></blockquote><blockquote type="cite"><span>_______________________________________________</span><br><span>Ccwg-auctionproceeds mailing list</span><br><span><a href="mailto:Ccwg-auctionproceeds@icann.org" style="color: purple; text-decoration: underline;">Ccwg-auctionproceeds@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</a></span></blockquote>_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org" style="color: purple; text-decoration: underline;">ALAC@atlarge-lists.icann.org</a><br><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" style="color: purple; text-decoration: underline;">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>At-Large Online:<span class="Apple-converted-space"> </span><a href="http://www.atlarge.icann.org/" style="color: purple; text-decoration: underline;">http://www.atlarge.icann.org</a><br>ALAC Working Wiki:<span class="Apple-converted-space"> </span><a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" style="color: purple; text-decoration: underline;">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></div></blockquote></div><br></div></body></html>