Default root password for bionicpup?

[haywirepc]

Somehow my chrome installed from repo got borked, trying to install from google provided deb. It prompts for a root password.

Suddenly I realized I never needed this before. Tried woofwoof, puppy, root, no go. Any idea what the default root password is in bionicpuppy linux?

[rockedge]

what happens when in a terminal you type "passwd"?

It must be an Ubuntu installer for chrome asking for a root password.

[williams2]

An unprivleged user, like spot, can not use su to switch to root
if su is not set suid

Code: Select all

# su spot
$ su
su: must be suid to work properly
$ exit
exit
# chmod -v u+s /bin/su
mode of '/bin/su' changed from 0755 (rwxr-xr-x) to 4755 (rwsr-xr-x)
# su spot
$ su
Password:
# whoami
root
# chmod -v u-s /bin/su
mode of '/bin/su' changed from 4755 (rwsr-xr-x) to 0755 (rwxr-xr-x)

But su is a symlink to busybox, so setting the suid bit for su
is really setting the suid bit for busybox.
So busybox and any symlinked busybox applet would allow spot to use any of these programs as if spot were root.
This doesn't matter much if you are running as root anyway.

You could try setting suid by typing or pasting this in a text terminal
(click the "console" icon on the desktop:

Code: Select all

chmod -v u+s /bin/su

Then try installing Chrome.
Then unset the suid bit:

Code: Select all

chmod -v u-s /bin/su

suid might not be what is causing your problem.

[haywirepc]

passwd did it. Not sure why I didn't think of that, I thought you needed the old password to change it. thanks.

I think my chrome issue was caused by installing both the latest from the chrome install website and the one from the puppy repos previously.

Uninstalled all and just installed the one from chrome site, now everything seems to be working nicely.

Thank you all for your help.

[Mike Walsh]

@ haywirepc:-

Goes to prove what I've been trying to get people to understand for years. The official Google-Chrome Linux installer is a .deb package. Now, while .deb packages will install in Pup - most of the time, anyway - the Chrome installer is a bit of a special case. Sure, it'll install.....but in the process of doing so, it buggers up permissions throughout the pup_ro2 layer, and borks CUPS, amongst other things.

This is why I've been building special Puppy-only packages for the last 2 or 3 years; they're built to work with the Puppy way of doing things. Pup may well be 'binary-compatible' with Ubuntu.....but it sure as hell is NOT Ubuntu. There's also the issue of Ubuntu being a true 'multi-user' system, with the .deb package expecting to be installed by a 'user', rather than the root admin user (which Puppy is). It's written with permissions set accordingly, and expecting the use of 'sudo' to permit installation.....

I assume this must be Bionicpup64 we're talking about, yes?


Mike.

[williams2]

expecting the use of 'sudo' to permit installation.....

spot does not seem to be in the /etc/sudoers file
(in my BionicPup64)

Code: Select all

# su spot
$ sudo grep nobody /etc/shadow
spot is not in the sudoers file.  This incident will be reported.
$ sudo su
Password: 
spot is not in the sudoers file.  This incident will be reported.
$ exit
exit
#

I can enable it by editing /etc/sudoers
and adding a line something like this:

Code: Select all

spot	ALL=(root) ALL

Code: Select all

# whoami
root
# su spot
$ whoami
spot
$ grep nobody /etc/shadow
grep: /etc/shadow: Permission denied
$ sudo grep nobody /etc/shadow
Password: 
nobody:!:11141:0:99999:7:::
$ su
su: must be suid to work properly
$ sudo su
sh-4.4# whoami
root
sh-4.4#

Personally, I don't need spot to be allowed to use sudo.

BE CAREFUL EDITING /etc/sudoers
IT CAN PREVENT THE OS STARTING.

I boot to ram with an adrv sfs file, so if I reboot
everything is exactly the same as the last time I booted.