[Touch-packages] [Bug 1810129] Re: blake2b512 / sha3-512 invalid digest type
> did you try to use sha3-512 and did that work? please see the initial report: > or 'default_md = sha3-512' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1810129 Title: blake2b512 / sha3-512 invalid digest type Status in openssl package in Ubuntu: Incomplete Bug description: cosmic | openssl 1.1.1-1 Since 1.1.1.a-1 provides support for blake2b512 / sha3-512 it would be expected such to work when generating certificates which however does not. OpenSSL> list -digest-commands blake2b512 blake2s256 gost md4 md5 mdc2 rmd160 sha1 sha224 sha256 sha3-224 sha3-256 sha3-384 sha3-512 sha384 sha512 sha512-224 sha512-256 shake128 shake256 sm3 OpenSSL> list -digest-algorithms ... BLAKE2b512 ... SHA3-512 ... Steps to reproduce: in openssl_ca.conf set 'default_md = blake2b512' or 'default_md = sha3-512' generating a certificate ends with 'error:100C508A:elliptic curve routines:pkey_ec_ctrl:invalid digest type:crypto/ec/ec_pmeth.c:327:' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1810129/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
After having upgraded the host to: unbuntu disco (19.04) | kernel 5.0.0-13 | aa 2.13.2-9 | systemd 240-6 the issue is still present -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
adding cross reference https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916639#85 > I think that disabling AppArmor by default for new LXC containers for Buster would be an OK-ish fallback option, if nothing else can realistically be made to work in time for the freeze; that would be sad, but it would not be a regression vs. Stretch. ** Bug watch added: Debian Bug tracker #916639 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916639 -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
Whilst 'lxc.apparmor.profile: unconfined' appears the only way to keep unprivileged lxc guests with systemd v240 alive it defeats the purpose of AppArmor. Notwithstanding, the tail riding on this bug https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622 https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
https://github.com/lxc/lxd/issues/5439#issuecomment-461257784 > The fix in LXD is only partial because there's currently no safe way for us to fix that for privileged containers due to an apparmor parser bug that the AppArmor team is still working on. So we've made the change only to the unprivileged policy for now as the AppArmor bug isn't causing too much damage in that case. There's no such distinction in profile in LXC, so putting those same lines in the LXC policy would allow every user to bypass all mount protections, which isn't acceptable from a security point of view. So the LXC fix is effectively blocked on the AppArmor security bug being resolved first. ** This bug is no longer a duplicate of bug 1813622 systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd ** Bug watch added: LXD bug tracker #5439 https://github.com/lxc/lxd/issues/5439 -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1814986] [NEW] lxd/apparmor: Tweak default set of rules
Public bug reported: branches cosmic & disco the impact of current lxc aa rules in conjunction with systemd v240 is outlined here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10 Whilst LXC committed the patch to its master https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f it has not arrived downstream and thus would be appreciated to be merged, both in cosmic and disco since impacting users of both branches, e.g. arch linux guest that already deploy systemd v240 without this patch particular ubuntu patch https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1814986 Title: lxd/apparmor: Tweak default set of rules Status in lxc package in Ubuntu: New Bug description: branches cosmic & disco the impact of current lxc aa rules in conjunction with systemd v240 is outlined here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10 Whilst LXC committed the patch to its master https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f it has not arrived downstream and thus would be appreciated to be merged, both in cosmic and disco since impacting users of both branches, e.g. arch linux guest that already deploy systemd v240 without this patch particular ubuntu patch https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1814986/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
*** This bug is a duplicate of bug 1813622 *** https://bugs.launchpad.net/bugs/1813622 ** This bug has been marked a duplicate of bug 1813622 systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
This issue accelerating/cascading to the extent that that the lxc arch linux guest is now entirely dead https://bugs.archlinux.org/task/61428 -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
Some further input from the lxc dev team: > What systemd wants to do is the equivalent of executing mount --make-rslave / > on the commandline. The syscall from systemd specifically AFAICT is: > mount(NULL, "/", NULL, MS_REC|MS_SLAVE, NULL); As for the AppArmor profile rule, see https://github.com/lxc/lxc/blob/master/config/apparmor/abstractions/container-base.in#L94 I've pinged jjohansen from the AppArmor devs on irc about it and am hoping he's gonna find the time to dig into this soon. -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
strace does not seem to be the tool to figure out the info you are asking for. Considering that the pid of the involved processes would be unknown at the time of starting strace. And executing the process(es) from the cli along with strace will not bear fruit for the case. Going back to the log message I would reckon that MOUNT_NAMESPACES is in play, in particular recursive MS_SLAVE. Would be that be supported by AA in general and with the profile in particular? -- 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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] Re: systemd--networkd mounts denied for lxc guest
profile="lxc-container-default-cgns"
profile lxc-container-default-cgns flags=(attach_disconnected,mediate_deleted) {
#include
# the container may never be allowed to mount devpts. If it does, it
# will remount the host's devpts. We could allow it to do it with
# the newinstance option (but, right now, we don't).
deny mount fstype=devpts,
mount fstype=cgroup -> /sys/fs/cgroup/**,
mount fstype=cgroup2 -> /sys/fs/cgroup/**,
}
__
> flags are being used by the mount(2) system call that's failed
Pardon my ignorance as not being sure what you are asking here. I
thought it was obvious from the log
pid=8426 comm="(networkd)" flags="rw, rslave"
--
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/1811248
Title:
systemd--networkd mounts denied for lxc guest
Status in apparmor package in Ubuntu:
New
Bug description:
Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7
Guest Arch Linux | systemd 240.0
After having upgraded in the guest systemd from 239.370 to 240.0 the
host's AA is exhibiting
> audit: type=1400 audit(1547125168.853:722): apparmor="DENIED"
operation="mount" info="failed flags match" error=-13 profile="lxc-
container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw,
rslave"
and the guest
> systemd-networkd.service: Failed to set up mount namespacing: Permission
denied
> systemd-networkd.service: Failed at step NAMESPACE spawning
/usr/lib/systemd/systemd-networkd: Permission denied
According to lxc bug tracker https://github.com/lxc/lxc/issues/2778
> While we'd like to allow such mounts we cannot do so until the
apparmor_parser is fixed to handle them correctly.
other cross references
https://github.com/systemd/systemd/issues/11371
https://bugs.archlinux.org/task/61313
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1811248] [NEW] systemd--networkd mounts denied for lxc guest
Public bug reported: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission > denied > systemd-networkd.service: Failed at step NAMESPACE spawning > /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 ** Affects: apparmor (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/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+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 1810129] [NEW] blake2b512 / sha3-512 invalid digest type
Public bug reported: cosmic | openssl 1.1.1-1 Since 1.1.1.a-1 provides support for blake2b512 / sha3-512 it would be expected such to work when generating certificates which however does not. OpenSSL> list -digest-commands blake2b512 blake2s256 gost md4 md5 mdc2 rmd160 sha1 sha224 sha256 sha3-224 sha3-256 sha3-384 sha3-512 sha384 sha512 sha512-224 sha512-256 shake128 shake256 sm3 OpenSSL> list -digest-algorithms ... BLAKE2b512 ... SHA3-512 ... Steps to reproduce: in openssl_ca.conf set 'default_md = blake2b512' or 'default_md = sha3-512' generating a certificate ends with 'error:100C508A:elliptic curve routines:pkey_ec_ctrl:invalid digest type:crypto/ec/ec_pmeth.c:327:' ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: digest -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1810129 Title: blake2b512 / sha3-512 invalid digest type Status in openssl package in Ubuntu: New Bug description: cosmic | openssl 1.1.1-1 Since 1.1.1.a-1 provides support for blake2b512 / sha3-512 it would be expected such to work when generating certificates which however does not. OpenSSL> list -digest-commands blake2b512 blake2s256 gost md4 md5 mdc2 rmd160 sha1 sha224 sha256 sha3-224 sha3-256 sha3-384 sha3-512 sha384 sha512 sha512-224 sha512-256 shake128 shake256 sm3 OpenSSL> list -digest-algorithms ... BLAKE2b512 ... SHA3-512 ... Steps to reproduce: in openssl_ca.conf set 'default_md = blake2b512' or 'default_md = sha3-512' generating a certificate ends with 'error:100C508A:elliptic curve routines:pkey_ec_ctrl:invalid digest type:crypto/ec/ec_pmeth.c:327:' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1810129/+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 1807134] Re: lxc 3.0.2/3 - cannot create root password in privileged container
The issue is due to the lxc logic of applying in deploying in default.conf lxc.idmap = u 0 10 65536 lxc.idmap = g 0 10 65536 in which case the container is ultimately constructed as unprivileged container and such cannot be reverted with a the container specific config. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1807134 Title: lxc 3.0.2/3 - cannot create root password in privileged container Status in lxc package in Ubuntu: Invalid Bug description: Prior filing this as potential bug help was sought but did not yield a remedy https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root- password-in-privileged-container/3425 host - ubuntu cosmic with kernel 4.18.0-12 / systemd 239-7 / apparmor 2.12 Whilst there is no issue with creating a root password via lxc-attach and passwd in an unprivileged container it is however not possible to create a password the same way for a privileged container (tried centos 7 and ubuntu cosmic). Error reported from within the containers: passwd: System error passwd: Authentication token manipulation error Error reported at the host: passwd: PAM audit_log_acct_message() failed: Operation not permitted Next tried with: chroot /container/path/rootfs passwd but that produced the same error. Next tried with: lxc.cap.keep = CAP_AUDIT_WRITE but the container would not boot. Next tried with: lxc.apparmor.profile = unconfined but no remedy. Next switched the kernel to 4.19.7 but no dice either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1807134/+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 1807134] Re: lxc 3.0.2/3 - cannot create root password in privileged container
The issue persists after having upgraded lxc to version 3.0.3 ** Summary changed: - lxc 3.0.2 - cannot create root password in privileged container + lxc 3.0.2/3 - cannot create root password in privileged container -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1807134 Title: lxc 3.0.2/3 - cannot create root password in privileged container Status in lxc package in Ubuntu: New Bug description: Prior filing this as potential bug help was sought but did not yield a remedy https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root- password-in-privileged-container/3425 host - ubuntu cosmic with kernel 4.18.0-12 / systemd 239-7 / apparmor 2.12 Whilst there is no issue with creating a root password via lxc-attach and passwd in an unprivileged container it is however not possible to create a password the same way for a privileged container (tried centos 7 and ubuntu cosmic). Error reported from within the containers: passwd: System error passwd: Authentication token manipulation error Error reported at the host: passwd: PAM audit_log_acct_message() failed: Operation not permitted Next tried with: chroot /container/path/rootfs passwd but that produced the same error. Next tried with: lxc.cap.keep = CAP_AUDIT_WRITE but the container would not boot. Next tried with: lxc.apparmor.profile = unconfined but no remedy. Next switched the kernel to 4.19.7 but no dice either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1807134/+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 1807134] Re: lxc 3.0.2 - cannot create root password in privileged container
** Description changed: Prior filing this as potential bug help was sought but did not yield a remedy https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root- password-in-privileged-container/3425 - host - ubuntu cosmic with 4.18.0-12 kernel / systemd 239-7 / apparmor + host - ubuntu cosmic with kernel 4.18.0-12 / systemd 239-7 / apparmor 2.12 Whilst there is no issue with creating a root password via lxc-attach and passwd in an unprivileged container it is however not possible to create a password the same way for a privileged container (tried centos 7 and ubuntu cosmic). Error reported from within the containers: passwd: System error passwd: Authentication token manipulation error Error reported at the host: passwd: PAM audit_log_acct_message() failed: Operation not permitted - Next tried with: - chroot /srv/lxc/container_name/rootfs passwd + chroot /container/path/rootfs passwd but that produced the same error. - Next tried with: lxc.cap.keep = CAP_AUDIT_WRITE but the container would not boot. - Next tried with: lxc.apparmor.profile = unconfined but no remedy. - Next switched the kernel to 4.19.7 but no dice either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1807134 Title: lxc 3.0.2 - cannot create root password in privileged container Status in lxc package in Ubuntu: New Bug description: Prior filing this as potential bug help was sought but did not yield a remedy https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root- password-in-privileged-container/3425 host - ubuntu cosmic with kernel 4.18.0-12 / systemd 239-7 / apparmor 2.12 Whilst there is no issue with creating a root password via lxc-attach and passwd in an unprivileged container it is however not possible to create a password the same way for a privileged container (tried centos 7 and ubuntu cosmic). Error reported from within the containers: passwd: System error passwd: Authentication token manipulation error Error reported at the host: passwd: PAM audit_log_acct_message() failed: Operation not permitted Next tried with: chroot /container/path/rootfs passwd but that produced the same error. Next tried with: lxc.cap.keep = CAP_AUDIT_WRITE but the container would not boot. Next tried with: lxc.apparmor.profile = unconfined but no remedy. Next switched the kernel to 4.19.7 but no dice either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1807134/+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 1807134] [NEW] lxc 3.0.2 - cannot create root password in privileged container
Public bug reported: Prior filing this as potential bug help was sought but did not yield a remedy https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root- password-in-privileged-container/3425 host - ubuntu cosmic with 4.18.0-12 kernel / systemd 239-7 / apparmor 2.12 Whilst there is no issue with creating a root password via lxc-attach and passwd in an unprivileged container it is however not possible to create a password the same way for a privileged container (tried centos 7 and ubuntu cosmic). Error reported from within the containers: passwd: System error passwd: Authentication token manipulation error Error reported at the host: passwd: PAM audit_log_acct_message() failed: Operation not permitted Next tried with: chroot /srv/lxc/container_name/rootfs passwd but that produced the same error. Next tried with: lxc.cap.keep = CAP_AUDIT_WRITE but the container would not boot. Next tried with: lxc.apparmor.profile = unconfined but no remedy. Next switched the kernel to 4.19.7 but no dice either. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1807134 Title: lxc 3.0.2 - cannot create root password in privileged container Status in lxc package in Ubuntu: New Bug description: Prior filing this as potential bug help was sought but did not yield a remedy https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root- password-in-privileged-container/3425 host - ubuntu cosmic with 4.18.0-12 kernel / systemd 239-7 / apparmor 2.12 Whilst there is no issue with creating a root password via lxc-attach and passwd in an unprivileged container it is however not possible to create a password the same way for a privileged container (tried centos 7 and ubuntu cosmic). Error reported from within the containers: passwd: System error passwd: Authentication token manipulation error Error reported at the host: passwd: PAM audit_log_acct_message() failed: Operation not permitted Next tried with: chroot /srv/lxc/container_name/rootfs passwd but that produced the same error. Next tried with: lxc.cap.keep = CAP_AUDIT_WRITE but the container would not boot. Next tried with: lxc.apparmor.profile = unconfined but no remedy. Next switched the kernel to 4.19.7 but no dice either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1807134/+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 1786995] Re: autodev: adapt to changes in Linux 4.18
lxc 3.0.2 available from the bionic repo, just upgraded and subsequent to ml kernel 4.18.14 ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1786995 Title: autodev: adapt to changes in Linux 4.18 Status in lxc package in Ubuntu: Fix Released Bug description: unprivileged lxc containers do not start with mainline kernel 4.18. This been discussed: - https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html - https://discuss.linuxcontainers.org/t/lxd-3-0-1-with-kernel-4-18/2147/10 and a patch been issued https://github.com/lxc/lxc/commit/3e04a6083eefe0b837db6d1b826721fd985ce052 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1786995/+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 1786995] Re: autodev: adapt to changes in Linux 4.18
Looking forward to 3.0.2 then. Whilst 4.18 is indeed not shipping the thread in the lxc forum at least indicates that there are a few users on the mainline kernel. Like I just updated to 4.18 and then remembered the forum thread. Want to close this as fixed then (with the upcoming release of 3.0.2)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1786995 Title: autodev: adapt to changes in Linux 4.18 Status in lxc package in Ubuntu: Confirmed Bug description: unprivileged lxc containers do not start with mainline kernel 4.18. This been discussed: - https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html - https://discuss.linuxcontainers.org/t/lxd-3-0-1-with-kernel-4-18/2147/10 and a patch been issued https://github.com/lxc/lxc/commit/3e04a6083eefe0b837db6d1b826721fd985ce052 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1786995/+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 1786995] [NEW] autodev: adapt to changes in Linux 4.18
Public bug reported: unprivileged lxc containers do not start with mainline kernel 4.18. This been discussed: - https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html - https://discuss.linuxcontainers.org/t/lxd-3-0-1-with-kernel-4-18/2147/10 and a patch been issued https://github.com/lxc/lxc/commit/3e04a6083eefe0b837db6d1b826721fd985ce052 ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: - unprivileged lxc containers do not start with mainline kernel 4.18. This - been discussed on the mailing list - https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html + unprivileged lxc containers do not start with mainline kernel 4.18. This been discussed: + - https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html + - https://discuss.linuxcontainers.org/t/lxd-3-0-1-with-kernel-4-18/2147/10 + and a patch been issued https://github.com/lxc/lxc/commit/3e04a6083eefe0b837db6d1b826721fd985ce052 ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1786995 Title: autodev: adapt to changes in Linux 4.18 Status in lxc package in Ubuntu: Confirmed Bug description: unprivileged lxc containers do not start with mainline kernel 4.18. This been discussed: - https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html - https://discuss.linuxcontainers.org/t/lxd-3-0-1-with-kernel-4-18/2147/10 and a patch been issued https://github.com/lxc/lxc/commit/3e04a6083eefe0b837db6d1b826721fd985ce052 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1786995/+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 1699478] [NEW] package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-con
Public bug reported: apt-get upgrade is not working ProblemType: Package DistroRelease: Kali 2017.1 Package: console-setup-linux 1.164 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Jun 21 16:11:36 2017 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.19 SourcePackage: console-setup Title: package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kali-rolling third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1699478 Title: package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 Status in console-setup package in Ubuntu: New Bug description: apt-get upgrade is not working ProblemType: Package DistroRelease: Kali 2017.1 Package: console-setup-linux 1.164 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Jun 21 16:11:36 2017 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.19 SourcePackage: console-setup Title: package console-setup-linux 1.164 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1699478/+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 1455937] [NEW] HP 1018 not seen after upgrade to Ubuntu 15.04
Public bug reported: My usb connect Hp Laserjet 1018 worked on Ubuntu 14.04 but after a update through 14.10 and then 15.04, CUPS no longer sees it. I did not test in 14.10 since I went right to 15.04. Here is some of the requested info $ lsmod |grep usb btusb 32768 0 usb_storage69632 1 uas bluetooth 491520 22 bnep,btusb,rfcomm usbhid 53248 0 hid 110592 2 hid_generic,usbhid $ tail -f /var/log/syslog May 17 10:58:07 orac kernel: [ 229.204084] usb 1-12: new high-speed USB device number 17 using xhci_hcd May 17 10:58:07 orac kernel: [ 229.408652] usb 1-12: New USB device found, idVendor=03f0, idProduct=4117 May 17 10:58:07 orac kernel: [ 229.408654] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 17 10:58:07 orac kernel: [ 229.408656] usb 1-12: Product: HP LaserJet 1018 May 17 10:58:07 orac kernel: [ 229.408657] usb 1-12: Manufacturer: Hewlett-Packard May 17 10:58:07 orac kernel: [ 229.408658] usb 1-12: SerialNumber: KP2920Z May 17 10:58:07 orac logger: loading HP Device 001 017 May 17 10:58:07 orac logger: loading hp_laserjet_1018 firmware 001 017 May 17 10:58:11 orac kernel: [ 233.074425] WARNING! power/level is deprecated; use power/control instead May 17 10:58:11 orac udev-configure-printer: add /devices/pci:00/:00:14.0/usb1/1-12 May 17 10:58:11 orac udev-configure-printer: device devpath is /devices/pci:00/:00:14.0/usb1/1-12 May 17 10:58:11 orac udev-configure-printer: Device vendor/product is 03F0:4117 May 17 10:58:17 orac udev-configure-printer: Failed to fetch Device ID May 17 10:58:23 orac /lib/udev/hplj1018: foo2zjs: Missing HP LaserJet 1018 firmware file /lib/firmware/hp/sihp1018.dl May 17 10:58:23 orac /lib/udev/hplj1018: foo2zjs: ...read foo2zjs installation instructions and run ./getweb 1018 May 17 10:58:28 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:28 orac python3: io/hpmud/musb.c 2212: invalid product id string ret=-7 May 17 10:58:33 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:33 orac python3: io/hpmud/musb.c 2217: invalid serial id string ret=-7 May 17 10:58:38 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:38 orac python3: io/hpmud/musb.c 2081: invalid product id string ret=-7 May 17 10:58:43 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:43 orac python3: io/hpmud/musb.c 2086: invalid serial id string ret=-7 May 17 10:58:48 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:48 orac python3: io/hpmud/musb.c 2091: invalid manufacturer string ret=-7 May 17 10:58:48 orac /hp-firmware: hp-firmware[4977]: error: Invalid USB Device ID or USB bus ID. No device found. May 17 10:58:48 orac systemd[1]: Reached target Printer. May 17 10:58:48 orac systemd[1]: Starting Printer. May 17 10:58:53 orac kernel: [ 275.303504] usblp 1-12:1.0: usblp0: USB Bidirectional printer dev 17 if 0 alt 0 proto 2 vid 0x03F0 pid 0x4117 May 17 10:58:53 orac kernel: [ 275.303536] usbcore: registered new interface driver usblp May 17 10:58:53 orac colord-sane: io/hpmud/musb.c 2076: Invalid usb_open: Permission denied $ lsusb Bus 004 Device 002: ID 8087:8000 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard Bus 001 Device 011: ID 0566:4006 Monterey International Corp. Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 001 Device 012: ID 04e6:5410 SCM Microsystems, Inc. SCR35xx Smart Card Reader Bus 001 Device 009: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader Bus 001 Device 006: ID 0424:2602 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 0424:2502 Standard Microsystems Corp. Bus 001 Device 016: ID 22b8:2e33 Motorola PCS Bus 001 Device 002: ID 0e9c: Streamzap, Inc. Streamzap Remote Control Bus 001 Device 017: ID 03f0:4117 Hewlett-Packard LaserJet 1018 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ ls -l /dev/usb/lp* crw-rw 1 root lp 180, 0 May 17 10:58 /dev/usb/lp0 $ ls -l /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 May 17 10:55 /dev/bus/usb/001/001 crw-rw-r-- 1 root root 189, 1 May 17 10:55 /dev/bus/usb/001/002 crw-rw-r-- 1 root root 189, 3 May 17 10:55 /dev/bus/usb/001/004 crw-rw-r-- 1 root root 189, 4 May 17 10:55 /dev/bus/usb/001/005 crw-rw-r-- 1 root roo
