schroot crash at login for dapper

Bug #135397 reported by whtet
6
Affects Status Importance Assigned to Milestone
schroot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: schroot

dapper
----------
root@dapper:~# schroot -u whtet
I: [schroot] (root->whtet) Running login shell: "/usr/bin/schroot"
E: Could not exec "-schroot": No such file or directory
E: Session failure: Child exited abnormally with status '1'
root@dapper:~#

feisty
--------
root@feisty:~# schroot -u whtet
I: [default chroot] (rootâwhtet) Running login shell: â/bin/bashâ
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

whtet@feisty:~$

I have not tested the schroot for edgy.

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

Revision history for this message
Roger Leigh (rleigh) wrote :

I'm not entirely sure I am getting the point of this bug. Is there a bug at all here?

schroot gets the login shell from the passwd database using getpwuid/getpwnam. In the first case, it appears that the shell is set to /usr/bin/schroot, which unsurprisingly doesn't exist inside the chroot, so the session fails. In the second case, it's running a bash login shell (I'm assuming a different passwd database here, or there is a nasty bug!), though I'm not sure where the sudo message comes from unless you added some sudo use to your .bash_profile or something.

Regards,
Roger

Daniel T Chen (crimsun)
Changed in schroot:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.