Skip to main content
P
Paul_welbroek
Participating Frequently
July 7, 2020
Question

Question about looking up the right protocol and launching the corect app

  • July 7, 2020
  • 3 replies
  • 1212 views

Hello, by the end of 2019 there was an issue about opening a pdf-file in Chrome, and in that pdf-file, there was a link to an other protocol (ibmscp), that would not open. It turned out to a blanc page. Here below i will past the info from Google. Anyway, the issue is fixed, i asume in a later version of Acrobat reader..?
Can anyone confirm this, and let me know in what version this issue is fixed?

Many thanx an regards, Paul.

Chrome ignores customer protocols passed in via command line ( referes to ibmscp protocol) . This was reported as a bug to google but their response is that it is a safety feature. From the google problem report: https://bugs.chromium.org/p/chromium/issues/detail?id=259881
 
 
The current behaviour is intentional. Allowing arbitrary protocols from the command line is extremely dangerous. It exposes every registered handler to various bouncing and tunnelling attacks. (The fix for issue 9862 actually blocked a protocol bouncing attack that was later reported against stable.)
 
The bug here is in Acrobat Reader, which should be looking up the correct protocol and launching the correct app as a handler. That is the only safe thing to do, because only the app initiating the handler has the context to make an accurate security decision. Adobe has disabled all custom protocols as a security measure 
This topic has been closed for replies.

3 replies

P
Paul_welbroekAuthor
Participating Frequently
July 9, 2020

anyone..?

T
Test Screen Name
Legend
July 9, 2020

I think you've so thoroughly confused us all, nobody will now dare to try to answer.

    P
    Paul_welbroekAuthor
    Participating Frequently
    July 9, 2020

    I am truly sorry.  But i am not aware why it seems to be so hard to answer my question...

    There was an issue, it is fixed, i just want to know how. There must be something...

    JR Boulay
    Community Expert
    JR BoulayCommunity Expert
    Community Expert
    July 7, 2020

    Chrome is not a PDF viewer, nor a PDF editor.

    You should use Acrobat Reader instead.

    Acrobate du PDF, InDesigner et Photoshopographe
    P
    Paul_welbroekAuthor
    Participating Frequently
    July 7, 2020

    Hi, i open the pdf file in Acrobat reader.

    Bernd Alheit
    Community Expert
    Bernd AlheitCommunity Expert
    Community Expert
    July 7, 2020

    Google Chrome doesn't use Acrobat Reader.

    P
    Paul_welbroekAuthor
    Participating Frequently
    July 7, 2020

    Hello Bernd,

    maybee i am not clear...
    We use HCL connections, if you open a connections community in Chrome, and in the community there is a pdf file, within the pdf-file there is a link to an other file wich should be opend with (like) ibmscp, then nothing happend. Or a blanc tab is opend.

    P
    Paul_welbroekAuthor
    Participating Frequently
    July 7, 2020

    No, I think you're clear, but you are wrong in your conclusions that Acrobat Reader is involved. You quoted an entirely correct bug report for Google Chrome, then asserted the problem wasn't in Google Chrome at all.


    And also this:

    The bug here is in Acrobat Reader, which should be looking up the correct protocol and launching the correct app as a handler. That is the only safe thing to do, because only the app initiating the handler has the context to make an accurate security decision. Adobe has disabled all custom protocols as a security measure .

    Don't get me wrong, it is working fine now, for the administration i want to know how this is fixed.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices