DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Setting the root password
- Thread starter sidww2
- Start date
kristoff125
Member
What exactly is a root password?
The Unix Superuser password..
Think Administrator password on a Windows box..
http://en.wikipedia.org/wiki/Superuser
The password for the root/ super user account.(I have a rooted droid) Right now when I su, it doesn't ask me for a password.
it wont it doesnt need to.
droidman101
Member
thats sorta the reason that it makes the popup come up for all su commands unless you hit remember
Has anyone found a way to set the root password? For those wondering why we want to set a password just google iPhone Rick Roll. That was basically a proof of concept attack that could have been much worse. I'd like to protect my phone from such things and I'm sure you would too.
Thanks,
MajickMan
Thanks,
MajickMan
Then Unroot. As it has been said, you cannot add a password to Root.
Much like newer versions of windows will ask if you want to run an exectuable, even when logged on with an administrator account, your phone does the same thing with busybox, mm, root explorer, setcpu, and more.
If you really want to step things up a notch then you don't run your OS as root/admin. By rooting our phones we set ourselves at risk. By allowing to install from unknown sources we set ourselves at risk. By just installing an app from the market because it looks cool we also set ourselves at risk.
When we install an app that has lots of press coverage that lots of folks have already used we are acting in a more secure manner. The dev might be better known, others would have uncovered something wrong etc.
Any of the apps you install that say they can collect network, browser, and keyboard info could possibly be gathering and sending info you don't want sent. The community is what is keeping things safe.
I'd be interested in knowing what other sorts of safeguards are on the market to prevent keystroke capturing type code from being present in apps. Root isn't needed for that.
All that being said...there's a ton of phones out there. not so many viruses. I feel pretty safe with what I've done with my phone, as well as with my pc. But you never can be 100% sure.
If you really want to step things up a notch then you don't run your OS as root/admin. By rooting our phones we set ourselves at risk. By allowing to install from unknown sources we set ourselves at risk. By just installing an app from the market because it looks cool we also set ourselves at risk.
When we install an app that has lots of press coverage that lots of folks have already used we are acting in a more secure manner. The dev might be better known, others would have uncovered something wrong etc.
Any of the apps you install that say they can collect network, browser, and keyboard info could possibly be gathering and sending info you don't want sent. The community is what is keeping things safe.
I'd be interested in knowing what other sorts of safeguards are on the market to prevent keystroke capturing type code from being present in apps. Root isn't needed for that.
All that being said...there's a ton of phones out there. not so many viruses. I feel pretty safe with what I've done with my phone, as well as with my pc. But you never can be 100% sure.
noobkiller
New Member
Let's clarify ths
Okay, *****cat, let's see why you're noob
I used linux as a developer and administrator of a huge system for the last ten years, but I have to tell that I use android for 3 days, and never had before.
Through these 3 mere days I discovered that android is fundamentally an _exact_ linux and, as such, it does impiles the possibility of using unix user accounts and passwords.
The former (user accounts) is a natural part of the system, every app installed to the droid is given an exclusive one. (i must stop here to admit this is a strike of genius, a beautiful way to separate applications' workspace and permissions in such a way as we usually do on web servers hosting multiple domains, virtual hosts). It must be mentioned, that the files which control user accounts under linux (like /etc/passwd) are absent under android, because there is a stub for mapping the android_id to passwd structure. So there are no physical files for this purpose, the stub should populate the values. BUT this behaviour may be altered (i wouldn't like to describe how, it's your fight to figure out).
The latter one is a bit tricky, because android has no system authentication method (like PAM, or such) built in it, hence the only way to change the UID or EUID is to call the corresponding kernel call from a C program. BUT you are welcome to these C programs (including PAM itself), from any of the linux distros around, and after a (really-really) minimal modification they will work on android perfectly.
Thank you for your kind attention
Okay, *****cat, let's see why you're noob
I used linux as a developer and administrator of a huge system for the last ten years, but I have to tell that I use android for 3 days, and never had before.
Through these 3 mere days I discovered that android is fundamentally an _exact_ linux and, as such, it does impiles the possibility of using unix user accounts and passwords.
The former (user accounts) is a natural part of the system, every app installed to the droid is given an exclusive one. (i must stop here to admit this is a strike of genius, a beautiful way to separate applications' workspace and permissions in such a way as we usually do on web servers hosting multiple domains, virtual hosts). It must be mentioned, that the files which control user accounts under linux (like /etc/passwd) are absent under android, because there is a stub for mapping the android_id to passwd structure. So there are no physical files for this purpose, the stub should populate the values. BUT this behaviour may be altered (i wouldn't like to describe how, it's your fight to figure out).
The latter one is a bit tricky, because android has no system authentication method (like PAM, or such) built in it, hence the only way to change the UID or EUID is to call the corresponding kernel call from a C program. BUT you are welcome to these C programs (including PAM itself), from any of the linux distros around, and after a (really-really) minimal modification they will work on android perfectly.
Thank you for your kind attention
kristoff125
Member
Noobkiller first and foremost welcome to the forums. Not sure where you get off calling people noobs when you show up in a forum and resurrect a dead three year old thread to drop worthless knowledge. There is no way to set a root password on Android. Go away troll.
noobkiller
New Member
Hi!
At first I have to say sorry about my behaviour. I was googling for hours, visiting tons of android forums concerning the topic, knowing it has to be possible. This was the last stop of my desperate trip towards the solution and a huge anger overcame my politeness. I think everybody has committed such a fault at least once on a time. Again, I am really sorry, I did not want insult anyone.
Anyway,
I did it on the weekend. I compiled the PAM library, openssh server, and other neccessary tools gathered from Gentoo Linux and installed them on my android system. After configuration (and a bit of magic, of course
), both publickey and keyboard-interactive authentication was being supported on my device (Galaxy S) through ssh. Additionally, the good ol' /bin/login is available, that is, password authentication is also possible directly on the phone.If somebody feels this achievement of mine usable, I gladly share the binaries or the "androidized" source codes. Please contact me on the e-mail address
geza@mine.hu
Best regards,
Géza
PS: I hope this knowledge is not in fact worthless for the community...