On Mon, 08 Jun 2020 16:02:02 -0400 "Garry T. Williams"
wrote
On Monday, June 8, 2020
12:41:03 PM EDT R. G. Newbury wrote:
On 2020-06-07 4:46 p.m., From: Samuel Sieb wrote:
On 6/7/20 10:31 AM, R. G. Newbury wrote:
It was apparently something to do with selinux. I usually disable
selinux as
On 2020-06-08 2:42 p.m.>Samuel Sieb wrote> On 6/8/20
9:41 AM, R. G. Newbury wrote:>> On 2020-06-07 4:46 p.m., From: Samuel
Sieb wrote:>>> On 6/7/20 10:31 AM, R. G. Newbury
wrote: Oddly 1) I was running as root... so*who/what* was the
'unauthorized sender'? and>>> That sounds like a l
On 2020-06-08 2:42 p.m.,Jonathan Billings wrote
On Mon, Jun 08, 2020 at
12:41:03PM -0400, R. G. Newbury wrote:
Wow! So running as root causes error messages? Pull the other leg, it has
bells on it!
And why? Because this was immediately after a clean install to a brand new
drive, while I was st
On 6/8/20 4:14 PM, Doug McGarrett wrote:
if it would work in a modern environment.) OpenSUSE's KDE provides
Dolphin PLUS a separate app that looks and works like Dolphin, but has
root access after you supply a password.
I expect it's just a different desktop file that launches Dolphin using
k
On Mon, 2020-06-08 at 11:40 -0700, Samuel Sieb wrote:
> Many years ago I used to always login as root because it was
> "easier". But then I realized it was unnecessary, somewhat
> hazardous, and tended to cause weird issues if I wasn't careful or
> even if I was.
When I first explored Linux, I di
On Mon, 8 Jun 2020 19:14:52 -0400
Doug McGarrett wrote:
> Now to the question for you: CERT seems to mean Community Emergency
> Response Team. Is this what you mean, or am I (probably)
> missing something?
https://www.us-cert.gov/
___
users mailing l
On 6/8/20 6:55 PM, jdow wrote:
The latest one is a java based exploit that hits both Linux and
Windows. It was announced within the past week. CERT is a good place
to go looking for exploits. Running as root for system maintenance
makes sense. Running as root routinely day after day is asking
The latest one is a java based exploit that hits both Linux and Windows. It was
announced within the past week. CERT is a good place to go looking for exploits.
Running as root for system maintenance makes sense. Running as root routinely
day after day is asking for problems. Perhaps the worst m
On Mon, 8 Jun 2020 at 15:00, Doug H. wrote:
> On Mon, Jun 8, 2020, at 10:54 AM, Tom Horsley wrote:
> > I keep asking for people to point me to the huge list
> > of exploits that certainly must exist given all the
> > horrors expressed about running as root.
>
> No one has ever been able to tell m
On Monday, June 8, 2020 12:41:03 PM EDT R. G. Newbury wrote:
> On 2020-06-07 4:46 p.m., From: Samuel Sieb wrote:
> >On 6/7/20 10:31 AM, R. G. Newbury wrote:
> >> It was apparently something to do with selinux. I usually disable
> >> selinux as the first or second thing I do to a new install. I
>
On Mon, Jun 08, 2020 at 01:54:21PM -0400, Tom Horsley wrote:
>
> I keep asking for people to point me to the huge list
> of exploits that certainly must exist given all the
> horrors expressed about running as root.
>
> No one has ever been able to tell me where to find it.
Running a graphical se
On 06/08/2020 12:51 PM, Bob Goodwin wrote:
I often have a window open using "su" is that less desirable than using
sudo? Bob
Same here. I never put myself in wheel because I always know the root
password and don't need sudo. I can't say that I always have a terminal
open as root, but I do
On 6/8/20 11:51 AM, Bob Goodwin wrote:
On 2020-06-08 14:40, Samuel Sieb wrote:
But then I realized it was unnecessary, somewhat hazardous, and tended
to cause weird issues if I wasn't careful or even if I was. "sudo -i"
is easy and convenient. I always have several terminal windows open
wi
On 2020-06-08 14:40, Samuel Sieb wrote:
But then I realized it was unnecessary, somewhat hazardous, and tended
to cause weird issues if I wasn't careful or even if I was. "sudo -i"
is easy and convenient. I always have several terminal windows open
with that running for the various root tas
On 6/8/20 9:41 AM, R. G. Newbury wrote:
On 2020-06-07 4:46 p.m., From: Samuel Sieb wrote:
On 6/7/20 10:31 AM, R. G. Newbury wrote:
Oddly 1) I was running as root... so*who/what* was the 'unauthorized
sender'? and
That sounds like a likely cause right there. Why are you doing that?
Wow! So
On 06/08/2020 11:54 AM, Tom Horsley wrote:
I keep asking for people to point me to the huge list
of exploits that certainly must exist given all the
horrors expressed about running as root.
No one has ever been able to tell me where to find it.
This is because the problem with running as root
On Mon, Jun 8, 2020, at 10:54 AM, Tom Horsley wrote:
> I keep asking for people to point me to the huge list
> of exploits that certainly must exist given all the
> horrors expressed about running as root.
>
> No one has ever been able to tell me where to find it.
Don't know about expolits, but
I keep asking for people to point me to the huge list
of exploits that certainly must exist given all the
horrors expressed about running as root.
No one has ever been able to tell me where to find it.
___
users mailing list -- users@lists.fedoraproject.
On Mon, Jun 08, 2020 at 12:41:03PM -0400, R. G. Newbury wrote:
> Wow! So running as root causes error messages? Pull the other leg, it has
> bells on it!
>
> And why? Because this was immediately after a clean install to a brand new
> drive, while I was still running upgrades and transferring file
On 2020-06-07 4:46 p.m., From: Samuel Sieb wrote:
On 6/7/20 10:31 AM, R. G.
Newbury wrote:
It was apparently something to do with selinux. I usually disable
selinux as the first or second thing I do to a new install. I forgot to
do that.
That should never be necessary.
Well obviously, it WAS
On Sun, 2020-06-07 at 12:51 -0700, Samuel Sieb wrote:
> That sounds like a likely cause right there. Why are you doing that?
Doctor, doctor, it hurts when I do this.
Then stop doing that.
But I want to.
Then you'll have to learn put up with the pain.
--
uname -rsvp
Linux 3.10.0-1127.10.1.el7
On 6/7/20 10:31 AM, R. G. Newbury wrote:
It was apparently something to do with selinux. I usually disable
selinux as the first or second thing I do to a new install. I forgot to
do that.
That should never be necessary.
A quick edit to /etc/selinux/config and a reboot solved removed the
anno
On Sat, 6 Jun 2020 10:30:04 -0600 Jerry James wrote
On Fri, Jun 5, 2020 at 9:54 PM R. G. Newbury wrote:
> Brand new Fedora 32 KDE spin installation. Seems to work nicely, except:
>
> I have an error notification popping up, every hour, in the bottom right
> corner of the screen:
>
> Plasma Desk
On Fri, Jun 5, 2020 at 9:54 PM R. G. Newbury wrote:
> Brand new Fedora 32 KDE spin installation. Seems to work nicely, except:
>
> I have an error notification popping up, every hour, in the bottom right
> corner of the screen:
>
> Plasma Desktop Workspace (and the minutes since the message was po
Hi all,
Brand new Fedora 32 KDE spin installation. Seems to work nicely, except:
I have an error notification popping up, every hour, in the bottom right
corner of the screen:
Plasma Desktop Workspace (and the minutes since the message was posted,
or the time, hourly of a previous message)
25 matches
Mail list logo
