FS#16474 - scponly doesn't seem to work on x86_64

Attached to Project: Arch Linux
Opened by D. Casey Tucker (dctucker) - Monday, 05 October 2009, 18:46 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 05 October 2009, 21:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I'm able to compile scponly from source and get it working, but when I use the version in [community] and try to login to the affected server via sftp, I get the following error:

Oct 5 14:16:27 [hostname] sshd[20189]: subsystem request for sftp
Oct 5 14:16:27 [hostname] scponly[20190]: a getopt() argument check could not be performed for /usr/lib/ssh/sftp-server, recompile scponly without support for /usr/lib/ssh/sftp-server or rebuild scponly with getopt
Oct 5 14:16:27 [hostname] scponly[20190]: requested command (/usr/lib/ssh/sftp-server) tried to use disallowed argument (username: [username](1001), IP/port: [ip] 57293 22))


Additional info:
Version: 4.8-5



Steps to reproduce:

Install scponly, assign a user to use /usr/bin/scponly as the shell, try to login as said user.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 05 October 2009, 21:29 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#16475 
Comment by Pierre Schmitz (Pierre) - Monday, 05 October 2009, 18:50 GMT
Why don't you use the built-in scp chroot capabilities of ssh? Btw: this is a community package.
Comment by D. Casey Tucker (dctucker) - Monday, 05 October 2009, 19:47 GMT
I know this is a community package, but I couldn't find the community bug-report page for this item. I'm using it because I don't care about chrooting, I care about making sure that certain users can get access via sftp but not shell access.
Comment by D. Casey Tucker (dctucker) - Monday, 05 October 2009, 19:53 GMT
Update: sorry for the trouble, I've posted to the community bug report system.

http://bugs.archlinux.org/task/16475

Loading...