Noticed that this bug is still marked as "incomplete" - do you need any
more information?
--
ACL covering all IPv4 addresses is broken in 2.2.1
https://bugs.launchpad.net/bugs/235653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Chuck,
version 2.2.1-2.1ubuntu7.2~ppa1 seems to have fixed the ACL bug.
regards,
- Charles
--
ACL covering all IPv4 addresses is broken in 2.2.1
https://bugs.launchpad.net/bugs/235653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I tried the package in your PPA on 2008-06-30 (see above), and as far as
I can tell, the patch included in 2.2.1-2.1ubuntu7.2~ppa1 fixes this bug
(that is, I can now use 0.0.0.0/0 as an ACL entry instead of having to
use two separate 1-bit netmasks).
(Should I set the status to "confirmed" myself?
Excellent. Thanks for handling this!
--
ACL covering all IPv4 addresses is broken in 2.2.1
https://bugs.launchpad.net/bugs/235653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
ne to exploit any
potential holes in the NUT ACL code.
Hope that helps.
--
- Charles Lepple
--
[SRU] ACL covering all IPv4 addresses is broken in 2.2.1
https://bugs.launchpad.net/bugs/235653
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Aug 26, 2008, at 8:11 PM, Steve Langasek wrote:
> Hi Charles,
>
> Well, most sysadmins that I know, including the sysadmin that is
> me :),
> prefer security in depth and don't want an either-or choice between
> application-level and system-level ACLs.
Understood, but at the very least, appl
Martin,
I apologize for making things confusing. Let me try and simplify it
somewhat:
tripplite_usb and bestups are two of the hardware-specific drivers, and
they won't stick around if the corresponding hardware (old Tripp-Lite
gear, or Best Power, respectively) isn't present on the system. So th
Public bug reported:
Binary package hint: apport
1) $ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04
2) $ apt-cache policy apport
apport:
Installed: 0.108.2
Candidate: 0.108.2
Version table:
*** 0.108.2 0
500 http://us.archive.ubuntu.com hardy-updates/main Packag
Public bug reported:
Binary package hint: nut
$ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04
$ apt-cache policy nut
nut:
Installed: 2.2.1-2.1ubuntu7
Candidate: 2.2.1-2.1ubuntu7
Version table:
*** 2.2.1-2.1ubuntu7 0
500 http://us.archive.ubuntu.com hardy/main Pa
As a follow-up to the discussion here, libwrap replaces the old NUT ACL
functionality in the upcoming nut-2.4.0 release. This provides
application-level connection filtering using a fairly well-known ACL
syntax.
--
[SRU] ACL covering all IPv4 addresses is broken in 2.2.1
https://bugs.launchpad.ne
On Mar 13, 2009, at 4:42 PM, Martin Pitt wrote:
> Hm, I'm at the end of my wisdom here as well. Perhaps you can try
> starting ups with ulimit -c unlimited, so that you'll get core files?
> (1) does that work with apport enabled? (2) does that work after sudo
> /etc/init.d/apport stop?
Some inter
The hardware for tripplite_usb isn't hooked up to that computer at the
moment, but I tried simulating a crash on /lib/nut/bestups, /lib/nut
/usbhid-ups, /sbin/upsd and /sbin/upsmon. None of those generated any
output in /var/log/apport.log
Just to see if apport was working, I killed /usr/sbin/coll
test just by installing the core
asterisk package along with asterisk-rate-engine and its dependencies.
--
- Charles Lepple
--
rate-engine fails to load due to missing symbol
https://bugs.launchpad.net/bugs/52290
You received this bug notification because you are a member of Ubuntu
Bugs, which
I also saw the same bug as Robert when running edgy, and now when I
install asterisk-rate-engine on feisty, I get a similar error message:
Apr 7 15:59:24 WARNING[8002] loader.c:
/usr/lib/asterisk/modules/rate_engine.so: undefined symbol: ast_load
Apr 7 15:59:24 WARNING[8002] loader.c: Loading m
On 3/30/07, Paul Libert wrote:
> Please find hereafter a diff file that correct the problem.
> All other file including seems to have been corrected in the
> same way.
Excellent, that patch worked. Thanks!
In case anyone else has the same problem, I removed
/usr/src/modules/zaptel, untarred zap
Public bug reported:
Binary package hint: zaptel-source
just upgraded from edgy to feisty, and apparently m-a can't find
linux/config.h:
$ sudo module-assistant -t a-i zaptel
[...]
CC [M] /usr/src/modules/zaptel/zaphfc.o
/usr/src/modules/zaptel/zaphfc.c: In function ‘hfc_findCards’:
/usr/src/
Chris and Christian, thanks for working on this!
For xenial, looks like this debian/ patch might have gotten dropped
(other half of the 52--nut-usbups.rules renaming), which might be
causing the build failure: https://anonscm.debian.org/cgit/collab-
maint/nut.git/commit/?id=b0b61548a47b153b1ce6205
Simon, can you check whether the SYSFS/ATTR comment from the Debian bug
applies? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600#10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title
Patch for xenial:
https://launchpadlibrarian.net/300873279/nut_2.7.4-0ubuntu6~xenial~libusb1~gb0e1758_2.7.4-0ubuntu7~xenial~libusb1~gb0e1758.diff.gz
I haven't tested the patch for trusty, but I assume it would be similar
since the udevd binary has the same name.
Uploaded to PPA:
https://launchpad
I uninstalled NUT on xenial, rebooted, confirmed that ownership was
root:root, enabled xenial-proposed, and installed nut-server
2.7.2-4ubuntu1.2. The ownership was successfully changed to root:nut.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You receiv
I did a quick check on Ubuntu 16.04, but I don't have that box in front
of me at the moment. Pretty sure it was up-to-date, so using version
0.8.12-3.
Notes just added to Debian bug #867588:
"So far, I have not observed any failures after removing the offending
lines ("sqlalchemy >= 0.6, <= 0.7.1
@william-gallaf, likely related.
While the patch mentioned in comment #6 above will prevent the segfault,
it also prevents the driver from determining whether some APC
workarounds need to be applied:
https://github.com/networkupstools/nut/blob/master/drivers/apc-hid.c#L40
Which size Back-UPS ES
Confirmed that this affects xenial as well.
** Tags added: xenial
** Changed in: nut (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540008
Title:
USB permi
Public bug reported:
1) $ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
2) nut-server: 2.7.1-1ubuntu1; udev: 204-5ubuntu20.15
3) On a fresh install of Ubuntu 14.04 (amd64), I installed the nut-
server package while the UPS was already connected via USB. After
installat
@davis65536: I think we might have a lead on this. Are you running in a
VM?
https://github.com/networkupstools/nut/issues/258
The APC portion of usbhid-ups expects that if it can open the device, it
can read the string descriptors. Your system is printing "unknown" for
the Manufacturer, Product a
Since you only have one UPS, I would recommend removing the extra "-x"
options (this prevents problems down the road if a new kernel assigns a
different bus number). I believe the regex matcher is case-sensitive, so
the "051D" does not match.
Interestingly enough, we did have another recent unrepr
26 matches
Mail list logo
