Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #242526
| From | "James H. H. Lampert" <jamesl@touchtonecorp.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Don't try this at home kids |
| Date | 2021-11-30 00:20 +0100 |
| Message-ID | <DoY6d-6NX-1@gated-at.bofh.it> (permalink) |
| References | <DoXtw-6m0-3@gated-at.bofh.it> <DoXDb-6pd-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 11/29/21 2:41 PM, Jeremy Ardley wrote: > P.S. I am totally unconvinced about the arguments for using sudo rather > than running as root. You can do exactly the same damage with sudo as > being root user. > P.P.S The conventional instruction is to use visudo to do the edits. > Which means using Vi, which is another anachronism that should be > humanely put down. That's about the size of it. I've used forty-year-old non-full-screen editors that are a hundred times more intuitive than vi is. And the only reason ROOT access is more dangerous than, say, QSECOFR access on OS/400 (or whatever IBM is calling it this week) is because there's nothing stopping a Linux ROOT from doing things *nobody* should be allowed to do without putting the system into some kind of maintenance mode. I have access to a number of Amazon Linux virtual boxes, that don't like password authentication in general (preferring certificate authentication . . . which authenticates the BOX that is ssh-ing in, but not the WARM BODY between the chair and the keyboard). And if you have a system that doesn't allow ROOT to sign on, and doesn't allow you to SU, then you can achieve the same result by doing sudo bash -- JHHL
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Don't try this at home kids Bob Bernstein <poobah@ruptured-duck.com> - 2021-11-29 23:40 +0100
Re: Don't try this at home kids Jeremy Ardley <jeremy@ardley.org> - 2021-11-29 23:50 +0100
Re: Don't try this at home kids Jude DaShiell <jdashiel@panix.com> - 2021-11-29 23:50 +0100
Re: Don't try this at home kids David Wright <deblis@lionunicorn.co.uk> - 2021-11-30 05:50 +0100
Re: Don't try this at home kids Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2021-11-30 07:00 +0100
Re: Don't try this at home kids Paul Johnson <baloo@ursamundi.org> - 2021-11-30 18:20 +0100
Re: Don't try this at home kids Greg Wooledge <greg@wooledge.org> - 2021-11-30 19:20 +0100
Re: Don't try this at home kids David Wright <deblis@lionunicorn.co.uk> - 2021-12-03 03:50 +0100
Re: Don't try this at home kids Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2021-11-30 20:40 +0100
Re: Don't try this at home kids Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-05 16:40 +0100
Re: Don't try this at home kids Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-05 16:50 +0100
Re: Don't try this at home kids Darac Marjal <mailinglist@darac.org.uk> - 2021-11-30 00:00 +0100
Re: Don't try this at home kids "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2021-11-30 00:20 +0100
Re: Don't try this at home kids Jeremy Ardley <jeremy@ardley.org> - 2021-11-30 00:30 +0100
Re: Don't try this at home kids John Hasler <john@sugarbit.com> - 2021-11-30 01:10 +0100
Re: Don't try this at home kids Bob Bernstein <poobah@ruptured-duck.com> - 2021-11-30 01:10 +0100
Re: Don't try this at home kids Nicholas Geovanis <nickgeovanis@gmail.com> - 2021-11-30 01:30 +0100
Re: Don't try this at home kids Tom Dial <tddial@comcast.net> - 2021-11-30 05:30 +0100
Re: Don't try this at home kids Nicholas Geovanis <nickgeovanis@gmail.com> - 2021-12-03 05:50 +0100
Re: Don't try this at home kids Igor Korot <ikorot01@gmail.com> - 2021-11-30 00:00 +0100
Re: Don't try this at home kids Pierre-Elliott Bécue <peb@debian.org> - 2021-11-30 00:00 +0100
csiph-web