More info. I used getenforce' and found SELinux is installed but disabled on the system where FTP Voyager can connect using SFTP over ssh, and not installed at all on the system where FTP Voyager cannot connect. In fact, using either the `getenforce' or `'sestatus' on the no-connect system yields `command not found'. Am I on to something?
- ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP tomas
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP Lars Noodén
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP Daniel Bareiro
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFT... Steve Matzura
- Re: ssh Problem using it for SFT... Daniel Bareiro
- Re: ssh Problem using it for... Steve Matzura
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP Daniel Bareiro
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP Steve Matzura
- Re: ssh Problem using it for SFTP Brandon Vincent