Re: Howto add a vnc URL handler to Icedove?
Scott Ferguson writes: > 1. while the link displays as show above, in the HTML (subset used in > email) it's actually a mailto link... > > 2. I've tried adding to Icedove about:config:- > ;a new string value of "network.protocol-handler.app.vnc" with the value > "$processingScript %U" > ;a new boolean value "network.protocol-handler.expose.vnc" with the > value "true" > > But I suspect they'll never be called as Icedove treats the link as "mailto" Well, what about changing how 'mailto' URIs are handled? You could specify that 'mailto' URIs should be handled by a script. That script can examine the URI and, if it begins with the scheme name 'vnc', does the setup you require, but would otherwise calls the default 'mailto' handler. Might that do what you need? (i've set up Iceweasel to call a script for 'mailto' links, so that i can click on them and have a template email message open in Emacs, which i can then edit and send.) Alexis. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/878ujpuhs1@gmail.com
Re: Howto add a vnc URL handler to Icedove?
On Saturday 01 November 2014 13:51:16 Jape Person wrote: > You (Scott) help a lot of people here. I wish someone would help you! Sadly, perhaps no-one knows the answer. :-( Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201411051455.44998.lisi.re...@gmail.com
Re: Howto add a vnc URL handler to Icedove?
On 10/29/2014 01:38 AM, Scott Ferguson wrote: I want to make things easier for people accepting remote desktop invitations from Krfb. Ideal scenario:- 1. Create a reverse ssh tunnel to "middle" (an internet accessible server) from the "users" computer. e.g. port 1234 to port 1235 "middle" has port forwarding enabled e.g. port 1234 to port 1236, and the reverse ssh tunnel creation is automated (KMenu entry for Krfb modified to call a script, that starts the reverse ssh tunnel before calling Krfb). 2. The "user" then sends an (encrypted) email invitation from Krfb[*1] to the "support" - and waits for support to connect (which then requires the "user" to allow "support" access). 3. "support" then opens the email in Icedove, clicks on the link[*2], Icedove uses a script to handle the link, which then processes[*3] the link before calling krdc (or tightvnc) - which then gives "support" remote access to the "users" desktop. Ideal outcome:- Quick and easy remote desktop support even when both the "user" and "support" are behind NAT firewalls. [*1] Krfb is set to use port 1235 [*2] e.g. vnc://invitation:cpcz-...@xxx.xxx.xxx.xxx: There /appears/ to be two problems which I'd like suggestions on how to solve:- 1. while the link displays as show above, in the HTML (subset used in email) it's actually a mailto link... 2. I've tried adding to Icedove about:config:- ;a new string value of "network.protocol-handler.app.vnc" with the value "$processingScript %U" ;a new boolean value "network.protocol-handler.expose.vnc" with the value "true" But I suspect they'll never be called as Icedove treats the link as "mailto" Google yields nothing, nor does the Mozilla developer documentation, and the same question has previously been posted to Mozilla forums, carefully described, by someone else - but has never received an answer. So I ask the question here, knowing that there are some informed list readers who might have useful suggestions. Kind regards No, don't get your hopes up. I ain't gonna be helpful. I'm just expressing my disappointment that no one has responded to this message. Information on how to do this would be very helpful to me. You (Scott) help a lot of people here. I wish someone would help you! (and me) ;-) Jape -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5454e554.30...@comcast.net
Howto add a vnc URL handler to Icedove?
I want to make things easier for people accepting remote desktop invitations from Krfb. Ideal scenario:- 1. Create a reverse ssh tunnel to "middle" (an internet accessible server) from the "users" computer. e.g. port 1234 to port 1235 "middle" has port forwarding enabled e.g. port 1234 to port 1236, and the reverse ssh tunnel creation is automated (KMenu entry for Krfb modified to call a script, that starts the reverse ssh tunnel before calling Krfb). 2. The "user" then sends an (encrypted) email invitation from Krfb[*1] to the "support" - and waits for support to connect (which then requires the "user" to allow "support" access). 3. "support" then opens the email in Icedove, clicks on the link[*2], Icedove uses a script to handle the link, which then processes[*3] the link before calling krdc (or tightvnc) - which then gives "support" remote access to the "users" desktop. Ideal outcome:- Quick and easy remote desktop support even when both the "user" and "support" are behind NAT firewalls. [*1] Krfb is set to use port 1235 [*2] e.g. vnc://invitation:cpcz-...@xxx.xxx.xxx.xxx: There /appears/ to be two problems which I'd like suggestions on how to solve:- 1. while the link displays as show above, in the HTML (subset used in email) it's actually a mailto link... 2. I've tried adding to Icedove about:config:- ;a new string value of "network.protocol-handler.app.vnc" with the value "$processingScript %U" ;a new boolean value "network.protocol-handler.expose.vnc" with the value "true" But I suspect they'll never be called as Icedove treats the link as "mailto" Google yields nothing, nor does the Mozilla developer documentation, and the same question has previously been posted to Mozilla forums, carefully described, by someone else - but has never received an answer. So I ask the question here, knowing that there are some informed list readers who might have useful suggestions. Kind regards -- “It ain’t what you don’t know that gets you into trouble. It’s what you know for sure that just ain’t so.” -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54507d62.9050...@gmail.com
