Fwd: [Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan
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@jhellerstein.com Skype ID:JudithHellerstein Begin forwarded message:
From: Nathalie Peregrine <nathalie.peregrine@icann.org> Date: April 20, 2018 at 2:16:27 PM EDT To: "ccwg-auctionproceeds@icann.org" <ccwg-auctionproceeds@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@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 to reported 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 Investigation 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. 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 Steps 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. 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@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 President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)
_______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning@icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning _______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp _______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg _______________________________________________ Ccwg-auctionproceeds mailing list Ccwg-auctionproceeds@icann.org https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
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@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@jhellerstein.com Skype ID:JudithHellerstein
Begin forwarded message:
*From:* Nathalie Peregrine <nathalie.peregrine@icann.org> *Date:* April 20, 2018 at 2:16:27 PM EDT *To:* "ccwg-auctionproceeds@icann.org" <ccwg-auctionproceeds@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@icann.org* <RP-tool@icann.org>
Best regards, David
https://www.icann.org/news/blog/adobe-connect-what-next[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog...>
*ADOBE CONNECT – WHAT NEXT?*
As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to reported issues[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog...> 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 Investigation*
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.
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:
1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. 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 Steps*
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.
Accordingly, we would like to propose the following plan to the broader community for consideration:
1. 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. 2. 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@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 President
Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)
_______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning@icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning
_______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp
_______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg
_______________________________________________ Ccwg-auctionproceeds mailing list Ccwg-auctionproceeds@icann.org https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
_______________________________________________ ALAC mailing list ALAC@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 @evanleibovitch or @el56
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 Holly On 21 Apr 2018, at 4:20 am, Judith Hellerstein <judith@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@jhellerstein.com Skype ID:JudithHellerstein
Begin forwarded message:
From: Nathalie Peregrine <nathalie.peregrine@icann.org> Date: April 20, 2018 at 2:16:27 PM EDT To: "ccwg-auctionproceeds@icann.org" <ccwg-auctionproceeds@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@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 to reported 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 Investigation 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. 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 Steps 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. 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@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 President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)
_______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning@icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning _______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp _______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg _______________________________________________ Ccwg-auctionproceeds mailing list Ccwg-auctionproceeds@icann.org https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
ALAC mailing list ALAC@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+(ALA...)
I totally agree. My experience with webex and zoom have not been great. There have been audio problems requiring use of both phone and computer interface (to see the slides) -- which causes all kinds of extra work for staff and chairs and sometimes feels like enhanced teleconferencing for the participants. Neither platform is very intuitive and people, myself included, seem to have trouble figuring how to do basic things like mute/unmute, raise hand, etc. So I would be very happy to see a return to Adobe as our basic platform although I don't know whether "hardened" Adobe will look a bit different. My hat is off to staff and meeting chairs who have been struggling with this change. Marita Moll On 4/21/2018 6:47 AM, Holly Raiche wrote:
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
Holly On 21 Apr 2018, at 4:20 am, Judith Hellerstein <judith@jhellerstein.com <mailto:judith@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@jhellerstein.com <mailto:judith@jhellerstein.com> Skype ID:JudithHellerstein
Begin forwarded message:
*From:*Nathalie Peregrine <nathalie.peregrine@icann.org <mailto:nathalie.peregrine@icann.org>> *Date:*April 20, 2018 at 2:16:27 PM EDT *To:*"ccwg-auctionproceeds@icann.org <mailto:ccwg-auctionproceeds@icann.org>" <ccwg-auctionproceeds@icann.org <mailto:ccwg-auctionproceeds@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@icann.org*<mailto:RP-tool@icann.org> ** Best regards, David https://www.icann.org/news/blog/adobe-connect-what-next[icann.org]<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=> *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]<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=>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 Investigation* 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. 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:
1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. 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 Steps* 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. Accordingly, we would like to propose the following plan to the broader community for consideration:
1. 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. 2. 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@icann.org<mailto:RP-tool@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 President
Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)
_______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning@icann.org <mailto:SOAC-Leaders-ICANNMeeting-Planning@icann.org> https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning _______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org <mailto:Gnso-igo-ingo-crp@icann.org> https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp _______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org <mailto:gnso-rpm-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rpm-wg _______________________________________________ Ccwg-auctionproceeds mailing list Ccwg-auctionproceeds@icann.org <mailto:Ccwg-auctionproceeds@icann.org> https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online:http://www.atlarge.icann.org <http://www.atlarge.icann.org/> ALAC Working Wiki:https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
“I want my AdobeC!!!!” (shouted like “I want my MTV!!!”) Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Apr 21, 2018, at 10:16 AM, Marita Moll <mmoll@ca.inter.net> wrote:
I totally agree. My experience with webex and zoom have not been great. There have been audio problems requiring use of both phone and computer interface (to see the slides) -- which causes all kinds of extra work for staff and chairs and sometimes feels like enhanced teleconferencing for the participants. Neither platform is very intuitive and people, myself included, seem to have trouble figuring how to do basic things like mute/unmute, raise hand, etc.
So I would be very happy to see a return to Adobe as our basic platform although I don't know whether "hardened" Adobe will look a bit different.
My hat is off to staff and meeting chairs who have been struggling with this change.
Marita Moll
On 4/21/2018 6:47 AM, Holly Raiche wrote: 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
Holly
On 21 Apr 2018, at 4:20 am, Judith Hellerstein <judith@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@jhellerstein.com Skype ID:JudithHellerstein
Begin forwarded message:
From: Nathalie Peregrine <nathalie.peregrine@icann.org> Date: April 20, 2018 at 2:16:27 PM EDT To: "ccwg-auctionproceeds@icann.org" <ccwg-auctionproceeds@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@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 to reported 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 Investigation 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. 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 Steps 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. 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@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 President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)
_______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning@icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning _______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp _______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg _______________________________________________ Ccwg-auctionproceeds mailing list Ccwg-auctionproceeds@icann.org https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
ALAC mailing list ALAC@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+(ALA...)
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
Dear Marita, On 21/04/2018 16:16, Marita Moll wrote:
So I would be very happy to see a return to Adobe as our basic platform although I don't know whether "hardened" Adobe will look a bit different.
Spot on. The big question is whether a "hardened" Adobe Connect will work the same way as the "old" Adobe Connect, especially across platforms and networks with differing quality of service. Kindest regards, Olivier
Hi, I tried to use WebEx in China. However, I was not able to load the program because I am still using Windows XP. Although XP is not being supported by Microsoft anymore, but it is being supported by a domestic vendor and is still widely being used. Thus, using WebEx may block many participating from China. Kaili ----- Original Message ----- From: Holly Raiche To: Judith Hellerstein Cc: alac@atlarge-lists.icann.org ; ttf@atlarge-lists.icann.org ; na-discuss@atlarge-lists.icann.org Sent: Saturday, April 21, 2018 6:47 PM Subject: Re: [ALAC] Fwd: [Ccwg-auctionproceeds] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan 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 Holly On 21 Apr 2018, at 4:20 am, Judith Hellerstein <judith@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@jhellerstein.com Skype ID:JudithHellerstein Begin forwarded message: From: Nathalie Peregrine <nathalie.peregrine@icann.org> Date: April 20, 2018 at 2:16:27 PM EDT To: "ccwg-auctionproceeds@icann.org" <ccwg-auctionproceeds@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@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 to reported 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 Investigation 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. 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: 1.. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2.. 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 Steps 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. Accordingly, we would like to propose the following plan to the broader community for consideration: 1.. 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. 2.. 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@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 President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ SOAC-Leaders-ICANNMeeting-Planning mailing list SOAC-Leaders-ICANNMeeting-Planning@icann.org https://mm.icann.org/mailman/listinfo/soac-leaders-icannmeeting-planning _______________________________________________ Gnso-igo-ingo-crp mailing list Gnso-igo-ingo-crp@icann.org https://mm.icann.org/mailman/listinfo/gnso-igo-ingo-crp _______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg _______________________________________________ Ccwg-auctionproceeds mailing list Ccwg-auctionproceeds@icann.org https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds _______________________________________________ ALAC mailing list ALAC@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+(ALA...) ------------------------------------------------------------------------------ _______________________________________________ ALAC mailing list ALAC@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+(ALA...)
participants (7)
-
Evan Leibovitch -
Holly Raiche -
Javier Rua -
Judith Hellerstein -
Kan Kaili -
Marita Moll -
Olivier MJ Crépin-Leblond