Quote:
|
Originally Posted by hamba
I'll contact the port maintainer and see if he can hep
|
IMO, that's
not something you should be bothering the port maintainer with. Please google for that error message; there are many hits.
Just a comment from me, FWIW: using the scponly chroot capabilities introduces something of a security risk, in that you're requiring it to run with the suid bit set. To me it would be much safer to build a FBSD jail and keep your users contained within. Or, just use the regular scponly shell if you can live with the idea that they'll have access to files on the system that their permissions allow.