WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: passwd (not) updated successfully  (Read 6837 times)

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: passwd (not) updated successfully
« Reply #15 on: September 24, 2015, 09:51:02 AM »
The sudoers file in dCore is what determines whether su asks for a password.  It would break the dCore script routines if that was changed.

Have you run "sce-update -a" recently and rebooted?

And are you using the latest dCore release?

Offline hiro

  • Hero Member
  • *****
  • Posts: 1229
Re: passwd (not) updated successfully
« Reply #16 on: September 24, 2015, 06:32:23 PM »
yes, i did. i updated again now just to make sure and rebooted again and still i get the same behavior for both passwd and su.
can you not reproduce this?

i mean... put dcore x86 into a vm, load openssh package and run su as any user (without changing sudoers file) and you'll get root access.

i now installed a special VM.
then i only do sce-import openssh and sce-load openssh
and any user can use su to get root without password.

also why would su use the sudoers file that should be for sudo?
« Last Edit: September 24, 2015, 07:03:25 PM by hiro »

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: passwd (not) updated successfully
« Reply #17 on: September 24, 2015, 10:08:43 PM »
Fixed the su command, please download a new dCore x86 from the release area.  Using the busybox version to ask for a password, though by design 'sudo su' does not need a password. 

On my box, /bb/passwd is used as passwd as expected.

I imported libgnutls-deb0-28 and then ran 'sce-update libgnutls-deb0-28' and it said the package was up to date.

I am using a real install on a standard PC, what virtual machine are you using?

Offline hiro

  • Hero Member
  • *****
  • Posts: 1229
Re: passwd (not) updated successfully
« Reply #18 on: September 25, 2015, 03:04:27 AM »
Seems like sce-update would only detect libgnutls-deb0-28 as outdated with the previous release from august.

Perhaps you have /bb in the front of your path? Does your /bin/passwd file get deleted?

I  can't find a su.deb2sce in deb2sce.tar.gz, but I do indeed see a passwd.deb2sce, still it seems that it doesn't get executed successfully?

*edit: I realise there is no su.deb, it comes from login.deb. Of course the tce.installed/login file doesn't delete the su file.

What change did you make? I can't see anything in the git log.

*I tried to debug a bit using dpkg-deb (which is installed, but "dpkg-deb: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory")

after installing liblzma5 I get
dpkg-deb -c coreutils_8.23-4_i386.deb
tar: unrecognized option '--warning=no-timestamp'

I also again have problems posting to the forum multiple times in sequence:
Quote
We're sorry, but we could not fulfill your request for /index.php/board,66/action,post2.html on this server.

You do not have permission to access this server. Before trying again, close your browser, run anti-virus and anti-spyware software and remove any viruses and spyware from your computer.

Your technical support key is: b01f-fd46-b40c-8ddc

*also I'm not getting mail notifications any more when someone replies.
« Last Edit: September 25, 2015, 03:28:02 AM by hiro »

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: passwd (not) updated successfully
« Reply #19 on: September 25, 2015, 08:13:04 AM »
Below is my $PATH

tc@box:~$ echo $PATH
/home/tc/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/bb:/etc/sysconfig/tcedir/ondemand
tc@box:~$

/bin/passwd does get deleted from it's startup script. 

/bin/su has been added in base as a symlink to busybox and does not get overwritten by imported packages.  Git is for changes in the dCore scripts, so base file changes don't get in there.  But I will be more detailed in the release and release candidates thread.

Debian tools are not fully supported, we track and manipulate packages and files much the same as Core but with a different source of binaries. 

It sounds like Debian tar is not installed so busybox tar is being used.  I can add those deps so if there is functionality of dpkg-deb folks can use it.

Sorry, I can't help with the forum issues you are seeing. 

Offline hiro

  • Hero Member
  • *****
  • Posts: 1229
Re: passwd (not) updated successfully
« Reply #20 on: September 25, 2015, 12:39:25 PM »
It's strange that the passwd didn't get overwritten in the older .iso.
Now with last .iso everything is as you say. passwd gets deleted while a link to busybox su gets created.
One thing is still strange with busybox su: if you put no password su segfaults on enter.
« Last Edit: September 25, 2015, 12:41:02 PM by hiro »

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: passwd (not) updated successfully
« Reply #21 on: September 25, 2015, 02:30:37 PM »
When I enter su and just enter at the password prompt, it just replies "incorrect password" on my box. 
« Last Edit: September 25, 2015, 02:32:35 PM by Jason W »

Offline hiro

  • Hero Member
  • *****
  • Posts: 1229
Re: passwd (not) updated successfully
« Reply #22 on: September 25, 2015, 04:55:55 PM »
it happens when the password is not set (* or ! in /etc/shadow)

Offline hiro

  • Hero Member
  • *****
  • Posts: 1229
Re: passwd (not) updated successfully
« Reply #23 on: September 26, 2015, 05:15:07 AM »
It's strange. I updated my other server to latest initramfs and it seems like there the /usr/local/tce.installed/passwd didn't get run successfully, because I still have passwd pointing to the passwd provided by openssh-server.
packages have been updated using sce-update -a

Also there's a line 'rm /usr/bin/chpasswd', but it has no effect cause chpasswd and chgpasswd is in /usr/sbin/
« Last Edit: September 26, 2015, 05:18:42 AM by hiro »

Offline hiro

  • Hero Member
  • *****
  • Posts: 1229
Re: passwd (not) updated successfully
« Reply #24 on: September 26, 2015, 05:23:12 AM »
Could it be that there is some bug when multiple sce have passwd and get loaded one after the other?
To support this thesis: Openssh gets loaded after lvm2 here. lvm2 also has passwd (I think there the delete must have worked).
« Last Edit: September 26, 2015, 05:28:38 AM by hiro »

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: passwd (not) updated successfully
« Reply #25 on: September 26, 2015, 05:56:24 AM »
Added symlinks to busybox for passwd and chpasswd in base, current changes uploaded to release candidates.  Adjusted startup script for compatibility with current release.

The startup scripts for packages get run by the first SCE loaded that contains the package.

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: passwd (not) updated successfully
« Reply #26 on: September 26, 2015, 08:08:16 AM »
I consider this a temporary fix as I would like to get passwd to work like we do with other packages that need adjustments.