SSH user for domain.tld

[koko92_national]

It will be nice if i could add chrooted ssh user for domain.tld Only to enter the username, password and directory. What do you think?

[Nuxwin]

(09-06-2009 11:37 PM)koko92_national Wrote:  It will be nice if i could add chrooted ssh user for domain.tld Only to enter the username, password and directory. What do you think?

What would be the primary interest in the context of a shared hosting dedicated hosting web page? Certain panel offer this feature but I'm not sure it is indispensable.

[sci2tech]

It is on the roadmap. As a matter of fact I already started some work on this but do not expect it too soon.

[theprincy]

(09-06-2009 11:55 PM)sci2tech Wrote:  It is on the roadmap. As a matter of fact I already started some work on this but do not expect it too soon.

[koko92_national]

(09-06-2009 11:55 PM)sci2tech Wrote:  It is on the roadmap. As a matter of fact I already started some work on this but do not expect it too soon.

Great in which version should we see it?

[sci2tech]

Maybe 1.2.0

[koko92_national]

Great this is matching with my plans perfectly. Thank you and I wish ISP Omega to become first of all Hosting Panels.

[kilburn]

Quote:As a matter of fact I already started some work on this but do not expect it too soon.

Just for the record, which chroot solution are you planning to implement? Everytime that I've read about chrooted ssh access I'm left with the feeling that there is no really secure way to do it without a really big overhead....

[koko92_national]

If he limits it by username and group name I think it will be all right.

[kilburn]

Quote:If he limits it by username and group name I think it will be all right.

I'm speaking about the chroot concept, not about which permissions should you use. AFAIK chroots are either:
-) insecure : if there is a work-around to allow running binaries from outside the chroot
-) nearly unusable though a shell : if each chroot has just the minimal set of binaries accessible.
-) highly overloaded : if a complete copy/mount --bind/something like this is used so that chroot users have access to all binaries.

It has nothing to do about who you let access the chroot, but how you let him run the binaries.