Bug#942128: installation-guide-amd64: security apt resource
Package: installation-guide-amd64 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? In installation of debian 10, testing, there is bad entry to /etc/apt/sources.list - installation procedure reports error when trying contact old security repository (up to 9). The instalation procedure should use the new one: deb http://security.debian.org testing-security main contrib non-free deb-src http://security.debian.org testing-security main contrib non-free Thank you. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#830775: systemd: systemctl poweroff ask me twice for user and password.
I would prefer if it even does not aks who i am. It should ask for password only. And my second wish is, that i would be able to poweroff even without password as I do in GUI/Gnome. Regards Pavel Michael Biebl napsal(a) dne 11.7.2016 v 14:39: Am 11.07.2016 um 14:33 schrieb Pavel Kosina: Its ssh, putty, dady@linuxbox:~$ systemctl poweroff AUTHENTICATING FOR org.freedesktop.login1.set-wall-message === Authentication is required to set a wall message Multiple identities can be used for authentication: 1. ,,, (dady) 2. ,,, (danca) Choose identity to authenticate as (1-2): 1 Password: AUTHENTICATION COMPLETE === AUTHENTICATING FOR org.freedesktop.login1.power-off === Authentication is required for powering off the system. Multiple identities can be used for authentication: 1. ,,, (dady) 2. ,,, (danca) Choose identity to authenticate as (1-2): Failed to power off system via logind: Spojení bylo přílií Failed to start poweroff.target: Spojení bylo příliš dlouho neaktivní See system logs and 'systemctl status poweroff.target' for details. dady@linuxbox:~$ dady@linuxbox:~$ loginctl show-session $XDG_SESSION_ID Id=5 User=1000 Name=dady Timestamp=Po 2016-07-11 14:30:44 CEST TimestampMonotonic=1861158573 VTNr=0 Remote=yes RemoteHost=192.168.1.101 Service=sshd Thanks for the quick reply. So this is a remote login. That explains why you get the polkit prompt. As you can see, the admin password is asked for two distinct things: For setting a wall message and for the actual poweroff. Both require admin privileges. If you don't want to have the prompt for the wall message, use systemctl poweroff --no-wall That should only give you one polkit prompt. Afaics, everything is working as expected, although I have to admit that entering the credentials twice for the same command is a nuisance. Regards, Michael
Bug#830775: systemd: systemctl poweroff ask me twice for user and password.
Its ssh, putty, dady@linuxbox:~$ systemctl poweroff AUTHENTICATING FOR org.freedesktop.login1.set-wall-message === Authentication is required to set a wall message Multiple identities can be used for authentication: 1. ,,, (dady) 2. ,,, (danca) Choose identity to authenticate as (1-2): 1 Password: AUTHENTICATION COMPLETE === AUTHENTICATING FOR org.freedesktop.login1.power-off === Authentication is required for powering off the system. Multiple identities can be used for authentication: 1. ,,, (dady) 2. ,,, (danca) Choose identity to authenticate as (1-2): Failed to power off system via logind: Spojení bylo přílií Failed to start poweroff.target: Spojení bylo příliš dlouho neaktivní See system logs and 'systemctl status poweroff.target' for details. dady@linuxbox:~$ dady@linuxbox:~$ loginctl show-session $XDG_SESSION_ID Id=5 User=1000 Name=dady Timestamp=Po 2016-07-11 14:30:44 CEST TimestampMonotonic=1861158573 VTNr=0 Remote=yes RemoteHost=192.168.1.101 Service=sshd Scope=session-5.scope Leader=3608 Audit=5 Type=tty Class=user Active=yes State=active IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 LockedHint=no dady@linuxbox:~$ loginctl list-sessions SESSION UID USER SEAT 5 1000 dady c1 116 Debian-gdm seat0 2 1000 dady seat0 3 sessions listed. Thank you Pavel Michael Biebl napsal(a) dne 11.7.2016 v 14:26: How exactly did you trigger the bug? Typically, a systemctl shutdown should be possible (without a password prompt) when you are logged in locally and your session is marked as active. What's the output of $ loginctl show-session $XDG_SESSION_ID $ loginctl list-sessions