search for: remoteforwarded

Specifying a RemoteForward of 0:example.com:1234 dynamically allocates the listen port on the server, and then reports it to ... the client! Where it is practically useless. Was this someone's idea of a joke? Presumably not--there are some technical obstacles to reporting it to the remote process. I'd like to help solve that problem. The natural way to me would be to extend the syntax

Hello, we have a server that appliances "in the field" SSH into with a config including: > RemoteForward 127.0.0.1:0 127.0.0.1:22 > RemoteForward 0 127.0.0.1:443 so that our support desk can then use these forwards to access SSH and HTTPS on them. Note that the remote endpoint of one is limited to IPv4, while the other defaults to v4+v6;

https://bugzilla.mindrot.org/show_bug.cgi?id=3609 Bug ID: 3609 Summary: Support the special ${RANDOM} environment variable Product: Portable OpenSSH Version: 9.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs

On Tue, 9 Jul 2024, Jochen Bern wrote: > allocated" the *same* port, one for SSH, one for HTTPS: No, it?s not the same port, it?s a different (address, port) tuple. > Is there anything I can do to prevent a port number being double assigned like > this? Use IPv4+IPv6 bindings for both? bye, //mirabilos -- 15:41?<Lo-lan-do:#fusionforge> Somebody write a testsuite for

Hi, I've just upgraded to openssh-4.7p1 on my gentoo box, and I've noticed a incompatibility with openssh-3.6.1p2 running on a redhat AS3 server. If I ssh from my openssh-4.7_p1 client to the openssh-3.6.1p2 server, and RemoteForward a port, the ssh connection closes if I try to send more than roughly 300K through the tunneled port. The problem isn't present when I use openssh-4.6p1

Hi, I've just upgraded to openssh-4.7p1 on my gentoo box, and I've noticed a incompatibility with openssh-3.6.1p2 running on a redhat AS3 server. If I ssh from my openssh-4.7_p1 client to the openssh-3.6.1p2 server, and RemoteForward a port, the ssh connection closes if I try to send more than roughly 300K through the tunneled port. The problem isn't present when I use openssh-4.6p1

http://bugzilla.mindrot.org/show_bug.cgi?id=1000 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #5 from dtucker at zip.com.au 2006-10-07 11:39 ------- Change all RESOLVED bug to CLOSED with the exception

https://bugzilla.mindrot.org/show_bug.cgi?id=3140 Bug ID: 3140 Summary: support a token for XDG_RUNTIME_DIR Product: Portable OpenSSH Version: 8.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

...ry before the agent forwarding connection but they are workarounds and I'd like to have this working smoothly. The gpg-agent forwarding is an awesome feature for us. ( I documented it under https://wiki.gnupg.org/AgentForwarding ) In my opinion OpenSSH should create the parent directories of RemoteForwarded files if possible. Maybe as a configuration option? Do you agree? Or do you think that some other software component in this setup is behaving wrongly? Regards, Andre -- Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Os...

https://bugzilla.mindrot.org/show_bug.cgi?id=3648 Bug ID: 3648 Summary: ssh client blocks itself by leaving unix domain socket alive after user Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh

The build bug: DESTDIR=$SOMEDIR does not work: mkdir ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/etc ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/sbin/sshd -t -f ${HOME}/tools/openssh/openssh-5.0p1/_i/usr/local/etc/sshd_config Could not load host key: /usr/local/etc/ssh_host_rsa_key Could not load host key: /usr/local/etc/ssh_host_dsa_key Disabling protocol version 2. Could not load

FINALLY, it's here. You can now tell SSH which address to bind to for every single port forwarding option! This patch allows you to pass the following as ssh command line options: ssh -L 192.168.1.55:1234:localhost:80 -R ::11:22:aa:bb/80/localhost/80 etc. Or as normal config file options: LocalForward ::11:22:33/1234 localhost/80 RemoteForward 1.2.3.4:80 localhost:80 It will also

https://bugzilla.mindrot.org/show_bug.cgi?id=2677 Bug ID: 2677 Summary: Provide a way to set an environment variable from ssh_config Product: Portable OpenSSH Version: 7.4p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh

http://bugzilla.mindrot.org/show_bug.cgi?id=413 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From markus at openbsd.org 2003-02-03 19:50 ------- i'll look into this. ------- You are

On 11/12/20 7:50 AM, Jonathan Billings wrote: > On Thu, Nov 12, 2020 at 12:56:15PM +0000, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: >> If the point is to access a specific web site only the remote >> machine can get to, you can also do it with port forwarding: >> ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine >> and

https://bugzilla.mindrot.org/show_bug.cgi?id=3133 Bug ID: 3133 Summary: Dynamically Assigned Ports for DynamicForward and LocalForward Product: Portable OpenSSH Version: 8.2p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh

On Thu, Nov 12, 2020 at 10:02:57AM -0700, S Bob wrote: > On 11/12/20 7:50 AM, Jonathan Billings wrote: > > If this is actually something you want to do with regularity, I > > suggest using the SSH SOCKS proxy (with the DynamicForward port), and > > configure Firefox to use the localhost:port as a SOCKS5 proxy. Then > > all traffic in firefox will be routed over the ssh

Hi, I posted this question to the OpenBSD bugs list last week, however I have had no reply and it was suggested on IRC that I post here instead. So I must apologise if this is not appropriate. For a reference here is my previous post: https://marc.info/?l=openbsd-bugs&m=156080681530337&w=2 I am running OpenBSD 6.5-stable (also tested on -current). When I ssh somewhere I get a sig abort

https://bugzilla.mindrot.org/show_bug.cgi?id=3017 Bug ID: 3017 Summary: ExitOnForwardFailure=yes doesn't work for local forwards (-L) Product: Portable OpenSSH Version: 7.6p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh

If the point is to access a specific web site only the remote machine can get to, you can also do it with port forwarding: ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine and then locally run any browser, and access https://localhost:443 (assuming it's https. If it's plain http, use "http" and 80). Note that you'll be breaking some aspects of https