scponly bug in RHEL5 and Suse
Brought to you by:
chronocide
Menu
▾
▴
#3 scponly bug in RHEL5 and Suse
I've been trying scponly in RHEL5, between 3 boxes, to be clear.
Obviulsy, I downloaded the package from the official website of the project,
http://sublimation.org/scponly/scponly-4.6.tgz
I compiled and installed it succesfully, everything worked out well.
I did the proper things to the /etc/shells and usermod in order to have my user with the scponly bash.
So, at this point everything should be ok, right?
I tried to copy a file using scp and it failed, nothing interesting when debugging the scp command (-v -v -v), nothing at all.
So after sometime guessing what could be wrong...(without success) I decided to copy the binary from my Ubuntu.
This is the infomation about the debian package from where I got the binary
manu@life:~$ apt-cache show scponly
Package: scponly
Priority: optional
Section: universe/utils
Installed-Size: 168
Maintainer: Thomas Wana <greuff@debian.org>
Architecture: i386
Version: 4.6-1
After changing it, everything is working smoothly.
I just wanted to let you know this issue with my RHEL5 and Suse 10
Thank you all for scpcopy.
Manuel
Logged In: YES
user_id=651826
Originator: NO
According to http://sublimation.org/scponly/wiki/index.php/FAQ
I can't connect to scponly using scp, what do I do?
scponly was recently changed (in version 4.2) to not allow scp by default. To enable scponly run configure with the --enable-scp-compat flag, and then reinstall scponly using the "make; make install" process.