Hi:
I could not figure out how to restrict users or other users from certain
privileges to execute certain commands in FreeBSD/NanoBSD?
What I meant is I want to create a NanoBSD image in which there will be an
additional user, say 'admin'. I need to give this new user (admin) some
privileges to
> Hi:
>
> I could not figure out how to restrict users or other users from certain
> privileges to execute certain commands in FreeBSD/NanoBSD?
>
> What I meant is I want to create a NanoBSD image in which there will be an
> additional user, say 'admin'. I need to give this new user (admin) some
On Sat, Apr 28, 2012 at 9:38 AM, Daniel Braniss wrote:
> > Hi:
> >
> > I could not figure out how to restrict users or other users from certain
> > privileges to execute certain commands in FreeBSD/NanoBSD?
> >
> > What I meant is I want to create a NanoBSD image in which there will be
> an
> > a
On 04/28/2012 09:50 AM, Zenny wrote:
> On Sat, Apr 28, 2012 at 9:38 AM, Daniel Braniss wrote:
>
>>> Hi:
>>>
>>> I could not figure out how to restrict users or other users from certain
>>> privileges to execute certain commands in FreeBSD/NanoBSD?
>>>
>>> What I meant is I want to create a NanoBSD
On 2012-04-28 09:50, Zenny wrote:
> On Sat, Apr 28, 2012 at 9:38 AM, Daniel Braniss wrote:
...
>> try sudo from ports, security/sudo
> Thanks Daniel, but sudo gives all (not selective) root privileges to the
> user (admin in my case).
This isn't true. With sudo, you can give specific users, or g
28.04.2012 14:50, Zenny пишет:
>> try sudo from ports, security/sudo
>>
>> cheers,
>>danny
>>
>>
> Thanks Daniel, but sudo gives all (not selective) root privileges to the
> user (admin in my case). So this is not what I am trying to achieve in my
> original post.
Please do study sudo rea
On Sat, Apr 28, 2012 at 11:29:58AM +0200, Dimitry Andric wrote:
> On 2012-04-28 09:50, Zenny wrote:
> > On Sat, Apr 28, 2012 at 9:38 AM, Daniel Braniss wrote:
> ...
> >> try sudo from ports, security/sudo
> > Thanks Daniel, but sudo gives all (not selective) root privileges to the
> > user (admin
Hi, all,
Am 28.04.2012 um 11:39 schrieb Eugene Grosbein:
> 28.04.2012 14:50, Zenny пишет:
>
>>> try sudo from ports, security/sudo
>>>
>>> cheers,
>>> danny
>>>
>>>
>> Thanks Daniel, but sudo gives all (not selective) root privileges to the
>> user (admin in my case). So this is not wha
On Sat, Apr 28, 2012 at 11:47:07AM +0200, Patrick M. Hausen wrote:
> Hi, all,
>
> Am 28.04.2012 um 11:39 schrieb Eugene Grosbein:
>
> > 28.04.2012 14:50, Zenny ??:
> >
> >>> try sudo from ports, security/sudo
> >>>
> >>> cheers,
> >>> danny
> >>>
> >>>
> >> Thanks Daniel, but su
On Sat, 28 Apr 2012 09:50:30 +0200
Zenny wrote:
> Thanks Daniel, but sudo gives all (not selective) root privileges to the
> user (admin in my case). So this is not what I am trying to achieve in my
> original post.
FWIW, sudo can be configured to allow only some commands.
HTH
--
Regards,
Torfi
Hi!
> > > Please do study sudo real power :-)
> > > It can give selective privileges per-command,
[...]
> > Just make sure none of the permitted commands has got the
> > feature of starting a shell ;-))
>
> Right, think of vi(1), less(1), et al.
Even this aspect is taken care of with sudo (at le
On 04/28/2012 02:50 AM, Zenny wrote:
On Sat, Apr 28, 2012 at 9:38 AM, Daniel Braniss wrote:
Hi:
I could not figure out how to restrict users or other users from certain
privileges to execute certain commands in FreeBSD/NanoBSD?
What I meant is I want to create a NanoBSD image in which there
On Apr 28, 2012 12:50 AM, "Zenny" wrote:
>
> On Sat, Apr 28, 2012 at 9:38 AM, Daniel Braniss
wrote:
>
> > > Hi:
> > >
> > > I could not figure out how to restrict users or other users from
certain
> > > privileges to execute certain commands in FreeBSD/NanoBSD?
> > >
> > > What I meant is I want
Le 28/04/2012 ? 09:55:41+0300, Alexander Motin a écrit
> On 04/28/12 00:34, Albert Shih wrote:
> Definitely, because here I don't see much.
>
Thanks.
> Generally, all CPU loads and load averages now calculated via sampling,
> so theoretically with spiky load numbers may vary for many reasons.
On Sat, Apr 28, 2012 at 08:04:31PM +0200, Kurt Jaeger wrote:
> Hi!
>
> > > > Please do study sudo real power :-)
> > > > It can give selective privileges per-command,
> [...]
> > > Just make sure none of the permitted commands has got the
> > > feature of starting a shell ;-))
> >
> > Right, th
On Apr 28, 2012 4:03 PM, "Jason Hellenthal" wrote:
> cp /usr/bin/vi ~/
>
> or upload your own...
>
> sudo $HOME/vi
>
If your Cmnd_Alias includes the full path to vi, then your last command
won't work.
___
freebsd-stable@freebsd.org mailing list
http://l
On Sat, Apr 28, 2012 at 04:34:34PM -0700, Freddie Cash wrote:
> On Apr 28, 2012 4:03 PM, "Jason Hellenthal" wrote:
> > cp /usr/bin/vi ~/
> >
> > or upload your own...
> >
> > sudo $HOME/vi
> >
>
> If your Cmnd_Alias includes the full path to vi, then your last command
> won't work.
I know. Jus
On 04/29/12 01:53, Oliver Pinter wrote:
Attached the ktr file. This is on core2duo P9400 cpu (
smbios.system.product="HP ProBook 5310m (WD792EA#ABU)" ). The workload
is only a single user boost: sh + top running, but the load average is
near 0.5.
ktr shows no real load there. But it shows that
On Sun, 29 Apr 2012 08:17:38 +0300, Alexander Motin wrote:
> On 04/29/12 01:53, Oliver Pinter wrote:
> > Attached the ktr file. This is on core2duo P9400 cpu (
> > smbios.system.product="HP ProBook 5310m (WD792EA#ABU)" ). The workload
> > is only a single user boost: sh + top running, but the l
On 04/29/12 09:09, Ian Smith wrote:
On Sun, 29 Apr 2012 08:17:38 +0300, Alexander Motin wrote:
> On 04/29/12 01:53, Oliver Pinter wrote:
> > Attached the ktr file. This is on core2duo P9400 cpu (
> > smbios.system.product="HP ProBook 5310m (WD792EA#ABU)" ). The workload
> > is only
> Daniel Braniss wrote:
> > > Security_Multipart(Fri_Apr_27_13_35_56_2012_748)--
> > > Content-Type: Text/Plain; charset=us-ascii
> > > Content-Transfer-Encoding: 7bit
> > >
> > > Rick Macklem wrote
> > > in
> > > <1527622626.3418715.1335445225510.javamail.r...@erie.cs.uoguelph.ca>:
> > >
21 matches
Mail list logo