- ttf - lists.iana.org

Re: [technology taskforce] [At-Large] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203
by Hadia Abdelsalam Mokhtar EL miniawi Feb. 12, 2020

Feb. 12, 2020

He is suggesting a way through which non-technical users can identify easily the eTLD+1 and thus maybe not tricked by bad actors. Hadia From: At-Large [mailto:at-large-bounces@atlarge-lists.icann.org] On Behalf Of Carlton Samuels Sent: Tuesday, February 11, 2020 8:07 PM To: Dev Anand Teelucksingh Cc: Technology Taskforce WG; At-Large Worldwide Subject: Re: [At-Large] [technology taskforce] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203 I viewed the video and my takeaway was that browsers can be configured for a role in building confidence in domain names. Very good discussion guys. CAS On Mon, 10 Feb 2020, 10:08 pm Dev Anand Teelucksingh, <devtee(a)gmail.com<mailto:devtee@gmail.com>> wrote: Dr. Alejandro Pisanty Baruch <apisan(a)unam.mx<mailto:apisan@unam.mx>> wrote: "is this just one more iteration of "domain names will cease to be relevant soon" or is it a move or trend that will definitely undermine their importance and therefore also change the markets?" I think no, this is not an iteration about domain names becoming irrelevant. The discussion focused on how to ensure browser users can identify what domain they are visiting so IMO, it strengthens the use of domain names by having users trust the domain they are visiting. The challenge as I see it is with the prevalence of many new TLDs, the risk of phishing and malware attacks are higher where bad persons try to trick persons to either: - go to bad persons' website(s) at domains pretending to be another organisation/service in order to get user login credentials to such organisations/services or - open links to malware files and become infected. So typically, bad persons would use typos that look similiar to the legitimate domain or add a few characters before or after the 2nd level domain So for example.com<http://example.com>, there could be exannple.com<http://exannple.com> , examp1e.com<http://examp1e.com>, eexamples.com<http://eexamples.com> and examples.com<http://examples.com> . With more TLDs and wider use of ccTLDs, bad persons could also do things like examples.xyz<http://examples.xyz>, examp1e.tv<http://examp1e.tv> and so on. With longer URLs, one can mask the legitimate domain as a third or fourth level subdomain of a bad persons' domain. Very long URLs like this are more difficult to parse and read on a mobile phone. Content Management Systems for websites over the years unfortunately generate long URLs that do work to direct persons to websites but are obscure for persons to parse. So an example of a bad URL : https://community.icann.org.can.work/display/atlarge/2020-01-27+At-Large+Te… Persons glancing at this URL would see icann.org<http://icann.org> and may think everything is fine and go ahead and click on the URL when its not. Nearly all browser vendors are using the Public Suffix List at https://publicsuffix.org/ which started as a Mozilla Initiative. From the Public Suffix List website, a "public suffix" is one under which Internet users can (or historically could) directly register names. Tracking this is important to ensure that a website can't set cookies that other websites can read or modify under the same domain. What the episode showed was that Mozilla Firefox (at least on the desktop) highlights the part of the domain that is the public suffix by making it slightly bolder than the rest of the URL. It is however to me, very, very subtle and I wish that Mozilla (and other browsers) make the public suffix part more bold or even a slightly bigger font size to alert users as to the true domain being viewed. Some mobile browsers are showing only the domain and not the rest of the URL and allow for the full URL can be viewed and edited when you tap on the URL bar which also helps. Kind Regards, Dev Anand Teelucksingh On Sun, Feb 9, 2020 at 3:23 PM Dr. Alejandro Pisanty Baruch <apisan(a)unam.mx<mailto:apisan@unam.mx>> wrote: Dev, thanks a lot for sending this. While at first it may seem off-topic, it cuts deeply into very relevant questions for us: is this just one more iteration of "domain names will cease to be relevant soon" or is it a move or trend that will definitely undermine their importance and therefore also change the markets? If it proceeds, what balances of power will appear that we don't face now? One example: will the companies that operate search or that provide browsers (or both!) earn new powers? This is already being discussed elsewhere. What are the views that are relevant for ICANN Internet users At Large, and other stakeholders? Yours, Alejandro Pisanty - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico +52-1-5541444475 FROM ABROAD +525541444475 DESDE MÉXICO SMS +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---->> Unete a ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . ________________________________ Desde: At-Large [at-large-bounces(a)atlarge-lists.icann.org<mailto:at-large-bounces@atlarge-lists.icann.org>] en nombre de Dev Anand Teelucksingh [devtee(a)gmail.com<mailto:devtee@gmail.com>] Enviado el: viernes, 07 de febrero de 2020 11:21 Hasta: At-Large Worldwide Asunto: [At-Large] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203 "In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. What are browsers doing today to overcome that? And, is there a better way" Watch the 20 min episode : https://youtu.be/0-wB1VY3Nrc Dev Anand _______________________________________________ ttf mailing list ttf(a)atlarge-lists.icann.org<mailto:ttf@atlarge-lists.icann.org> https://mm.icann.org/mailman/listinfo/ttf _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Public Comment new features - testing now!
by Olivier MJ Crépin-Leblond Feb. 10, 2020

Feb. 10, 2020

Hello all, I'm just off a call with the good folks at Information Transparency Initiative (ITI) and they took us through the new Public Comment features Beta site. This was announced by David Olive on Friday: https://www.icann.org/news/blog/improving-the-public-comment-feature-an-inf… I would therefore invite you to test out all the features of the new Public Comment Site. Go to: https://feedback.icann.org/ and follow the link to "Public Comment" which will take you to a test environment where you'll be able to play with the features and submit test comments etc. Kindest regards, Olivier

1 0

Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203
by Dev Anand Teelucksingh Feb. 8, 2020

Feb. 8, 2020

"In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. What are browsers doing today to overcome that? And, is there a better way" Watch the 20 min episode : https://youtu.be/0-wB1VY3Nrc Dev Anand

4 11

STARTING in 15 mins / Meeting invitation: At-Large Technology Taskforce Call on Monday, 27 January 2020 at 16:00 UTC
by ICANN At-Large Staff Jan. 27, 2020

Jan. 27, 2020

**If you require a dial-out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number.** Dear All, The next At-Large Technology Taskforce Call is scheduled for Monday, 27 January 2020 at 16:00 UTC for 60 mins. For other times: https://tinyurl.com/uclhnjk The agenda and call details can be found at: https://community.icann.org/x/0AWJBw Zoom Room: https://icann.zoom.us/j/894944547 Meeting ID: 894-944-547 ADIGO Conference Bridge: EN: 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann Main Wiki Space: https://community.icann.org/x/FpfbAQ If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

REMINDER / Meeting invitation: At-Large Technology Taskforce Call on Monday, 27 January 2020 at 16:00 UTC
by ICANN At-Large Staff Jan. 27, 2020

Jan. 27, 2020

**If you require a dial-out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number.** Dear All, The next At-Large Technology Taskforce Call is scheduled for Monday, 27 January 2020 at 16:00 UTC for 60 mins. For other times: https://tinyurl.com/uclhnjk The agenda and call details can be found at: https://community.icann.org/x/0AWJBw Zoom Room: https://icann.zoom.us/j/894944547 Meeting ID: 894-944-547 ADIGO Conference Bridge: EN: 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann Main Wiki Space: https://community.icann.org/x/FpfbAQ If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Krebs on Security : Does Your Domain Have a Registry Lock?
by Dev Anand Teelucksingh Jan. 24, 2020

Jan. 24, 2020

Fascinating read from Krebs on Security on the perils of loosing your domain name even with registrar lock and how a registry lock would have helped - Dev Anand "On December 23, 2019, unknown attackers began contacting customer support people at OpenProvider <https://openprovider.com/>, a popular domain name registrar based in The Netherlands. The scammers told the customer representatives they had just purchased from the original owner the domain *e-hawk.net <http://e-hawk.net>* — which is part of a service that helps Web sites detect and block fraud — and that they were having trouble transferring the domain from OpenProvider to a different registrar. The real owner of e-hawk.net is *Raymond Dijkxhoorn*, a security expert and entrepreneur who has spent much of his career making life harder for cybercrooks and spammers. Dijkxhoorn and E-HAWK’s *CEO Peter Cholnoky* had already protected their domain with a “*registrar lock*,” a service that requires the registrar to confirm any requested changes with the domain owner via whatever communications method is specified by the registrant. In the case of e-hawk.net, however, the scammers managed to trick an OpenProvider customer service rep into transferring the domain to another registrar with a fairly lame social engineering ruse — and without triggering any verification to the real owners of the domain." https://krebsonsecurity.com/2020/01/does-your-domain-have-a-registry-lock/

1 0

At-Large Technology Taskforce Call
by ICANN Policy Calendar Jan. 14, 2020

Jan. 14, 2020

Dear All, The next At-Large Technology Taskforce Call is scheduled for Monday, 27 January 2020 at 16:00 UTC for 60 mins. For other times: https://tinyurl.com/uclhnjk The agenda and call details can be found at: https://community.icann.org/x/0AWJBw Zoom Room: https://icann.zoom.us/j/894944547 Meeting ID: 894-944-547 ADIGO Conference Bridge: EN: 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann Main Wiki Space: https://community.icann.org/x/FpfbAQ If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 1

Meeting invitation: At-Large Technology Taskforce Call on Monday, 27 January 2020 at 16:00 UTC
by ICANN At-Large Staff Jan. 13, 2020

Jan. 13, 2020

**If you require a dial-out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number.** Dear All, The next At-Large Technology Taskforce Call is scheduled for Monday, 27 January 2020 at 16:00 UTC for 60 mins. For other times: https://tinyurl.com/uclhnjk The agenda and call details can be found at: https://community.icann.org/x/0AWJBw Zoom Room: https://icann.zoom.us/j/894944547 Meeting ID: 894-944-547 ADIGO Conference Bridge: EN: 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann Main Wiki Space: https://community.icann.org/x/FpfbAQ If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

At-Large Technology Taskforce Call
by ICANN Policy Calendar Jan. 13, 2020

Jan. 13, 2020

**If you require a dial-out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number.** Dear All, The next At-Large Technology Taskforce Call is scheduled for Monday, 27 January 2020 at 16:00 UTC for 60 mins. For other times: https://tinyurl.com/uclhnjk The agenda and call details can be found at: https://community.icann.org/x/0AWJBw Zoom Room: https://icann.zoom.us/j/894944547 Meeting ID: 894-944-547 ADIGO Conference Bridge: EN: 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann Main Wiki Space: https://community.icann.org/x/FpfbAQ If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Internet2 app features
by Seun Ojedeji Dec. 10, 2019

Dec. 10, 2019

Hello, I am getting to use the internet2 app for the first time, and walking through its features, I remembered the ICANN meetings app. I think there may be some features/lessons to be modelled from the app towards improving that of the ICANN meetings app. https://meetings.internet2.edu/2019-technology-exchange/internet2-events-mo… Regards Sent from my mobile Kindly excuse brevity and typos

1 0