Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 178059

The SSH File Transfer Protocol (SFTP) provides secure file transfer functions using the same infrastructure used by the Secure Shell protocol. It can be seen as a secure replacement for FTP.

2
votes
2answers
I just installed a CentOS-based to serve as an SFTP server. I need all incoming files to go /mnt/inbound/ folder, so I want to ensure that every user from this host that logs in via SFTP gets /mnt … /inbound/ as their starting point, and I want to ensure that they cannot go anywhere else. I got as far as being able to connect with a test user using an SFTP client and ensuring the user is jailed to …
asked Jul 4 '16 by pmdci
5
votes
# Chroot the connection into the specified directory ChrootDirectory /mnt/inbound/%u # Force the connection to use the built-in SFTP support ForceCommand internal-sftp -d … internal-sftp -d /%u, I could make the /mnt/inbound/<username> folder be owned by the end-user since /mnt/inbound is now the new root directory that must be owned by the root account. However users would be …
answered Jul 4 '16 by pmdci
6
votes
2answers
I configured a CentOS server to be a SFTP server that receives customer files in a secure way. Then I need to be able to access these files via SMB. The 'root' of my SFTP is in /var/inbound/ Then … /inbound/customer1/uploads/) I managed to make the permissions work as expected and everything is fine and dandy to support customer access to the SFTP. One important aspect is that I 'jailed' users to …
asked Jan 4 '17 by pmdci
1
vote
Seems like I was chasing a zebra all along. Thanks to the help of users derobert, terdon and others in the /dev/chat channel, we found out that the issue is indeed SELinux. In fact, the CentOS wiki d …
answered Jan 5 '17 by pmdci