On Mon, Nov 9, 2020 at 10:50 PM Cameron Simpson wrote:
> On 09Nov2020 22:47, Tom H wrote:
>>
>> "w" and "who" look at "/var/run/utmp".
>>
>> "last" looks at "/var/log/wtmp".
>
> Thank you for this correction, brain fade on my part.
You're welcome. The only reason that I remember this mismarch be
On 09Nov2020 22:47, Tom H wrote:
>On Sat, Nov 7, 2020 at 10:22 PM Cameron Simpson
>wrote:
>> Dunno, but maybe you can disable what it measures. Do your xterms
>> make entries in wtmp (listed by "w" and "who")? Is so, ISTR that
>> xterm has an option to not do that (look for "wtmp" in the manual
>
On Sat, Nov 7, 2020 at 10:22 PM Cameron Simpson
wrote:
> On 06Nov2020 21:50, Tom Horsley wrote:
>>
>> For as long as I can remember I've run dnf update in a root
>> xterm and when all the akmod activity and wot-not is finished,
>> I've run reboot from another terminal.
>>
>> Now, it won't reboot
On Sun, Nov 08, 2020 at 12:05:14PM -0800, Dave Stevens wrote:
> Matthew Miller wrote:
> > On Sun, Nov 08, 2020 at 11:13:31AM -0800, Dave Stevens wrote:
> > > "The current console user is generally allowed to reboot the
> > > system." why?? isn't that a giant security hole? just from
> > > mistakes
On 20201108 11:33:30, Dave Stevens wrote:
On Sun, 8 Nov 2020 14:19:53 -0500
Jamie Fargen wrote:
If you have physical access it is trivial to gain root to the host, by
booting into single user mode and changing the root password.
you mean it won't work over ssh?
There seems to be some linguis
On 11/8/20 12:13 PM, Dave Stevens wrote:
I just shut everything down. On reboot I logged in as dave, no apps
running and only one user - me. typing reboot into bash restarted the
machine.
Does your regular user have wheel? If so, try creating a test user
without it and see what happens. (Non
On 08Nov2020 11:13, Dave Stevens wrote:
>On Sat, 7 Nov 2020 17:28:01 -0800
>jdow wrote:
>
>
>and then others wrote
>"The current console user is generally allowed to reboot the system."
>
>why?? isn't that a giant security hole? just from mistakes, not to
>mention malice.
Cannot the console user
On Sun, 8 Nov 2020 14:36:03 -0500
Matthew Miller wrote:
> On Sun, Nov 08, 2020 at 11:13:31AM -0800, Dave Stevens wrote:
> > "The current console user is generally allowed to reboot the
> > system." why?? isn't that a giant security hole? just from
> > mistakes, not to mention malice.
>
> What
>
> you mean it won't work over ssh?
>
Correct. If you ssh into a host, you need to be in a group with elevated
privileges like whee, use sudo, or the root user to shutdown or reboot the
system. I ssh'd into the same system with the same username and password
with the F32 VM that I started up and
On Sun, Nov 08, 2020 at 11:13:31AM -0800, Dave Stevens wrote:
> "The current console user is generally allowed to reboot the system."
> why?? isn't that a giant security hole? just from mistakes, not to
> mention malice.
What is the attack scenario you are envisioning here for this to be a
securit
On Sun, 8 Nov 2020 14:19:53 -0500
Jamie Fargen wrote:
> If you have physical access it is trivial to gain root to the host, by
> booting into single user mode and changing the root password.
you mean it won't work over ssh?
___
users mailing list -- us
On Sun, Nov 8, 2020 at 2:15 PM Dave Stevens wrote:
> On Sat, 7 Nov 2020 17:28:01 -0800
> jdow wrote:
>
>
>
> and then others wrote
>
> "The current console user is generally allowed to reboot the system."
>
> why?? isn't that a giant security hole? just from mistakes, not to
> mention malice.
>
On Sat, 7 Nov 2020 17:28:01 -0800
jdow wrote:
and then others wrote
"The current console user is generally allowed to reboot the system."
why?? isn't that a giant security hole? just from mistakes, not to
mention malice.
I just shut everything down. On reboot I logged in as dave, no apps
run
On Sun, Nov 8, 2020 at 9:44 AM Mauricio Tavares wrote:
> On Sat, Nov 7, 2020 at 7:47 PM Samuel Sieb wrote:
> >
> > On 11/7/20 3:16 PM, jdow wrote:
> > > On 20201107 13:21:47, Cameron Simpson wrote:
> > >> On 06Nov2020 21:50, Tom Horsley wrote:
> > >>> For as long as I can remember I've run dnf
On Sat, Nov 7, 2020 at 7:47 PM Samuel Sieb wrote:
>
> On 11/7/20 3:16 PM, jdow wrote:
> > On 20201107 13:21:47, Cameron Simpson wrote:
> >> On 06Nov2020 21:50, Tom Horsley wrote:
> >>> For as long as I can remember I've run dnf update in a root
> >>> xterm and when all the akmod activity and wot-
On 07Nov2020 17:28, jdow wrote:
>On 20201107 16:47:03, Samuel Sieb wrote:
>>On 11/7/20 3:16 PM, jdow wrote:
>>>On 20201107 13:21:47, Cameron Simpson wrote:
On 06Nov2020 21:50, Tom Horsley wrote:
>For as long as I can remember I've run dnf update in a root
>xterm and when all the akmod
On 20201107 16:47:03, Samuel Sieb wrote:
On 11/7/20 3:16 PM, jdow wrote:
On 20201107 13:21:47, Cameron Simpson wrote:
On 06Nov2020 21:50, Tom Horsley wrote:
For as long as I can remember I've run dnf update in a root
xterm and when all the akmod activity and wot-not is finished,
I've run re
On 11/7/20 3:16 PM, jdow wrote:
On 20201107 13:21:47, Cameron Simpson wrote:
On 06Nov2020 21:50, Tom Horsley wrote:
For as long as I can remember I've run dnf update in a root
xterm and when all the akmod activity and wot-not is finished,
I've run reboot from another terminal.
Now, it won't r
On 20201107 13:21:47, Cameron Simpson wrote:
On 06Nov2020 21:50, Tom Horsley wrote:
For as long as I can remember I've run dnf update in a root
xterm and when all the akmod activity and wot-not is finished,
I've run reboot from another terminal.
Now, it won't reboot "because root is logged in"
On 06Nov2020 21:50, Tom Horsley wrote:
>For as long as I can remember I've run dnf update in a root
>xterm and when all the akmod activity and wot-not is finished,
>I've run reboot from another terminal.
>
>Now, it won't reboot "because root is logged in".
>
>Gah! Who cares if root is logged in?
>
Tom Horsley writes:
For as long as I can remember I've run dnf update in a root
xterm and when all the akmod activity and wot-not is finished,
I've run reboot from another terminal.
Now, it won't reboot "because root is logged in".
Gah! Who cares if root is logged in?
Can I disable this helpf
On Fri, 2020-11-06 at 21:50 -0500, Tom Horsley wrote:
> For as long as I can remember I've run dnf update in a root
> xterm and when all the akmod activity and wot-not is finished,
> I've run reboot from another terminal.
>
> Now, it won't reboot "because root is logged in".
>
> Gah! Who cares if
For as long as I can remember I've run dnf update in a root
xterm and when all the akmod activity and wot-not is finished,
I've run reboot from another terminal.
Now, it won't reboot "because root is logged in".
Gah! Who cares if root is logged in?
Can I disable this helpful feature any way?
___
23 matches
Mail list logo
