How do I get a Linux install to bypass authentication?
Worf son of Maugg
human intervention.
P.S. Don't care about the security issues so just skip it!
Aardvark Hater
why not just rm -rf /* and get it over with early
--
Aardvark Hater
ICQ: 8440315
10:30am up 11:02, 1 user, load average: 0.47, 0.20, 0.07
Worf son of Maugg
<rose...@iprimus.com.au> wrote:
>Worf son of Maugg wrote:
>
>> I want this box to boot directly to the KDE desktop as "root" w/o any
>> human intervention.
>>
>>
>>
>>
>> P.S. Don't care about the security issues so just skip it!
>
>why not just rm -rf /* and get it over with early
This is typical of my favorite Linux community member the "root Nazi".
The only reason that "root Nazi's" do the whole "su" thing is to
pretend that they are big time system administrators. It's the same
reason little girls play house. They want to pretend to be all grown
up. Why do many in the Linux community take "root" so serious? It
seems to be a Linux cultural thing. I think it has more to do with
tradition then any real technical reason. It only makes sense in big
systems with many users. On a single user system it's overboard. I
would not mind it but I have been discriminated against for working as
root. When I got kicked from a chat room because I'm logged in as
"root"(root wasn't my nick but somehow they could tell). I got so
pissed off that I got rid of ALL accounts except "root" and now I
live, eat, sleep and breath as "root". So far I can telnet, IRC and
ftp as root. Some day I hope to do away with all file permissions and
get rid of all hidden directories. Linux is the only OS where this
would be possible. So don't treat me bad just because I don't want to
play house with you.
Thanks for the help.
Michael Pye
"Worf son of Maugg" <M...@KnowWhere.org> wrote
> >why not just rm -rf /* and get it over with early
>
> This is typical of my favorite Linux community member the "root Nazi".
> The only reason that "root Nazi's" do the whole "su" thing is to
> pretend that they are big time system administrators. It's the same
> reason little girls play house. They want to pretend to be all grown
> up. Why do many in the Linux community take "root" so serious? It
> seems to be a Linux cultural thing. I think it has more to do with
> tradition then any real technical reason. It only makes sense in big
> systems with many users. On a single user system it's overboard. I
> would not mind it but I have been discriminated against for working as
> root. When I got kicked from a chat room because I'm logged in as
> "root"(root wasn't my nick but somehow they could tell). I got so
> pissed off that I got rid of ALL accounts except "root" and now I
> live, eat, sleep and breath as "root". So far I can telnet, IRC and
> ftp as root. Some day I hope to do away with all file permissions and
> get rid of all hidden directories. Linux is the only OS where this
> would be possible. So don't treat me bad just because I don't want to
> play house with you.
Erm, actually it makes sense on any system. You cannot accidentally corrupt
/ destroy things which are vital to your machine, and neither can most
programmes you run unless you are root. As root there is no second chance.
Even windows double checks before allowing you to remove files with a system
attribute!
MP
Topaz_Crow
>
>This is typical of my favorite Linux community member the "root Nazi".
>The only reason that "root Nazi's" do the whole "su" thing is to
>pretend that they are big time system administrators. It's the same
>reason little girls play house. They want to pretend to be all grown
>up. Why do many in the Linux community take "root" so serious? It
>seems to be a Linux cultural thing. I think it has more to do with
>tradition then any real technical reason. It only makes sense in big
>systems with many users. On a single user system it's overboard. I
>would not mind it but I have been discriminated against for working as
>root. When I got kicked from a chat room because I'm logged in as
>"root"(root wasn't my nick but somehow they could tell). I got so
>pissed off that I got rid of ALL accounts except "root" and now I
>live, eat, sleep and breath as "root". So far I can telnet, IRC and
>ftp as root. Some day I hope to do away with all file permissions and
>get rid of all hidden directories. Linux is the only OS where this
>would be possible. So don't treat me bad just because I don't want to
>play house with you.
>
You are just asking for it if your in IRC as root. Servers such as
the chat room you are talking about only do that to protect themselves
and you. Running as root opens yourself up to trojans and other
problems.
Also to mistakes in typeing. For example, you remove everything in
a directory by 'rm -rf ./*' if your running as root and mistakenly
type 'rm -rf /*' your screwed.
But it is your computer. You can screw it up if you want. Don't
expect servers to open themselves to someone that has no regard
for security though.
This is why viruses are rampant for windows. Because users run
as root all of the time.
--
Topaz Crow
No replies by email, sorry.
Reply to alt.anonymous.messages Subject: ATTN: Topaz Crow
PGP: DSS: 0x75D0E0E8 RSA: 0x75D0E0E8 GPG: 0xDD54E4CE
Worf son of Maugg
wrote:
>I want this box to boot directly to the KDE desktop as "root" w/o any
>human intervention.
>
>
>
>
>P.S. Don't care about the security issues so just skip it!
Damn! I'm sorry I never should have flamed back at Aardvark Hater.
Although I do really believe everything I said. I should not have
fired back like that.
Let us get back on the topic. Keepin in mind that we have already
covered the security issues.
How do you get a box to boot directly to the KDE desktop as "root" w/o
any human intervention?
Michael Pye
"Worf son of Maugg" <M...@KnowWhere.org> wrote
> Let us get back on the topic. Keepin in mind that we have already
> covered the security issues.
> How do you get a box to boot directly to the KDE desktop as "root" w/o
> any human intervention?
To be honest, there may not be an easy way. I know I was offered auto-login
service when I installed one distribution, probably mandrake or redhat, but
I doubt it would allow you to do so as root. You might want to look at your
bootscripts (usually in /etc/rc*) but I don't know how far you will get. Of
course it can be done, but I don't know enough to say how...
Plus I'm not sure if I want to help you in such a foolhardy exercise ;P
MP
Root Nazi
<snip>
Truly I used to have th eopinion that you have and trust me I am not
knocking you aor having a dig at you but I learnt the hard way as have a
lot of others in the past.
I do the SU thing all the time and even that isn't foolproof. I am speaking
as a fool here and I can guarantee it isn't foolprof. Now I log in as a
normal user on TTY1 and on TTY 2 I log in as root if I need to or if I need
to run X as root I will do that on tty2 as well.
Thanks I love my new name
--
Root Nazi
ICQ: 8440315
6:18pm up 2 days, 1:25, 1 user, load average: 1.27, 1.27, 1.11
Worf son of Maugg
wrote:
>Worf son of Maugg wrote:
>
><snip>
>
>Truly I used to have th eopinion that you have and trust me I am not
>knocking you aor having a dig at you but I learnt the hard way as have a
>lot of others in the past.
>I do the SU thing all the time and even that isn't foolproof. I am speaking
>as a fool here and I can guarantee it isn't foolprof. Now I log in as a
>normal user on TTY1 and on TTY 2 I log in as root if I need to or if I need
>to run X as root I will do that on tty2 as well.
>Thanks I love my new name
I was looking at "id:5:initdefault:" and changing it to 1 (on RH 7.1
that boots single user mode) but I'm afraid that it would knock down
all authentication. I still need to have remote access through ssh. I
was thinking that there should be a way to pass the user name (root)
and password to the login program at boot up. Some sort of script
maybe? Foolish? I can reinstall in about ten minutes. If you kill
your system with a typo. The fact that you typed "su" just before
makes no difference. So how does using "su" help? It does not. So why
do it?
Michael Pye
"Worf son of Maugg" <M...@KnowWhere.org> wrote
> I was looking at "id:5:initdefault:" and changing it to 1 (on RH 7.1
> that boots single user mode) but I'm afraid that it would knock down
> all authentication. I still need to have remote access through ssh. I
> was thinking that there should be a way to pass the user name (root)
> and password to the login program at boot up. Some sort of script
> maybe? Foolish? I can reinstall in about ten minutes. If you kill
> your system with a typo. The fact that you typed "su" just before
> makes no difference. So how does using "su" help? It does not. So why
> do it?
But I am not sued all the time! about 99% of my typos don't matter because I
don't have root access when I make them. Plus if you have used su, you are
likely to be more careful about the commands you issue because it has
reminded you of what you are doing...
MP
PS. You can reinstall in 10mins? lucky you. What about the work you did
between your last backup and killing your system. Or don't you do anything
useful with your computer? Wouldn't be surprised if you didn't make
backups...
Worf son of Maugg
It's a Quake3 game server and Internet gateway.
Just install RH 7.1, drag the quake stuff over from the
windoze box and the q3a patch. The firewall (gShield) sets up almost
by it self.
Just what are you doing with your Linux box? I boot the box,
run the firewall script and the q3a servers then leave it for anywhere
from 4 to 5 weeks. Unless there is a quake patch. I don't need to
touch it for well over a month. I never do anything that does not
require root access. I guess if you play around moving, coping and
removing files for fun you could get into trouble.
Backups? The q3a/OS stuff is on a disk. I got the network
setup memorized and the server command lines are simple quake stuff.
Why do Linux people act so weird about root? I am beginning to
feel like a Jehovah Witness in Afghanistan! Is root somehow religious?
Will I go to Hell for not respecting it? No. The only thing at stake
is my lame little Quake server.
Michael Pye
"Worf son of Maugg" <M...@KnowWhere.org> wrote
> It's a Quake3 game server and Internet gateway.
> Just install RH 7.1, drag the quake stuff over from the
> windoze box and the q3a patch. The firewall (gShield) sets up almost
> by it self.
> Just what are you doing with your Linux box? I boot the box,
> run the firewall script and the q3a servers then leave it for anywhere
> from 4 to 5 weeks. Unless there is a quake patch. I don't need to
> touch it for well over a month. I never do anything that does not
> require root access. I guess if you play around moving, coping and
> removing files for fun you could get into trouble.
> Backups? The q3a/OS stuff is on a disk. I got the network
> setup memorized and the server command lines are simple quake stuff.
Well, fair enough, but in that case, what is the big hassle in typing "root,
*******" every time you turn it on? Especially if you only do it once every
4-5 weeks! :P
Personally I use Linux as my desktop OS. I do everything with it. And most
people like to be careful with their servers because they hold a lot of
data, often belonging to other people who will want explanations if it goes
missing...
> Why do Linux people act so weird about root? I am beginning to
> feel like a Jehovah Witness in Afghanistan! Is root somehow religious?
> Will I go to Hell for not respecting it? No. The only thing at stake
> is my lame little Quake server.
Mainly it's a bad habit. Working with many workstations and servers to
maintain, other peoples data to safeguard, and the possibility of looking
for a new job if it goes pear shaped has taught REAL sysadmins (so everybody
except windows ones really...) to weald their power with care.
You might be correct that you won't lose much on that machine, but it is a
bad habit to use the root account for general usage, so it is frowned upon
no matter what so it cannot develop into a habit...
MP
stan
page for getty and the ability to override the login program that the
system presents (by default /bin/login) for a specific tty (such as one
of the virtual screens). Haven't tried it but you might replace
/bin/login with /bin/bash (make sure you do this by specifying it on the
command line for invoking /bin/getty instead of putting this into the
/etc/conf.getty file). Only do this for a specific virtual terminal
(try something like tty4). You can modify the /etc/inittab entry for
tty4. Again, haven't tried it and you will probably need to use
/bin/getty instead of /sbin/mingetty which may or maynot work but,
hey... you can try.
Are there other ways? yes but the ones that come to (my) mind involve
writing some C code.
As with everyone else who responded to your posting I too feel this is
not a good idea.
Stan Mlynarczyk
Worf son of Maugg wrote:
>