similar to: Feature Request: also report LocalPort in logs

http://bugzilla.mindrot.org/show_bug.cgi?id=413 Summary: Port forwarding: [localhost:]localport:remotehost:remoteport Product: Portable OpenSSH Version: older versions Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:

Hi! ---- I'm doing some testing with the ssh client OpenSSH on Windows 10 (10.0-19045) but due to firewall restrictions I need to run my experiments from a local port < 1024 (not negotiable). I thought that this was no problem... but ssh |bind()| fails with "address in use" (yes, I checked netstat, no one is there) for any port < 1023. Then I checked $ netstat # and $ netsh

I found that the documentation for -L and -R was hard to understand. So I made some changes to try to make it clearer. I started with Revision 1.328 from http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/ssh.1 Comments welcome. ================ ssh.1.patch ================ --- ssh.1 2012/09/15 16:08:48 1.1 +++ ssh.1 2012/09/15 20:23:35 @@ -51,13 +51,13 @@ .Op Fl F Ar configfile .Op Fl I

I've got a usecase right now where I've got to use a few intermediate ProxyJump hosts, and it would help debugging via -v tremendously if the debug lines would have a prefix of the originating host, so that they can be easily associated. The FQDN might be too long, though -- perhaps just the PID with an additional line associating it with the host would be a better fit? Thanks!

On Mon, 11 Sep 2023, Philipp Marek wrote: > I've got a usecase right now where I've got to use a few > intermediate ProxyJump hosts, and it would help debugging > via -v tremendously if the debug lines would have a prefix > of the originating host, so that they can be easily associated. > > The FQDN might be too long, though -- perhaps just the PID > with an

>> I've got a usecase right now where I've got to use a few >> intermediate ProxyJump hosts, and it would help debugging >> via -v tremendously if the debug lines would have a prefix >> of the originating host, so that they can be easily associated. >> >> The FQDN might be too long, though -- perhaps just the PID >> with an additional line

Hi, On 12/09/2023 07:43, Philipp Marek wrote: >>> I've got a usecase right now where I've got to use a few >>> intermediate ProxyJump hosts, and it would help debugging >>> via -v tremendously if the debug lines would have a prefix >>> of the originating host, so that they can be easily associated. >>> >>> The FQDN might be too long,

http://bugzilla.mindrot.org/show_bug.cgi?id=413 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjc at makalumedia.com ------- Additional Comments From markus at openbsd.org 2002-11-22 09:48 ------- *** Bug 441 has been marked as

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

Hello everybody, I'd like to get SSH provide some virtual server feature. Eg. when connecting to an existing server on a different port I'd like to chroot all users to some directory. This can currently be done by starting sshd twice, with different config files (or perhaps command line options); but getting that "right" for all circumstances (init.d, upstart, systemd,

http://bugzilla.mindrot.org/show_bug.cgi?id=413 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #229 is|0 |1 obsolete| | ------- Additional Comments From dtucker at zip.com.au 2003-06-04 21:37 -------

http://bugzilla.mindrot.org/show_bug.cgi?id=413 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mohit_aron at hotmail.com ------- Additional Comments From dtucker at zip.com.au 2004-06-06 12:12 ------- *** Bug 876 has been marked

I guess you might find fail2ban useful. It scans logfiles (like /var/log/sshd.log), and when it sees too many authentication failures from an IP address (or network range) it can issue commands to drop any further attempts via a firewall. By having it read its own logfile it's possible to have repeated offenders be cut out for longer and longer time spans.

Greetings, I want to create a set of rules that will be in affect when I connection originates from outside of my local lan (internet) and on a specific port, this is what I've wrote: Match LocalPort 11111, Address *,!10.0.0.0/24 but when I start ssh, I get this error: Invalid LocalPort '11111,' on Match line /etc/ssh/sshd_config line 176: Bad Match condition why is that? how can I

On 22/11/18 10:09 pm, Philipp Marek wrote: > if it happens that your local terminal emulation is not available > on the remote machine(s), what would be the right place to fix it? Is it a trick question?? Isn't the remote machine the only place that you can fix ?? Setting TERM on the local machine won't magically make a Wyse 60 understand VT220 control codes. Why not wrap ssh

OpenSSH 6.1 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches,

OpenSSH 6.1 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches,

Without an assigned source port, Transmit function assign a random new source port to the packet being sent. It thus have to be set before calling Transmit if the source port have already been decided. Conversly, we have to save the assigned port to reuse it later if needed. Resolve bug #35. Signed-off-by: Celelibi <celelibi at gmail.com> --- efi/udp.c | 18 ++++++++++++++++++ 1 file

I tried running qemu-system-x86_64 -help" command manually. But it seems that it work normally. Here is the output. Kindly guide me. spanhal1@seclab2:/usr/bin$ qemu-system-x86_64 -help QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard usage: qemu-system-x86_64 [options] [disk_image] 'disk_image' is a raw hard disk image for IDE hard disk 0

On Sat, Jan 6, 2018 at 5:38 PM, Philipp Marek <philipp at marek.priv.at> wrote: > I think we are possibly interested in switching to DIRECT IO (given that it >> bypasses any caching system including page cache) when reading *.PEM file >> > Sorry, but this makes no sense. > The data could just as well be read from the SSH process > memory space. > I think