search for: terekhov

Hi, As I understand the "ForceCommand" in the sshd_confing file is meant to ignore any command supplied by the client, but if user's home is shared by server and client machines over network (ex. NFS) then user can still put something else into ~/.ssh/rc file and overcome this limitation. Is it possible to disable execution of the ~/.ssh/rc file in such a case? Thaks, Mike

> > On Mar 22, 2008, at 3:32 PM, Chris Wilson wrote: > > > >> As I understand the "ForceCommand" in the sshd_confing file is meant to > >> ignore any command supplied by the client, but if user's home is shared > >> by server and client machines over network (ex. NFS) then user can > >> still put something else into ~/.ssh/rc file and

...ackground on your OS and what kind of behavior you would like to end up with, I will send you some pointers to get you started in the right direction. On Mar 22, 2008, at 3:32 PM, openssh-unix-dev-request at mindrot.org wrote: > Date: Thu, 20 Mar 2008 18:19:02 -0400 > From: "Mikhail Terekhov" <termim at gmail.com> > Subject: ForceCommand and ~/.ssh/rc > > Hi, > > As I understand the "ForceCommand" in the sshd_confing file is > meant to > ignore any command supplied by the client, but if user's home is > shared by > server and clie...

I intend to release a project I wrote with Rails. What is the right licensing scheme for a web application (content managing system) which could grow with plugins and add-ons ? Personally, I would prefer the GPL but does that mean any add-on to the CMS (like task management) will have to be GPL ? If some people contribute to the code could it still be double-licenced so that the people who