similar to: Is there any way to hook the point when channel port listener accepts a new connection?

Displaying 20 results from an estimated 30000 matches similar to: "Is there any way to hook the point when channel port listener accepts a new connection?"

2012 May 10
2
Is there any method, with ChrootDirectory and internal-sftp, to automatically cd to a subdir on login?
Hi, This is either a query or a feature request. I have a system where sftp users are chrooted using scponly, which while requiring much more setup than OpenSSH's internal-sftp method, has the useful feature of allowing an initial chroot to a subdirectory, typically the one used for file exchange. I've searched for a way to do the same thing with OpenSSH. So far haven't found it. If
2009 Feb 25
2
Disabling specific port-forwarding
Hi all, I have a server where I allow some people to do SSH port forwarding for SVN, GIT, since I need to do that to access these services in certain locations. I can't access SVN ports in some work locations. Thing is, I also give specific access to some user accounts, mainly git and svn user, to some people I don't fully trust to have access to my VNC server, which is without password
2010 Jul 01
2
ssh server hangs the port even if client machine shuts down
Hi, I have the following problem with ssh, hope someone can help me with it: I have 2 processes of ssh server on same Linux machine. One of them is the normal ssh configuration for Linux, the other one starts with a custom configuration on another port. >From the client i do a remote port forwarding to the custom ssh server: ssh -R 1037:localhost:55555. After this command on ssh server
2023 Aug 06
1
Question on simultaneous IPv4 and IPv6 "any address" listening
Thanks to everyone for a fruitful discussion, links and ideas. The result is nearing a merge at https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI on any platform, including Windows (which behaves funny WRT binding to the same host:port as many times as you ask). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on
2023 Aug 06
1
Question on simultaneous IPv4 and IPv6 "any address" listening
Thanks to everyone for a fruitful discussion, links and ideas. The result is nearing a merge at https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI on any platform, including Windows (which behaves funny WRT binding to the same host:port as many times as you ask). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on
2006 May 23
4
Are there OpenSSH library coding examples
Hi- Apologies in advance if this is off-topic, but I've been unable to find any coding or usage examples on how to open a SSH client to a remote server. I'll happily RTFM if I can just find the FM (!). The client environment is x86 Linux 2.6.x, the remote SSH servers will be on proprietary embedded devices. My current application uses a socket interface and select() to communicate
2005 Aug 02
2
port forwarding trouble
Hi all, When I set up multiple tunnels from remote hosts to ports on localhost, I get the following error when I try to use them: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! (even though the keys haven't
2023 Apr 10
2
"Bad packet length 1231976033"
On Mon, 10 Apr 2023 at 07:07, Peter Stuge <peter at stuge.se> wrote: > > Brian Candler wrote: > > > What's odd is that the length is *always* 1231976033 (which is > > > 0x496E7661 or "Inva" in ASCII). One thing that can cause this is if the libc writes to stderr (ie fd 2) on some classes of error. This is something libc should probably not do, since
2011 Sep 08
1
Dynamic port remote listener - a BUG?
Hello, Today I tried using "dynamically assigned" port for remote listener, by requesting listener on port 0. This is supposed to create a listener on a port choosen by server. Everything seemed OK (the choosen port was sent back to client), but forwarding was refused. So I checked the source. in channels.c, function: channel_setup_fwd_listener /* *
2012 Feb 09
1
Restrict commands available in an SFTP session
Hello, i am using SFTP with CHROOT. I want to allow my users that they can upload and download with the sftp server, but they should never do an MKDIR! Is it possible to restrict commands and how can i do this? i only found material of modifing the source...and that is not the best way for me. regards Sonja Meyer sonne_meyer at yahoo.de
2004 Aug 06
2
could not create listener socket on port 8000
greetings! when i try to start the icecast server i get the following error: Could not create listener socket on port 8000 Server startup failed. Exiting. I did make sure that iptables has port 8000 open for tcp. Any suggestions for troubleshooting? Thanks. jg __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
2023 Oct 16
2
"Could not create listener socket on port" error only when using systemd service
Hi, I'm using icecast via Fedora 37 package and systemd service to start. I've added multiple <listen-socket> but get: "EROR connection/connection_setup_sockets Could not create listener socket on port xxx" Nothing listens on the ports in question, I verified via nc(1) and manually starting icecast via "/usr/bin/icecast -c /etc/icecast.xml" I can't
2004 Aug 06
2
could not create listener socket on port 8000
Remco B. Brink wrote: ><quote who="jensen galan"> > > > >>greetings! >> >>when i try to start the icecast server i get the >>following error: >> >>Could not create listener socket on port 8000 >>Server startup failed. Exiting. >> >>I did make sure that iptables has port 8000 open for >>tcp. >>
2023 Oct 17
1
"Could not create listener socket on port" error only when using systemd service
V?Mon, Oct 16, 2023 at 12:34:42PM -0700,?Jordan Erickson napsal(a): > On 10/16/23 10:37, Michael C Cambria wrote: > > I'm using icecast via Fedora 37 package and systemd service to start. > > > > I've added multiple <listen-socket> but get: > > > > "EROR connection/connection_setup_sockets Could not create listener > > socket on port
2023 Oct 16
1
"Could not create listener socket on port" error only when using systemd service
On 10/16/23 10:37, Michael C Cambria wrote: > > Hi, > > I'm using icecast via Fedora 37 package and systemd service to start. > > I've added multiple <listen-socket> but get: > > "EROR connection/connection_setup_sockets Could not create listener > socket on port xxx" *snip* That error sounds like it could either be an issue relating to which
2010 Jun 14
5
cooked mode sessions
Picking up on a couple really old threads (e.g. http://osdir.com/ml/ietf.secsh/2001-09/msg00003.html ) I've finally gotten around to this. The EXTPROC support on Linux is missing, but you can find kernel patches for that here http://lkml.org/lkml/2010/6/11/403 I've also fixed up the netkit telnet / telnetd code to work with EXTPROC / LINEMODE on Linux, those patches are here
2001 Jan 03
1
PORT BUG: openssh 2.3.0p1 in Linux Slackware 7
I'm running a Slackware 7-based Linux distribution. I had a problem using openssh 2.3.0p1. Slackware 7 uses shadow passwords. Openssh picks up the shadow password information correctly but doesn't encrypt the incoming password properly so all password authentication fails. The problem is that sshd *must* be compiled with the link flag '-lcrypt' which includes libcrypt with the
2004 Aug 06
0
could not create listener socket on port 8000
--- Oliver Stirling <oliver@ojms.org.uk> wrote: > jensen galan wrote: > > >thanks for the advice! > > > >i tried the netstat command to see if anything is > >running on port 8000, and it came up empty. > > > >any other suggestions? really appreciate this. > > > >jg > > > >__________________________________ > > >
2004 Aug 06
1
could not create listener socket on port 8000
On Wed, 7 Jan 2004, jensen galan wrote: > <hostname>localhost</hostname> > <port>8000</port> > > <listen-socket> > <port>8000</port> > <bind-address>192.168.1.99</bind-address> > </listen-socket> ah. I think I see your problem. You don't want to use both of these port values. If you want it to just use
2004 Aug 06
2
could not create listener socket on port 8000
jensen galan wrote: >thanks for the advice! > >i tried the netstat command to see if anything is >running on port 8000, and it came up empty. > >any other suggestions? really appreciate this. > >jg > >__________________________________ > > Do you have the server configured on the correct ip address (clutching at straws) as I supose it might come up with