similar to: openssh-4.7p1 & RemoteForward to openssh-3.6.1p2 Disconnecting: Bad packet length

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

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;

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

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

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=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

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

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

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

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

On Feb 28, 2005, at 19:16, Curt Cox wrote: > I'm interested in using LLVM to run source languages supported by GCC > (mostly just C and Fortran, actually) on a JVM. There seem to be two > general ways this could be accomplished. Here is a better way to do this. At least, I think it is better, mostly because someone else has already done all the work: http://www.xwt.org/mips2java/

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

Hi openssh dev's, I love an truly appreciate the Socket forwarding feature in OpenSSH 6.7. i use it for forwarding the socket of GnuPG's agent (that handles the secret stuff) to remote machines. Usecase: ====== I am a remote worker and use gnupg agent forwarding to connect to our company infrastructure that makes heavy use of PGP encryption while keeping my key out of the hands of

Hi, the attached patch implements adding and canceling of remote port forwardings by communicating with a running ssh client via a control socket. Thus, one can do this: ssh -MNfS ~/.ssh/ctl remotehost and then: ssh -S ~/.ssh/ctl -O add-rforward 2000:forward:80 localhost to add a new remote forwarding or ssh -S ~/.ssh/ctl -O cancel-rforward localhost:2000 localhost to remove it. The

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

http://bugzilla.mindrot.org/show_bug.cgi?id=993 Summary: adding and removing forwardings via the control connection Product: Portable OpenSSH Version: 4.0p1 Platform: All OS/Version: Linux Status: NEW Keywords: patch Severity: normal Priority: P2 Component: ssh

Hello, I have attached a small patch that enables OpenSSH 4.7p1 to use netgroups for users and hosts entries in the AllowUsers and DenyUsers configuration options in sshd_config. This has the following advantages: * hostnames or ip addresses don't have to be maintained in sshd_config, but you can use meaningful names for groups of users and groups of hosts. * large scale installations can

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=1389 Summary: Problem compiling openssh 4.7p1 Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: bitbucket at