[Coco] Compiling LWTOOLS - root ?

[Patrick Ulland]

A distinction without a difference. Probably half our helpful users knew 
and always used 'sudo bash' to save typing and avoid logs. Management 
let 'em, and when I left (just preVID), that trick still worked after 
ssh in. Maybe we broke something.


On 7/3/2023 10:48 AM, Jeff Teunissen via Coco wrote:
> The slight security difference between sudo and su on a regular Linux
> distro is that the password being entered is yours, and not the root
> password (which on most installations does not exist in order to
> disallow root login entirely). Those individual actions themselves
> don't make the machine more secure, but the combination (no root login
> permitted, no root password to crack) does somewhat improve things and
> makes it easier to lock down more by just editing sudoers.
>
> On Mon, Jul 3, 2023 at 7:16 AM Patrick Ulland via Coco
> <coco at maltedmedia.com> wrote:
>> Lots of sudo advice is taken out of context. In a commercial (not
>> development) systems, sudo is very important, users can’t do ANYTHING
>> unless they are in a short list of folks granted an even shorter list of
>> commands.
>>
>>    In a regular Linux distro, default user can sudo anything - try ‘sudo
>> bash’. So it’s only a password check now, might as well su once for the
>> whole task. Just turn the light off when done:-)
>>
>>
>>
>> On 7/2/2023 8:53 AM, Rocky Hill via Coco wrote:
>>>    Hi Charlie,
>>>
>>> You want to switch to the root user and then run make install as root?
>>> Yup, that should work as well.
>>>
>>>
>>>       On Sunday, July 2, 2023 at 09:36:48 AM EDT, coco at jechar.ca <coco at jechar.ca> wrote:
>>>
>>>    Reply to Rocky Hill
>>>
>>> Can I use
>>>
>>> su
>>> make install
>>>
>>> instead of
>>>
>>> sudo make install
>>>
>>> ?
>>>
>>> Charlie
>>>
>>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco