Thanks for letting us know, in that case (until really ready) let us
mark this incomplete.
Once re-started please add a team subscriber, answer the questions I
outlined and set it back to new.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry for the lack of status update here, we probably own one from a
desktop perspective. The feature is still something we would like to see
landing but it has disruption potential and Desktop is currently busy
with other things, I don't think we have the capacity to deal with the
integration and
@Rex - hi I see you added a priority tag.
This is waiting for further input/explanation on the open tasks/questions that
I have re-summarized on comment #21. You could either work with the Desktop
team which will own this or do it on your own, but the task is to track those
open things down
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816548
Title:
[MIR] usbguard
To manage notifications about this bug go to:
Thanks Jamie!
>From the MIR Team we had a list of todos in comment #4:
Some are resolved already around the lib/symbols as well as the formerly open
security issues being resolved in the new release.
What is left seems to be:
- Change the current on-install default to block all but host
From
https://bugs.launchpad.net/ubuntu/+source/usbguard/+bug/1855189/comments/2:
"FYI, upstream committed https://github.com/USBGuard/usbguard/pull/378
to address this issue. It is essentially what I mentioned in the bug
description."
If we apply that patch to our usbguard packages, I have no
0.7.5 does not fix bug #1855189 (and code inspection suggests 0.7.6 is
also affected). IMO, bug #1855189 needs to be fixed as part of main
inclusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I found the cause of usbguard becoming unresponsive and filed
https://bugs.launchpad.net/usbguard/+bug/1855189 (with
https://github.com/USBGuard/usbguard/issues/349).
** Bug watch added: github.com/USBGuard/usbguard/issues #349
https://github.com/USBGuard/usbguard/issues/349
--
You received
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => oem-priority
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> > The file is in the normal directory as all other libs (on the current
> > version in Eoan):
> > /usr/lib/x86_64-linux-gnu/usbguard/libusbguard.so.0.0.0
>
> Well, the fact that it's in a subdir there and not directly in
> /usr/lib/x86_64-linux-gnu means it's not in the standard
> The file is in the normal directory as all other libs (on the current version
> in Eoan):
> /usr/lib/x86_64-linux-gnu/usbguard/libusbguard.so.0.0.0
Well, the fact that it's in a subdir there and not directly in
/usr/lib/x86_64-linux-gnu means it's not in the standard LD_LIBRARY_PATH
and
Hi Seb,
thanks for putting effort into this in general - I know it can be rather time
consuming to clean up those review findings. You asked me to look again into
the aspect of the library lacking a symbols file due to the new info presented
above.
The file is in the normal directory as all
> - lacks symbols tracking for libusbguard.so.0
The Debian maintainer responded to that saying
'Usbguard upstream does not give any guarantees for backwards
compatibility for the usbguard library as long as its not version 1.0.
Thats also why the library is installed to
/usr/share//usbguard, to
sorry ignore that about the warning, it's still there, reported to
debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816548
Title:
> dpkg-shlibdeps: warning:
> debian/libusbguard0/usr/lib/x86_64-linux-gnu/usbguard
> /libusbguard.so.0.0.0 contains an unresolvable reference to symbol
> pthread_create: it's
> probably a plugin
> That is concerning as in this case it is not meant to be a plugin.
> Missing dependency?
That
Thanks for the review, I'm going to try to help moving that a bit
forward.
> Not so good:
> - lacks symbols tracking for libusbguard.so.0
I've forwarded that to Debian with a patch now
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931380
> - the current release (since July last year) 7.4 is
I reviewed usbguard 0.7.4+ds-1 as checked into eoan. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
usbguard consists of a daemon which manages the authorization of new USB
devices via udev events. It provides an IPC interface (which by default is
only
Oh, cool, a starting point to work with! Any chance an apt-get install
--reinstall would trip it?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816548
Title:
[MIR] usbguard
To manage
The error happened again after a snapd upgrade. I suspect it isn't
handling the udev trigger events that snapd does particularly well (even
though that is supposed to be safe).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> > Understanding that usbguard is a target for main, I've been running it
> > on my laptop for a little while and can say that there is a real issue
> > with the daemon stopping which causes all USB inserts to fail closed
> > until the daemon is restarted. I've also suspected some external
>
>
Thanks for the review Christian, It seems we have some work to do there,
we will plan some of that for next cycle.
Note that Desktop has not been a driver for the feature request, but we
got first pinged about it by security. GNOME might be integrating it
next cycle though which would create a
As an addendum to the TODOs, after purging it it should no more block
new devices (as it does right now). Which is not fun since the tools to
make them allowed are no more installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Duplication]
Function-wise there seems to be usbauth and usbguard (thanks Seth and Jamie for
adding your early experiences).
None of them is in main yet so it would be no duplication.
Picking among the two projects can be hard as they promise almost the same.
But in terms of upstream activity,
On Tue, Apr 09, 2019 at 11:33:00PM -, Jamie Strandboge wrote:
> Understanding that usbguard is a target for main, I've been running it
> on my laptop for a little while and can say that there is a real issue
> with the daemon stopping which causes all USB inserts to fail closed
> until the
Understanding that usbguard is a target for main, I've been running it
on my laptop for a little while and can say that there is a real issue
with the daemon stopping which causes all USB inserts to fail closed
until the daemon is restarted. I've also suspected some external
keyboard weirdness
Assigned to me for MIR review
** Changed in: usbguard (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816548
Title:
[MIR]
** Description changed:
* Availability
In sync with Debian, built on all architectures
https://launchpad.net/ubuntu/+source/usbguard/0.7.4+ds-1
* Rationale
We want to increase the security of USB devices, GNOME is working on this
feature for next cycle and relying on the
** Description changed:
* Availability
In sync with Debian, built on all architectures
https://launchpad.net/ubuntu/+source/usbguard/0.7.4+ds-1
-
* Rationale
- We want to increase the security of USB devices, GNOME is working on this
feature for next cycle and relying on the
28 matches
Mail list logo
