SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Funny also
to be able to run init , you need to be root (you've put a # in front), so whats the point of going into root again?
And then, on a lot of distro like debian and i bet a lot others, you fortunatly need root password to enter single user mode.
So it doesn't work...
Yes funny, suggesting that you are using software not really understanding how it works:
When you see GRUB menu with choices (SUSE, Failsafe, Floppy) add (this is possible - under choice name you will see sign and line:
|____________
you can write there...
init 1
then because this is singe mode, you will be not asked for root password (I hope that you can grasp meaning of this)
simply mount /etc and blank root password
well this is known so no reason to explain one more time
Now you're talking of grub, not the same!
And still on my grub on my machines which have a default install... it is not possible, you need to provide the password..
must be specific to suse..
yup, you are right, the one (suse) distributed by Novell.
If you can't do this, call Novell, they will explain it with pictures how to append init 1 to first grub menu before you boot kernel.
At this point you don't need password.
Quote:
Now you're talking of grub, not the same!
And still on my grub on my machines which have a default install... it is not possible, you need to provide the password..
of course I am talking about grub (this is not dirty trick). This option allow to boot installed kernel in specific mode. This (init 1) is precisely designed for such mishaps.
can't help you, read more about password recovery
In GRUB, all boot parameters can be changed prior to booting. For example, errors made when editing the menu file can be corrected in this way. Boot commands can also be entered interactively over a kind of input prompt (see Section 8.3.1.3, “Editing Menu Entries during the Boot Procedure”). GRUB offers the possibility of determining the location of the kernel and the initrd prior to booting. In this way, you can even boot an installed operating system for which no entry exists in the boot loader configuration.
In the graphical GRUB boot menu, select the operating system to boot with the arrow keys. If you select a Linux system, you can enter additional boot parameters at the boot prompt. To edit individual menu entries directly, press Esc to exit the splash screen and press E. Changes made in this way only apply to the current boot procedure and are not adopted permanently.
this is exactly what I was suggesting. This way you can appent init 1
and boot kernel in single mode (without password)
So you do have strange distribution (this can be done with any distro. See reasons above), if you are unable to do this.
I am o.k. (not sure about you)
You seem to have strong deficency of memory (yours, not your machine), so I recall what you were saying, and what I had quoted.
Code:
run
#init 1
and you will be logged as root (single mode) and without even asking about password! Jeezz
This is stupid and you were not mentionning grub.
In any case, with my strange linux distro (called debian have a look), both of your methods fail completly. So I guess this old insecurity is still present in your amazing distribution (Novell? humm.. no comment)
I don't want to waste my time talking with you anymore, just wanted to clear things, go back to your leet mac hacking, have fun.
ps:
It's not because you were not precise/wrong that you need to be arrogant.
I am loosing patience:
my first notion about init 1 was to answer this:
Quote:
#Originally Posted by abisko00
I would rather not give instructions how to crack a system. How do we know that gamesfan9000 is talking about his own machine?
then I said this:
Quote:
Ever heard about runlevels?
run
#init 1
and you will be logged as root (single mode) and without even asking about password! Jeezz
do you understand the context?
where did I mentioned multiuser level?
I said
"run init 1"
and this is corect statement: you actually run init 1 if appended to GRUB. So my statement is correct. That is all.
By the way can you append variables to GRUB as Novell states or you do have something seriously messed up?
All of this security stuff...I think the paranoid people, and it's not terrible to be paranoid, should disable booting from their CDROM by way of a BIOS password, and restrict their kernels. That should pretty much stop anyone from accessing a system they don't own, right??
That's my
All of this security stuff...I think the paranoid people, and it's not terrible to be paranoid, should disable booting from their CDROM by way of a BIOS password, and restrict their kernels. That should pretty much stop anyone from accessing a system they don't own, right??
That's my
* set a bootloader password
* set the boot order so that hard drive boots first (before CD, floppy, USB, network, etc.)
* set a BIOS password
* and physically lock the case with a decent lock so they don't clear the CMOS or remove the drive
Yes, pretty much exactly what I said but thank you for being more precise for those who might not have understood me. I didn't go so far as the case lock though. If someone is going to disassemble my computer in my house, I may have bigger problems to deal with!!!
should disable booting from their CDROM by way of a BIOS password, and restrict their kernels. That should pretty much stop anyone from accessing a system they don't own, right??
remove battery for a minute and BIOS password is reset and all settings restored to factory defaults.
So one can secure box only by preventing physical access.
However: first question was about resetting root password, not about security.
Again, in the case of pulling the battery, you have to open the tower. If you're dealing with that type of situation - as opposed to someone just dropping in a bootable CD or using boot options - then you need to find a new place to put your computer!
Yes, this was about resetting a password but it sidetracked a bit...maybe someone learned something they didn't plan on learning.
Again, in the case of pulling the battery, you have to open the tower. If you're dealing with that type of situation - as opposed to someone just dropping in a bootable CD or using boot options - then you need to find a new place to put your computer!
either someone has access to your box, then BIOS options are worthless, or not, then BIOS options are waste of time.
Protecting against access to CDROM suggests that there is access to the box, in this case BIOS password will not protect against anything.
Booting from CD and accesing system requires time. If someone has that much time, then opening box is not a big deal.
abisko00: never forget a cardinal rule about the Internet: "On the Internet, nobody can tell if you're a dog". Maybe gamesfan9000 is a most evil cracker, maybe he's just a newbie who hasn't learned the Linux way yet, and maybe he is a dog. If we all assumed the first assumption, there'd be no point to having this site; any piece of advice might support some dark and evil scheme. Let it go, abisko00, let it go...
This is an excellent response to any frantic suspicion Internet viewer. Yes, we have to do our best to avid the Hackers trap, but not on expense on Internet at large which become a part of our daily life.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.