Tiny Core Linux
General TC => General TC Talk => Topic started by: MTCAT on February 25, 2026, 02:50:31 PM
-
Hi everyone,
On Tinycore 3.8.4 (kernel 2.6.33) I'm trying to copy some files off my VortexDX3 CF card, onto an external SSD over a 100 Mbit ethernet port, after setting the IP address on my little ASUS EEE laptop to 172.16.1.20, and getting ssh up and running on the TinyCore VortexDX3, from the ASUS laptop I can successfully execute;
ping 172.16.1.98
So we have a connection there!, on the VortexDX3 I also made sure that ssh is listening to port 22 with
sudo netstat -tupan
And ssh is indeed running and listening to port22 on the DX3.
But, when I type (on the ASUS EEE laptop)
scp tc@172.16.1.98:/home/tc/data/* .
So as to copy all the files in /home/tc/data into the current directory on the external SSD, I get a prompt asking for the password for tc, I also tried the above command with "sudo" and same thing, need the password for tc.
What is the password for tc?I thought it was an empty string, just simply hit return, but that isn't working.
Hoping someone can see what I'm doing wrong.
Thanks,
David
-
What is the password for tc?
I thought it was an empty string, just simply hit return, but that isn't working.
imho that is the wrong question
likely more relevant question(s) might be
-- what is the default ssh configuration?
&
-- how to configure ssh auth with / without password ?
afaik this is less about tc and more about ssh (*defaults)
though the interplay/combination of the two appears to be the source of your confusion
see also
https://unix.stackexchange.com/questions/582315/can-a-user-with-no-password-set-login-with-ssh
-
When dealing with ssh you need to set a password or use PKI, like copy the public key to the computer you tries to connect to.
There are a lot of guides how to deal with this in ssh. And i think you can also config the ssh server to accept none password.
But that of course is very insecure.
-
Hi mocore and patrikg,
Thanks for the help, I'll look in the ssh_config file and see what's in there, and read up on ssh options more, I need to learn more about ssh obviously!
I could also just set a password for user tc, just hoping that wouldn't cause permission issues with all the scripts in bootlocal.sh and ~/.X.d.
Thanks,
David
-
You should of course look at the server config sshd_config file. Not the client config (ssh_config).
-
Hi patrikg,
Thanks for the help, I looked at both config files and made some changes in them to try remove password checking and even RSA Key authentication but it didn't work, and I may have made things worse now because since I started up a fresh session of openssh, new keys were generated and now I can't even get as far as a password request with my scp attempt, my ASUS EEE bails out immediately now since the keys are different (I think), yet I didn't copy any keys over to the ASUS on the first attempt either, so I'm confused....
I guess I need to start openssh on my TinyCore, generate new keys, and then copy the public key to my ASUS EEE (into /home/user/ssh/known_hosts) and then ssh might work?, assuming I have the correct password for user tc.
And then on my TC box, I could copy the keys into a directory on /home/tc (persistent) and can then after powering up, can copy the keys stored in /home/tc into /usr/local/etc/ssh every time so that the keys stay the same?
I just want to be able to transfer data files over ethernet with scp, but I wonder if there might be other simpler ways, like with ftp or wget even?
Thanks,
David
-
Hi patrikg,
Thanks again for the help, I've had a bit of a breakthrough!
I was able to get a WinXP executable called "PSCP.exe" (which I think is based on, or uses PUTTY behind the scenes) to work, just had to create the ssh config files ahead of time, start up openssh on TC 3.8.4, with a copy of "PSCP.exe" in a directory on an external hard drive, can type the usual;
pscp tc@172.16.1.98:/home/tc/data/* .
To copy the contents of the data folder on the CF card into the directory from which the PSCP.exe command was executed, somehow the PSCP.exe program deals with the
key issue, just allows me to accept the key from TC, and can continue on.
I got this "PSCP.exe" executable with a BeagleBone Black based data acqusition system, which is used to transfer data to/from the BBB.
With that, I was getting about 5-7 MB/sec over the 100 MBit ethernet port (onto an NTFS formatted external HD), but I noticed my "go-to" 64 GB FAT32 formatted pen drive was still stuck at around 1 MB/sec, which is also what I was getting with it when it was connected to the VortexDX3 USB ports as well, so that pen drive itself seemed to be the issue actually.
So, I tried some other pen drives connected direct to the USB 2.0 ports on the VortexDX3 and my goodness, what a difference!, can't believe it!, my 4 GB Cactus pen drive (ext4) was seeing almost 40 MB/sec and another mini 128 GB FAT32 formatted pen drive was getting 20 MB/sec!!, wow.
So all my problems with slow data transfers before was just due to using a low quality pen drive it seems!, wow, never expected that there could be such a difference.
Now that I know that the USB2.0 ports can indeed work pretty fast as long as you have a decent pen drive, this takes the heat off scp, etc., but at least I do have a viable "plan-B" with the WinXP laptop running "PSCP.exe" to transfer data onto an external HD, that works pretty well too but is a bit slower at 5 MB/sec.
Thanks again for the help,
David