On Wed, Dec 19, 2012 at 11:22:51AM -0600, Terry wrote: > We just upgraded to 2.3.3 (via EPEL on RHEL 6). After the upgrade, > our users get this when trying to simply scp in: > /usr/bin/rssh: Permission denied
This usually means that the program does not have execute permissions. In the case of a shell (such as rssh), however, it could also mean that the program that the shell is trying to execute does not have execute permissions. So look at the file permissions on rssh and on the scp binary, and make sure they have appropriate permissions for the users/groups who will be running them. At any rate, this really isn't an rssh problem per se. > The users are all part of an "sftp" group that has this in > /etc/security/access: > +:sftp:ALL > > I am not sure how to further debug this. Anyone have some ideas? It could also be that this is somehow failing. You could debug by temporarily changing a user's shell to bash and running id after they log in. Also look at the system logs (generally /var/log/messages) or wherever you have rssh configured to log. The USER log facility is (by default) configured to log to a different log file than the AUTH facility. There may be more info there. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0x81CFE75D
pgpW6c4u6xuGF.pgp
Description: PGP signature
------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________ rssh-discuss mailing list rssh-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rssh-discuss
