[technology taskforce] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203

[Dev Anand Teelucksingh]

The hyperlink in webpages (and emails) is the cornerstone of how the web
worked. There could be url links to files that are very long and designed
that way on purpose.

For example
https://community.icann.org.xyz/display/atlarge/2020-01-27+At-Large+Technology+Task+Force+Call?preview=/126420432/126422910/atlarge-technology-taskforce-27jan20-en.pdf

Consider links to google docs, Dropbox where the design is to create long
urls to files.

I doubt many persons would retype such long urls especially if it’s coming
from someone they trust

Dev Anand


On Sat, 8 Feb 2020 at 5:53 AM, Judith Hellerstein <judith at jhellerstein.com>
wrote:

> All,
> The problem here is that they are clicking on the link which they should
> never do. They should go to their bank’s website and login from there.  It
> is just training and educating people on the right thing to do
>
> Judith
>
> Sent from my iPad
> judith at jhellerstein.com
> Skype ID:JudithHellerstein
>
> On Feb 8, 2020, at 5:53 AM, Dev Anand Teelucksingh <devtee at gmail.com>
> wrote:
>
> 
>
> A large problem is when bad persons obscure the domains of companies in
> phishing campaigns so that persons go to the bad persons' website on
> another domain and steal their credentials or get malware installed.
>
> So say you get an email link from a trusted person whose been hacked
> saying - "hey we're not sure your paycheck was delivered to mybankinfo. Can
> you login to mybankinfo.com.paymentlogin.info and check?
> The challenge is that persons may just see "mybankinfo.com" and assume
> they are going to the mybankinfo.com site.
> And because they clicked on the link, how would the browser "know" what
> the site you really intended to go to?
>
> Dev Anand
>
> On Fri, Feb 7, 2020 at 3:04 PM Johan Helsingius <julf at julf.com> wrote:
>
>> On 07-02-2020 19:49, Dev Anand Teelucksingh wrote:
>> > Hmm....How would persons know what is the website they are viewing on
>> > without the URL?
>>
>> How many users check out the website info in URLs anyway? How will they
>> know that Mybankinfo.com is OK, but mybank.info isn't?
>>
>> Shouldn't it be the job of the browser to check if the web site is the
>> one you want to talk to (based on certificates)?
>>
>>         Julf
>>
>> _______________________________________________
>> ttf mailing list
>> ttf at 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.
>>
> _______________________________________________
> ttf mailing list
> ttf at 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ttf/attachments/20200208/9a19ea4d/attachment.html>