After installing slitaz to my hard drive, the username & password I set wont let me install any software/access slitaz panel. I can login to my machine, but cant use package manager or any other admin stuff that requires slitaz panel. Even the default "root" does not work. HELP!!!!
Cant install password
(14 posts) (7 voices)- Started 11 years ago by linuxpcplus
- Latest reply from ooseven
- This topic is not resolved
-
mojo
offlineKey Mastertazpanel-1.5.7. tazpkg owns /etc/slitaz/httpd.conf which links the busybox root user password to tazpanel root user password
If the file is bad,force re-install of tazpanel will replace it and fix the problem.
Open terminal
su
password: <your.root.password>
# tazpkg -gi tazpanel --forcedPosted 11 years ago # -
linuxpcplus
offlineMemberThis didnt work. The exact content of the file you mentioned is:
H:/var/www/tazpanel
A:127.0.0.1
D:*
*.cgi:/bin/sh
I:index.cgi
/:root:*I then opened terminal & followed your instructions. The exact output is:
olf@wolf:~$ su
Password:
root@wolf:/home/wolf# #tazpkg -gi tazpanel --forced
root@wolf:/home/wolf#I then rebooted & this still did not fix.
Posted 11 years ago # -
mojo
offlineKey MasterNo commands begin with a # , the shell ignores anything that follows on the same line.
This is why it's used in front of comments in scripts and configuration files.
The # means run the command that follows as user root :
root@wolf:/home/wolf# tazpkg -gi tazpanel --forced
root@wolf:/home/wolf# pkill httpd
root@wolf:/home/wolf# tazpanel startPosted 11 years ago # -
Aleksej
offlineCoder-hobbyistAsterisk (*) as password? Very strange bug/exploit. And it's not worked for me. I'm not changed root password, so only default root:root works. Who also changed root pass?
Posted 11 years ago # -
Bellard
offlineKey MasterSince http://hg.slitaz.org/wok/rev/a6b781a0cffb busybox httpd supports system passwords.
The password asterisk (*) means use system password (in /etc/password or /etc/shadow or PAM or ...)The new tazpanel configuration uses this trick since http://hg.slitaz.org/tazpanel/rev/3a8304862453
The combo new tazpanel (new config with *) + old busybox (no * support) explains this behaviour.
You can install http://mirror.slitaz.org/packages/4.0/busybox-1.18.4.tazpkg to get system password support.
Posted 11 years ago # -
The * worked for me also.
The question still arises: what happened to the actual password and why would/does it not work?
Does the * system password support negate the use of the actual password in slitaz panel
login (the server login) (noting that it (the actual password) works in other dialogs that request root)?Posted 11 years ago # -
Some issues:
I changed the tazpanel password using tazpanel passwd
Now * does not work and the root password does which makes sense considering the nature of * but makes no sense from a system consistency viewpoint especially since the use of * is intended to reflect the tazpanel's use of the system's admin/root password.
I would say synch the tazpanel's 'passwd' option with the use or non use of the new busybox's httpd system password support. Better yet, get rid of the tazpanel passwd option all together and always look to use the system's passwords seeing as tazpanel is a system admin panel.Also, some other issues:
The httpd server remains running after issuing tazpanel stop and so changes to the root password, be they through tazpanel passwd or the system's chpasswd are not reflected in the tazpanel's login since httpd does not reread the the httpd.conf config file.
One has to manually kill the server and start it up again, preferably (if not only) with tazpanel start, in order for the password changes to take affect.
Some clues:
root@slitaz:/home/tux# tazpanel stop
Stopping TazPanel web server...sh: can't kill pid 6707: No such process
root@slitaz:/home/tux# pidof httpd
6715the differences in the pid might explain what's happening.
Overall, in spite of the hiccups, I'm pretty happy with the distro. :)
Posted 11 years ago # -
Finally:
$HOME/.config/slitaz/subox.conf holds the root password in plain text if one decides to save it when requested.
Seemingly not terrible considering the file is readable by root only.
Of course this reasoning would lead us back to plain text passwords in /etc/passwd
and negate the argument for the change to 'x'.?
Posted 11 years ago # -
ooseven
offlineMemberroot@gauthier:/home/ooseven# tazpkg -gi tazpanel --forced
tazpanel-1.5.7 already in the cache : /var/cache/tazpkg/4.0/packagesInstallation of : tazpanel
================================================================================
Copying tazpanel... [ OK ]
Extracting tazpanel... [ OK ]
Extracting the pseudo fs... (lzma) [ OK ]
Saving configuration files for tazpanel... [ OK ]
Installing tazpanel... [ OK ]
Removing all tmp files... [ OK ]
================================================================================
tazpanel (1.5.7) is installed.root@gauthier:/home/ooseven# pkill httpd
root@gauthier:/home/ooseven# tazpanel start
Starting TazPanel web server on port 82... [ OK ]
root@gauthier:/home/ooseven#Installation of : busybox
Copying busybox... [ OK ]
Extracting busybox... [ OK ]
Extracting the pseudo fs... (lzma) [ OK ]
Keep installed GNU utilities ? Saving configuration files for busybox... [ OK ]
Installing busybox... [ OK ]
Removing all tmp files... [ OK ]busybox (1.18.4) is installed.
Still does not work
Posted 11 years ago #
Reply
You must log in to post.
