Fix pushed to upstream and will be released very soon in tinyproxy
1.8.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036985
Title:
denial of service of too many headers in response
To manage
I was not able to confirm yet,
but since 12.04 is a LTS release, are there any chances to get this fixed in
12.04?
Our virt server is running 12.04, and we would not like to do do an
upgrade before 14.04.
Thanks - Michael
--
You received this bug notification because you are a member of
Sorry, I meant to say: I was not yet able to confirm that it is fixed in
raring.
I am able to confirm that the bug persists in 12.04:
kvm-spice won't work with any other graphics card than cirrus.
Cheers - Michael
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi.
Thanks for the report and the patch!
And sorry for the long delay.
I have made minor modifications to the patches.
(will attach next).
I have to admit though, that I did not quite understand the problem though.
The seeding of the hash seems reasonabe in any case, but for, the loading of
Created attachment 63
updated version of the header limiting patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036985
Title:
denial of service of too many headers in response
To manage
To be quite clear: I see the danger of hash collisions and also
understand the risk of higher CPU consumption when the hashes collide
since behind a hash, we have a linear list in the bucket.
But since the hashofheaders is currently only built of 32 buckets,
(i.e. a 5 bit hash), with a big number
Created attachment 62
updated version of the hash seeding patch
slightly polished version of the seeding patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036985
Title:
denial of service of
indeed.
I have added updated patches to the upstream bug report:
https://banu.com/bugzilla/show_bug.cgi?id=110
Those adhere to coding guidelines and also add configure check for
the newly used functions (time, rand, srand).
These could go upstream.
I need to really understand the problem though
I am also currently struggeling with this behaviour:
I would like to configure bridges with libvirt but start my own universal
dnsmasq separately.
iirc, earlier versions of libvirt did not launch dnsmasq (not even for serving
dns), when
the dhcp section was not present in the network xml file.
@Serge,
Could you explain why use of --path can lead to X crashing where lxc-create
without --path is not?
My motivation was: I don't want lxc-create to create the rootfs under
/var/lib/lxc.
I need the stuff to be stored elsewhere.
I thought that the --path option in the template was made
Confirmed: running the same lxc-create command with --trim creates a
directly usable container.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925513
Title:
plymouth should not run in
@Serge,
thanks for your comments.
I have experimented a little more. And I found that --path is indead at
the very least misleading:
If I don't use --path, then the config (snippet) given to lxc-create by
-f is merged with the config that the template creates. If i do use
paht, then the -f file
@Serge,
I might have misready your statement about network config.
I do add nettwork config (veth0, dev=virbr0, etc) manually.
There is no /etc/lxc/lxc.conf in my system.
The reason I used a config file snipped for lxc-create was
exactly to get this network virtualization layer into the container
@Serge,
Could you explain why use of --path can lead to X crashing where lxc-create
without --path is not?
My motivation was: I don't want lxc-create to create the rootfs under
/var/lib/lxc.
I need the stuff to be stored elsewhere.
I thought that the --path option in the template was made
Confirmed: running the same lxc-create command with --trim creates a
directly usable container.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925513
Title:
plymouth should not run in container
To
@Serge,
thanks for your comments.
I have experimented a little more. And I found that --path is indead at
the very least misleading:
If I don't use --path, then the config (snippet) given to lxc-create by
-f is merged with the config that the template creates. If i do use
paht, then the -f file
@Serge,
I might have misready your statement about network config.
I do add nettwork config (veth0, dev=virbr0, etc) manually.
There is no /etc/lxc/lxc.conf in my system.
The reason I used a config file snipped for lxc-create was
exactly to get this network virtualization layer into the container
Hi,
plymouth running in the container prevents me from using
the container at all, it kills my X instead:
I created a 11.10 container with the following lxc-create command on
freshly installed 11.10:
sudo lxc-create -n ubuntu1 -f ./ubuntu1-template.conf -t ubuntu --
--release=oneiric
Hi,
plymouth running in the container prevents me from using
the container at all, it kills my X instead:
I created a 11.10 container with the following lxc-create command on
freshly installed 11.10:
sudo lxc-create -n ubuntu1 -f ./ubuntu1-template.conf -t ubuntu --
--release=oneiric
I think this is a duplicate of bug #857598
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890887
Title:
socksify try to LD_PRELOAD a missing library
To manage notifications about this bug go to:
With the attached patch (on x86_64), socksify does not complain any more
about the missing library.
** Patch added: patch to socksify for 64bit
https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+attachment/2701883/+files/socksify.patch
--
You received this bug notification
bug #890887 seems to be a duplicate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/857598
Title:
socksify fails to run
To manage notifications about this bug go to:
Please ignore the set -x in the patch. I added it only for debugging.
The patch quietens socksify's ERROR: ld.so: ... message.
But it does not finally fix the problem for me:
At least on 11.10, socksify still does not work:
output of socksify bash with set -x in socksify:
** Attachment added: patch to socksify for 64bit without set -x
https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+attachment/2701912/+files/socksify.patch2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This also seems to be a duplicate -- at partially -- of what is
described in bug #767085.
As described in that bug report, placing a symlink fixes socksify for
me:
$ sudo ln -s libc-2.13.so /lib/x86_64-linux-gnu/libc.so
What to do here?
--
You received this bug notification because you are a
also see bug #767085 -- it contains a workaround
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890887
Title:
socksify try to LD_PRELOAD a missing library
To manage notifications about this bug go
Public bug reported:
On my 11.10 64bit box, I get this:
$ cups-config --ldflags
-L/usr/lib/x86_64-linux-gnu
This library search path is default on the 64-bit system anyways.
The negative effect is that this leads to my software build system (for samba)
pulling in the libs that
reside in
Hi Lucas,
thank you for your opinion / estimation!
I don't want to waste anyone's time.
So I just added the yorba ppa to my sources
and updated to 0.10.
This works fine - thanks.
Cheers - Michael
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In the 10.10 shotwell package, this is _not_ fixed (for me):
The patch that is missing from the ubuntu package is describet in comment #27
of yorba bug 2370:
http://trac.yorba.org/ticket/2370#comment:27
The fix consists in requesting the user_photos permission in the
authorization request
Thanks Shahar for the hint,
I am not quite sure how / whether this allows me to mark the bug as
open for the maverick version (0.7.2) while keeping it fixed for other
versions. I don't seem to be able add a specific version of ubuntu or
the shotwell package to the also affects list. I guess I
Hi Alex,
thank you for the explanations!
I don't think that it would be useful to backport newer packages to
maverick.
I personally would like request a SRU, since firstly, it potentially affects
every
user publishing to facebook (when the user has not yet authorized the shotwell
connector and
*** This bug is a duplicate of bug 599450 ***
https://bugs.launchpad.net/bugs/599450
Hi, I have just installed maveric on 64bit.
Kernel is this:
# uname -a
Linux nirvana 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011
x86_64 GNU/Linux
I have copied xml config of a qemu-kvm
I just updated my ubuntu 9.10 after a couple of days today.
The update consisted of a kernel update and a libc update.
Since the update, I can not start my libvirt/kvm virtual machines
any more with virt-manager, nor create new ones.
When I try to start a vm with virt-manager, I get the error
Oops, I just found this in the debian bugs:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550845
And by chance, the same problem has occurred in my case:
I had installed the cgroups-bin package for testing purposes
today, too. And this made my vms fail. I uninstalled the
package and now they
(putting to invalid again)
--
Error starting domain: Unable to deny all devices for vm0: No such file or
director
https://bugs.launchpad.net/bugs/440015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
dardack:
The Listen 0.0.0.0 issue is this:
0.0.0.0 is the ipv4 wild card address that means
listen to all. This was the default when there was
no explicit Listen statement in the config file.
But it does of course also work when you explicitly
state Listen 0.0.0.0 in the config.
But the
I was looking for a reason why Ubuntu kernels dont have CIFS_POSIX_XATTR set?
So the nifty posix acl extensions can never be used with stock kernel.
Should we open a new enhancement bug report for this or was I just not clever
enough searching...
Michael
--
Default ACL not applied on files
I was looking for a reason why Ubuntu kernels dont have CIFS_POSIX_XATTR set?
So the nifty posix acl extensions can never be used with stock kernel.
Should we open a new enhancement bug report for this or was I just not clever
enough searching...
Michael
--
Default ACL not applied on files
38 matches
Mail list logo
