On 3/12/2012 5:23 PM, Polytropon wrote:
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
I think this would not let the user to
On Mon, Mar 12, 2012 at 8:19 PM, Tim Daneliuk tun...@tundraware.com wrote:
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want them to be able to exit
to the shell. The client in question has strong (and unyielding)
On 03/13/2012 01:39 AM, Joshua Isom wrote:
On 3/12/2012 5:23 PM, Polytropon wrote:
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
I think
On 3/13/2012 10:43 AM, Tim Daneliuk wrote:
On 03/13/2012 01:39 AM, Joshua Isom wrote:
On 3/12/2012 5:23 PM, Polytropon wrote:
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
Tim Daneliuk tun...@tundraware.com wrote:
... we're talking about almost 1000 systems
here. That's a whole bunch of configuration...
Had you considered using something along the lines of
sysutils/puppet?
___
freebsd-questions@freebsd.org mailing
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want them to be able to exit
to the shell. The client in question has strong (and unyielding) InfoSec
requirements in this regard.
So ... are there editors without this
On Mon, Mar 12, 2012 at 02:19:06PM -0500, Tim Daneliuk wrote:
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want them to be able to exit
to the shell. The client in question has strong (and unyielding) InfoSec
On 03/12/2012 03:13 PM, Thomas Dickey wrote:
On Mon, Mar 12, 2012 at 02:19:06PM -0500, Tim Daneliuk wrote:
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want them to be able to exit
to the shell. The client in question
From owner-freebsd-questi...@freebsd.org Mon Mar 12 14:22:29 2012
Date: Mon, 12 Mar 2012 14:19:06 -0500
From: Tim Daneliuk tun...@tundraware.com
To: FreeBSD Mailing List freebsd-questions@freebsd.org
Subject: Editor With NO Shell Access?
I have a situation where I need to provide people
On 2012-03-12 15:19, Tim Daneliuk wrote:
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want them to be able to exit
to the shell. The client in question has strong (and unyielding) InfoSec
requirements in this regard.
So
On Mon, 12 Mar 2012 17:40:10 -0400, Steve Bertrand wrote:
You can force a user directly into an editor so they have no shell
access. For example, if the user has '/bin/csh' as their login shell,
adding:
exec /usr/local/bin/vim
into their ~/.cshrc file will force them directly into vim.
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
I think this would not let the user to login,etc
___
freebsd-questions@freebsd.org mailing
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
I think this would not let the user to login,etc
I'm not sure... I assume
On 03/12/2012 03:23 PM, Polytropon wrote:
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
I think this would not let the user to
On 03/12/2012 03:47 PM, Edward M. wrote:
On 03/12/2012 03:23 PM, Polytropon wrote:
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe
I
On Mon, Mar 12, 2012 at 7:19 PM, Tim Daneliuk tun...@tundraware.com wrote:
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want them to be able to exit
to the shell. The client in question has strong (and unyielding)
On Mon, 12 Mar 2012 16:34:18 -0700, Edward M. wrote:
On 03/12/2012 03:47 PM, Edward M. wrote:
On 03/12/2012 03:23 PM, Polytropon wrote:
On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote:
On 03/12/2012 03:10 PM, Polytropon wrote:
/etc/shells to work, but a passwd entry like
There are two edits to make to ex_shell.c in /usr/src/contrib/nvi/ex that
will prevent a shell from being executed.
99,100c
return (1);
.
48,51c
return (1);
.
On Mon, Mar 12, 2012 at 4:59 PM, David Brodbeck g...@gull.us wrote:
On Mon, Mar 12, 2012 at 7:19 PM, Tim Daneliuk
From owner-freebsd-questi...@freebsd.org Mon Mar 12 17:46:04 2012
Date: Mon, 12 Mar 2012 15:47:59 -0700
From: Edward M. eam1edw...@gmail.com
To: Polytropon free...@edvax.de
Cc: freebsd-questions@freebsd.org
Subject: Re: Editor With NO Shell Access?
On 03/12/2012 03:23 PM, Polytropon wrote
On Mon, Mar 12, 2012 at 03:20:57PM -0500, Tim Daneliuk wrote:
On 03/12/2012 03:13 PM, Thomas Dickey wrote:
On Mon, Mar 12, 2012 at 02:19:06PM -0500, Tim Daneliuk wrote:
I have a situation where I need to provide people with the ability to edit
files. However, under no circumstances do I want
On 03/12/2012 05:33 PM, Robert Bonomi wrote:
From owner-freebsd-questi...@freebsd.org Mon Mar 12 17:46:04 2012
Date: Mon, 12 Mar 2012 15:47:59 -0700
From: Edward M.eam1edw...@gmail.com
To: Polytroponfree...@edvax.de
Cc: freebsd-questions@freebsd.org
Subject: Re: Editor With NO Shell Access
21 matches
Mail list logo
