--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/6bb134a0-ef4e-400f-a19d-48fb5cd00a07%40chromium.org.
currently, that's not supported. we plan on adding support for it, but don't have a schedule for it atm. you can star https://crbug.com/217785 for updates.btw, we support ssh:// URIs now:
On Tue, May 28, 2019 at 11:55 PM Palacios Family <palac...@gmail.com> wrote:
I have a scripted a dynamic webpage that generates URLs from an IP database that when clicked will open an SSH session using the SSH Extension. This works well for the equipment with the most current release of the OS. However I have legacy OS equipment where the URL fails:
chrome-extension://iodihamcpbpeioajjeobimgagajmlibd/html/nassh.html#MyUsername@10.255.255.218:22
"Unable to negotiate with UNKNOWN port -1: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 NaCl plugin exited with status code 255. "If I use the console interface of the SSH Extension and add the following to the SSH Arguments it works: -c aes128-cbc -oHostKeyAlgorithms=+ssh-dss -oKexAlgorithms=+diffie-hellman-group1-sha1I realize upgrading the OS and modifying the equipment configs is the best method. However due to various internal circumstances this is not possible.How can I have these arguments passed using the URL method?Thanks for your help!
--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromiu...@chromium.org.
Thank you for your quick reply. Are you saying ssh://URI is replacing the chrome-extension://URL ?
Thanks again!
On Tuesday, May 28, 2019 at 2:46:03 PM UTC-4, Mike Frysinger wrote:
currently, that's not supported. we plan on adding support for it, but don't have a schedule for it atm. you can star https://crbug.com/217785 for updates.btw, we support ssh:// URIs now:
On Tue, May 28, 2019 at 11:55 PM Palacios Family <palac...@gmail.com> wrote:
I have a scripted a dynamic webpage that generates URLs from an IP database that when clicked will open an SSH session using the SSH Extension. This works well for the equipment with the most current release of the OS. However I have legacy OS equipment where the URL fails:
chrome-extension://iodihamcpbpeioajjeobimgagajmlibd/html/nassh.html#MyUse...@10.255.255.218:22
"Unable to negotiate with UNKNOWN port -1: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 NaCl plugin exited with status code 255. "If I use the console interface of the SSH Extension and add the following to the SSH Arguments it works: -c aes128-cbc -oHostKeyAlgorithms=+ssh-dss -oKexAlgorithms=+diffie-hellman-group1-sha1I realize upgrading the OS and modifying the equipment configs is the best method. However due to various internal circumstances this is not possible.How can I have these arguments passed using the URL method?Thanks for your help!
--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromiu...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/6bb134a0-ef4e-400f-a19d-48fb5cd00a07%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/1dbab974-406f-48aa-a93a-889eacdd7da5%40chromium.org.
I have a scripted a dynamic webpage that generates URLs from an IP database that when clicked will open an SSH session using the SSH Extension. This works well for the equipment with the most current release of the OS. However I have legacy OS equipment where the URL fails:
chrome-extension://iodihamcpbpeioajjeobimgagajmlibd/html/nassh.html#MyUsername@10.255.255.218:22