Tiny Core Extensions > TCE Q&A Forum

openssh connection refused

<< < (2/3) > >>

tinypoodle:

--- Quote from: althalus on July 28, 2010, 07:42:41 PM ---Netstat can also be coerced to show what application is using what port, but I'll leave that as an excercise to the reader (hint: Google) (It may also require the full netstat, rather than the busybox version)

--- End quote ---
Works fine with busybox  ;)
Option is "-p"

cparke:

--- Quote from: mc006 on July 29, 2010, 04:04:47 AM ---Hi,
thanks i got it working now....
by default when try to start openssh using ./openssh start, it looks for sshd_config file which you can create by cp the sshd_config.example file. The issue is that when it does not find the sshd_config file it displays the error output stating that there is no sshdd_config file.....this is where the error is it should state sshd_config and not sshdd_config....minor error...

Thanks

--- End quote ---
This message may be 15 years later, but believe it or not I am seeing this exact same issue on the latest Tinycore (16.0).  Sshd won't start until that missing configuration file is created.  Furthermore, outgoing SSH/SCP/SFTP are failing with a strange error message for me. Putty is the work around, that works.. Quite surprising that such a simple and commonly used tool doesn't work in Tinycore even after so much time!

Rich:
Hi cparke

--- Quote from: cparke on April 03, 2025, 09:28:01 AM --- ... Quite surprising that such a simple and commonly used tool doesn't work in Tinycore even after so much time!
--- End quote ---
It does work. The end user can either copy the included config file
example, or create one that meets their needs.

The error message is a reminder that it's your job to figure out how
you need openssh configured. There's no universal config file that
will meet everyones needs, so a default is not placed where openssh
would find it.

cparke:

--- Quote from: Rich on April 03, 2025, 11:35:32 AM ---The error message is a reminder that it's your job to figure out how
you need openssh configured. There's no universal config file that
will meet everyones needs, so a default is not placed where openssh
would find it.
--- End quote ---
ssh now working with the config file in place.  The error message isn't very descriptive of the problem, which is why this came up again with me.

However, I still am having similar problems with sftp and scp.  I thought these use the same config file, or not?

I'm getting this:


--- Code: ---tc@TinyCorePure64:~$ sftp 192.168.0.100
192.168.0.100's password:
client_loop: send disconnect: Broken pipe
Connection closed. 
Connection closed
tc@TinyCorePure64:~$
--- End code ---

Any clue how to fix that too?

Rich:
Hi cparke
This worked for me.

Server machine 192.168.1.35
User name Rich

--- Code: ---sudo cp /usr/local/etc/ssh/sshd_config.orig /usr/local/etc/ssh/sshd_config
sudo /usr/local/etc/init.d/openssh start
sudo chpasswd
Rich:PASSWORD
--- End code ---

Client machine:

--- Code: ---tc@box:~$ sftp Rich@192.168.1.35
Rich@192.168.1.35's password:
Connected to 192.168.1.35.
sftp> exit
tc@box:~$
--- End code ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page