Can not connect sftp - "Warning: Permanently added to the list of known hosts"

https://stackoverflow.com/questions/9299651/git-says-warning-permanently-added-to-the-list-of-known-hosts

Create a ~/.ssh/config file and insert the line:

UserKnownHostsFile ~/.ssh/known_hosts

You will then see the message the next time you access Github (or any other sftp server), but after that you'll not see it anymore because the host is added to the known_hosts file. This fixes the issue, rather than just hiding the log message.

How to access SFTP server in Python

https://www.pcwdld.com/how-to-access-sftp-server-in-python

How can I find out if a specific program is installed?

How can I find out if a specific program is installed?

scp [source file] [username]@[destination server]:.

scp cool_stuff.txt sanjeev@example.com:.

 Remember not to miss the colon and full stop at the end.

https://superuser.com/questions/850740/how-to-upload-local-file-to-server-through-linux-terminal

Restrict SFTP (SSH) users to home folder

https://bensmann.no/restrict-sftp-users-to-home-folder/

Here is a guide for setting up SFTP users who’s access is restricted to their home directory.

Add the following to the end of the /etc/ssh/sshd_config file:

Subsystem sftp internal-sftp

# This section must be placed at the very end of sshd_config
Match Group sftponly
    ChrootDirectory %h
    ForceCommand internal-sftp
    AllowTcpForwarding no

This means that all users in the ‘sftponly’ group will be chroot’d to their home directory, where they only will be able to run internal SFTP processes.

Now you can create the group sftponly by running the following command:

$ groupadd sftponly

Set a user’s group:

$ usermod steve -g sftponly

To deny SSH shell access, run the following command:

$ usermod steve -s /bin/false

And set the user’s home directory:

$ usermod steve -d /folder

Finally, you probably need to restart SSH

$ service ssh restart

The SSH part should now be in order, but you should make sure that file permissions also are correct. If the chroot environment is in a user’s home directory both /home and /home/username MUST be owned by root and should have permissions along the lines of 755 or 750.

In other words, every folder leading up to and including the home folder must be owned by root, otherwise you will get the following error after logging in:

Write failed: Broken pipe
Couldn't read packet: Connection reset by peer