[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version
Ok. This was probably a bug in the update-manager that only manifested symptoms in my case in pcscd. I noticed the only place 'hirsute' was mentioned was in /etc/apt/ is one file, /etc/apt/sources.list.d/system.sources there. Once I changed all instances of 'hirsute' to 'impish' in /etc/apt/sources.list.d/system.sources it was possible to get pcscd installed as normal. So I guess this is either solved or should be relabeled as applying to 'update-manager' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1946235 Title: pcscd won't install due to bad dependency version Status in pcsc-lite package in Ubuntu: New Bug description: # apt install pcscd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pcscd (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Oct 6 17:15:29 2021 InstallationDate: Installed on 2020-06-16 (477 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1946235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version
$ apt policy pcscd libpcsclite1 pcscd: Installed: (none) Candidate: 1.9.1-1 Version table: 1.9.1-1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status libpcsclite1: Installed: 1.9.3-2 Candidate: 1.9.3-2 Version table: *** 1.9.3-2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 1.9.1-1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1946235 Title: pcscd won't install due to bad dependency version Status in pcsc-lite package in Ubuntu: New Bug description: # apt install pcscd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pcscd (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Oct 6 17:15:29 2021 InstallationDate: Installed on 2020-06-16 (477 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1946235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version
Yes, I've done the following. apt update apt upgrade However, qemu is not mentioned in any part of the output from those steps. Though it is installed: $ apt-cache policy qemu-system-x86 | head -n 3 qemu-system-x86: Installed: 1:6.0+dfsg-2expubuntu1 Candidate: 1:6.0+dfsg-2expubuntu1 The problems with pcscd arose after using the update-manager to move from 21.04 to 21.10-beta. pcscd is a dependency for another package which is the main reason for using Ubuntu instead of another distro. Specifically it is a smart card reader needed to interact with an increasing number of government sites and services. After removing qemu-block-extra, I get the following when trying to install pcscd : # apt install pcscd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1946235 Title: pcscd won't install due to bad dependency version Status in pcsc-lite package in Ubuntu: New Bug description: # apt install pcscd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pcscd (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Oct 6 17:15:29 2021 InstallationDate: Installed on 2020-06-16 (477 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1946235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version
I should add that libpcsclite1 is installed but a newer version, # apt install libpcsclite1 Reading package lists... Done Building dependency tree... Done Reading state information... Done libpcsclite1 is already the newest version (1.9.3-2). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1946235 Title: pcscd won't install due to bad dependency version Status in pcsc-lite package in Ubuntu: New Bug description: # apt install pcscd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pcscd (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Oct 6 17:15:29 2021 InstallationDate: Installed on 2020-06-16 (477 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1946235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 510732] Re: OpenSSH server sshd_config PermitRootLogin - NO
It has been fixed upstream: http://www.openssh.com/txt/release-6.9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/510732 Title: OpenSSH server sshd_config PermitRootLogin - NO Status in openssh package in Ubuntu: Opinion Bug description: Ubuntu does not use the root account directly so the PermitRootLogin directive in sshd_config should be set to no by default. This policy is backed by the upstream documentation: For security reasons, it is bad practice to log in as root during regular use and maintenance of the system. Instead, administrators are encour- aged to add a ``regular'' user, add said user to the ``wheel'' group, then use the su(1) and sudo(8) commands when root privileges are re- quired. This process is described in more detail later. From : http://www.openbsd.org/cgi-bin/man.cgi?query=afterboot Bruteforce attacks against the root account are now continual and have been for several years: http://arstechnica.com/security/news/2008/05/strong-passwords-no-panacea-as-ssh-brute-force-attacks-rise.ars If there are shortcomings in the the documentation and guides for sudo or how to use key-based autentication, then they should be addressed there so that this default setting can be set properly. Description:Ubuntu lucid (development branch) Release:10.04 openssh-server: Installed: 1:5.2p1-2ubuntu1 Candidate: 1:5.2p1-2ubuntu1 Version table: *** 1:5.2p1-2ubuntu1 0 500 http://fi.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/510732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 510732] Re: OpenSSH server sshd_config PermitRootLogin - NO
This one can probably be closed since the default is now PermitRootLogin without-password and that's close enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/510732 Title: OpenSSH server sshd_config PermitRootLogin - NO Status in openssh package in Ubuntu: Opinion Bug description: Ubuntu does not use the root account directly so the PermitRootLogin directive in sshd_config should be set to no by default. This policy is backed by the upstream documentation: For security reasons, it is bad practice to log in as root during regular use and maintenance of the system. Instead, administrators are encour- aged to add a ``regular'' user, add said user to the ``wheel'' group, then use the su(1) and sudo(8) commands when root privileges are re- quired. This process is described in more detail later. From : http://www.openbsd.org/cgi-bin/man.cgi?query=afterboot Bruteforce attacks against the root account are now continual and have been for several years: http://arstechnica.com/security/news/2008/05/strong-passwords-no-panacea-as-ssh-brute-force-attacks-rise.ars If there are shortcomings in the the documentation and guides for sudo or how to use key-based autentication, then they should be addressed there so that this default setting can be set properly. Description:Ubuntu lucid (development branch) Release:10.04 openssh-server: Installed: 1:5.2p1-2ubuntu1 Candidate: 1:5.2p1-2ubuntu1 Version table: *** 1:5.2p1-2ubuntu1 0 500 http://fi.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/510732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462758] [NEW] Cannot scp between two remote hosts
Public bug reported: According to the manual page, scp should be able to copy between two remote hosts: scp user@host1:file1 user@host2:. However, it fails after asking for the password for the first host, even though the same file can be copied in two steps: $ scp xx.yy.zz.aa:*.csv xx.yy.zz.bb:. f...@xx.yy.zz.aa's password: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password,keyboard-interactive). lost connection $ scp xx.yy.zz.aa:*.csv . f...@xx.yy.zz.aa's password: configuration_log.csv 100% 935 0.9KB/s 00:00 $ scp *.csv xx.yy.zz.bb:. f...@xx.yy.zz.bb's password: configuration_log.csv 100% 935 0.9KB/s 00:00 $ scp -v xx.yy.zz.aa:*.csv xx.yy.zz.bb:. Executing: /usr/bin/ssh '-x' '-oClearAllForwardings=yes' '-n' '-v' '--' 'xx.yy.zz.aa' 'scp -v' '*.csv' 'xx.yy.zz.bb:.' OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/foo/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to xx.yy.zz.aa [xx.yy.zz.aa] port 22. debug1: Connection established. debug1: identity file /home/foo/.ssh/id_rsa type -1 debug1: identity file /home/foo/.ssh/id_rsa-cert type -1 debug1: identity file /home/foo/.ssh/id_dsa type -1 debug1: identity file /home/foo/.ssh/id_dsa-cert type -1 debug1: identity file /home/foo/.ssh/id_ecdsa type -1 debug1: identity file /home/foo/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/foo/.ssh/id_ed25519 type -1 debug1: identity file /home/foo/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.8 debug1: match: OpenSSH_6.8 pat OpenSSH* compat 0x0400 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-sha1-...@openssh.com none debug1: kex: client-server aes128-ctr hmac-sha1-...@openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA 29:ad:e4:06:40:3a:bb:a2:d7:2c:b3:04:3c:ba:dc:9d debug1: Host 'xx.yy.zz.aa' is known and matches the ECDSA host key. debug1: Found key in /home/foo/.ssh/known_hosts:25 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/foo/.ssh/id_rsa debug1: Trying private key: /home/foo/.ssh/id_dsa debug1: Trying private key: /home/foo/.ssh/id_ecdsa debug1: Trying private key: /home/foo/.ssh/id_ed25519 debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: password f...@xx.yy.zz.aa's password: debug1: Authentication succeeded (password). Authenticated to xx.yy.zz.aa ([xx.yy.zz.aa]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v *.csv xx.yy.zz.bb:. Executing: program /usr/bin/ssh host xx.yy.zz.bb, user (unspecified), command scp -v -t . OpenSSH_6.8, LibreSSL 2.1 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to xx.yy.zz.bb [xx.yy.zz.bb] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/foo/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.8 debug1: match: OpenSSH_6.8 pat OpenSSH* compat 0x0400 debug1:
[Touch-packages] [Bug 1397652] [NEW] /dev/random and /dev/urandom world writeable
Public bug reported: It looks like in 14.04.1 that /dev/random and /dev/urandom are world- writeable. This occurs in at least 14.04.1 Desktop for AMD64 and Server for i386 $ ls -l /dev/*random crw-rw-rw- 1 root root 1, 8 Nov 25 10:44 /dev/random crw-rw-rw- 1 root root 1, 9 Nov 25 10:44 /dev/urandom As far as I know, they should be 664 or 644. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: base-files 7.2ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 30 12:06:43 2014 Dependencies: InstallationDate: Installed on 2014-10-26 (34 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1397652 Title: /dev/random and /dev/urandom world writeable Status in base-files package in Ubuntu: New Bug description: It looks like in 14.04.1 that /dev/random and /dev/urandom are world- writeable. This occurs in at least 14.04.1 Desktop for AMD64 and Server for i386 $ ls -l /dev/*random crw-rw-rw- 1 root root 1, 8 Nov 25 10:44 /dev/random crw-rw-rw- 1 root root 1, 9 Nov 25 10:44 /dev/urandom As far as I know, they should be 664 or 644. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: base-files 7.2ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 30 12:06:43 2014 Dependencies: InstallationDate: Installed on 2014-10-26 (34 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1397652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293525] Re: add apparmor profile for transmission-gtk
** Also affects: transmission (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1293525 Title: add apparmor profile for transmission-gtk Status in “apparmor” package in Ubuntu: Confirmed Status in “transmission” package in Ubuntu: New Bug description: There should be an apparmor profile for transmission-gtk. Attached is a draft for discussion. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor-profiles 2.8.0-0ubuntu38 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Mar 17 13:36:19 2014 InstallationDate: Installed on 2014-03-07 (9 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64+mac (20140307) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=b44a2e83-f3f2-4e70-800d-04964b932c90 ro quiet splash SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1293525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
