[Bug 321102] [NEW] Tor packages too old
*** This bug is a security vulnerability *** Public security bug reported: Tor packages do not seem to be updated in Ubuntu. The list http://packages.ubuntu.com/search?keywords=tor contains only outdated packages. My 8.04installs package tor 0.1.2.19-2, which is one year old by now. This is very bad as Tor is security software, and new versions frequently fix security issues. E.g., the latest version as of this writing (21 January 2009: Tor 0.2.0.33) comes with the following changelog entry: "Fix a heap-corruption bug that may be remotely triggerable on some platforms" (From http://archives.seul.org/or/announce/Jan-2009/msg0.html) In my view, Tor should either be removed from Ubuntu or updated regularly. Thanks Jens ** Affects: ubuntu Importance: Undecided Status: New ** Visibility changed to: Public -- Tor packages too old https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] Re: Security fixes in tor 0.2.0.32 and .33
Many thanks for your quick responses! As I wrote via e-mail already (hoping it would appear here automagically): I'm sorry, but I've never created a debdiff. To be honest I don't think that separate debdiffs are worth the trouble. Tor is under constant development, and lots of bugs (ordinary ones as well as attacks against its anonymity goal) are fixed frequently. In my view, this kind of software requires the use of the newest release. Otherwise, it's just dangerous. I filed a backport request as suggested by Hew McLachlan: https://bugs.launchpad.net/bugs/321520 -- Security fixes in tor 0.2.0.32 and .33 https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] [NEW] Build error: ‘struct bio’ has no member named ‘bi_hw_front_ size’
Public bug reported: Binary package hint: loop-aes-source loop-aes in jaunty is v3.2c. Build via "module-assistant auto-install loop-aes" fails. Changelog for v3.2d contains "Worked around block layer interface breakage on linux-2.6.28-rc kernels." Moreover, Changelog for v3.2e (current version) is "Fix null pointer dereference when loop was used to mount iso9660 CD-ROM image. This new bug was introduced in loop-AES-v3.2d, earlier versions are ok. Thanks to Peter Koek for reporting this issue." Please update to current version. ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] Re: Build error: ‘struct bi o’ has no member named ‘bi_hw_front_si ze’
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for "modprobe loop" I get "Invalid module format" (dmesg shows "loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)". I guess this happens as the jaunty kernel has "CONFIG_BLK_DEV_LOOP=y" whereas the loop-aes README clearly states "Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n." Did the build process via module-assistant ever work under Ubuntu? -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] [NEW] losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Public bug reported: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] Re: losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Added the "P.S." about acpi=off ** Description changed: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). + + P.S. losetup -d behaves as expected if I boot with "acpi=off". -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] Re: Security fixes in tor 0.2.0.32 and .33
Many thanks for your quick responses! As I wrote via e-mail already (hoping it would appear here automagically): I'm sorry, but I've never created a debdiff. To be honest I don't think that separate debdiffs are worth the trouble. Tor is under constant development, and lots of bugs (ordinary ones as well as attacks against its anonymity goal) are fixed frequently. In my view, this kind of software requires the use of the newest release. Otherwise, it's just dangerous. I filed a backport request as suggested by Hew McLachlan: https://bugs.launchpad.net/bugs/321520 -- Security fixes in tor 0.2.0.32 and .33 https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] [NEW] Tor packages too old
*** This bug is a security vulnerability *** Public security bug reported: Tor packages do not seem to be updated in Ubuntu. The list http://packages.ubuntu.com/search?keywords=tor contains only outdated packages. My 8.04installs package tor 0.1.2.19-2, which is one year old by now. This is very bad as Tor is security software, and new versions frequently fix security issues. E.g., the latest version as of this writing (21 January 2009: Tor 0.2.0.33) comes with the following changelog entry: "Fix a heap-corruption bug that may be remotely triggerable on some platforms" (From http://archives.seul.org/or/announce/Jan-2009/msg0.html) In my view, Tor should either be removed from Ubuntu or updated regularly. Thanks Jens ** Affects: ubuntu Importance: Undecided Status: New ** Visibility changed to: Public -- Tor packages too old https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] [NEW] Tor packages too old
*** This bug is a security vulnerability *** Public security bug reported: Tor packages do not seem to be updated in Ubuntu. The list http://packages.ubuntu.com/search?keywords=tor contains only outdated packages. My 8.04installs package tor 0.1.2.19-2, which is one year old by now. This is very bad as Tor is security software, and new versions frequently fix security issues. E.g., the latest version as of this writing (21 January 2009: Tor 0.2.0.33) comes with the following changelog entry: "Fix a heap-corruption bug that may be remotely triggerable on some platforms" (From http://archives.seul.org/or/announce/Jan-2009/msg0.html) In my view, Tor should either be removed from Ubuntu or updated regularly. Thanks Jens ** Affects: ubuntu Importance: Undecided Status: New ** Visibility changed to: Public -- Tor packages too old https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] Re: Security fixes in tor 0.2.0.32 and .33
Many thanks for your quick responses! As I wrote via e-mail already (hoping it would appear here automagically): I'm sorry, but I've never created a debdiff. To be honest I don't think that separate debdiffs are worth the trouble. Tor is under constant development, and lots of bugs (ordinary ones as well as attacks against its anonymity goal) are fixed frequently. In my view, this kind of software requires the use of the newest release. Otherwise, it's just dangerous. I filed a backport request as suggested by Hew McLachlan: https://bugs.launchpad.net/bugs/321520 -- Security fixes in tor 0.2.0.32 and .33 https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] [NEW] losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Public bug reported: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] [NEW] Build error: ‘struct bio’ has no member named ‘bi_hw_front_ size’
Public bug reported: Binary package hint: loop-aes-source loop-aes in jaunty is v3.2c. Build via "module-assistant auto-install loop-aes" fails. Changelog for v3.2d contains "Worked around block layer interface breakage on linux-2.6.28-rc kernels." Moreover, Changelog for v3.2e (current version) is "Fix null pointer dereference when loop was used to mount iso9660 CD-ROM image. This new bug was introduced in loop-AES-v3.2d, earlier versions are ok. Thanks to Peter Koek for reporting this issue." Please update to current version. ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] Re: Build error: ‘struct bi o’ has no member named ‘bi_hw_front_si ze’
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for "modprobe loop" I get "Invalid module format" (dmesg shows "loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)". I guess this happens as the jaunty kernel has "CONFIG_BLK_DEV_LOOP=y" whereas the loop-aes README clearly states "Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n." Did the build process via module-assistant ever work under Ubuntu? -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] Re: losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Added the "P.S." about acpi=off ** Description changed: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). + + P.S. losetup -d behaves as expected if I boot with "acpi=off". -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] [NEW] Build error: ‘struct bio’ has no member named ‘bi_hw_front_ size’
Public bug reported: Binary package hint: loop-aes-source loop-aes in jaunty is v3.2c. Build via "module-assistant auto-install loop-aes" fails. Changelog for v3.2d contains "Worked around block layer interface breakage on linux-2.6.28-rc kernels." Moreover, Changelog for v3.2e (current version) is "Fix null pointer dereference when loop was used to mount iso9660 CD-ROM image. This new bug was introduced in loop-AES-v3.2d, earlier versions are ok. Thanks to Peter Koek for reporting this issue." Please update to current version. ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] Re: Build error: ‘struct bi o’ has no member named ‘bi_hw_front_si ze’
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for "modprobe loop" I get "Invalid module format" (dmesg shows "loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)". I guess this happens as the jaunty kernel has "CONFIG_BLK_DEV_LOOP=y" whereas the loop-aes README clearly states "Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n." Did the build process via module-assistant ever work under Ubuntu? -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] [NEW] losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Public bug reported: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] Re: losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Added the "P.S." about acpi=off ** Description changed: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). + + P.S. losetup -d behaves as expected if I boot with "acpi=off". -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] [NEW] Tor packages too old
*** This bug is a security vulnerability *** Public security bug reported: Tor packages do not seem to be updated in Ubuntu. The list http://packages.ubuntu.com/search?keywords=tor contains only outdated packages. My 8.04installs package tor 0.1.2.19-2, which is one year old by now. This is very bad as Tor is security software, and new versions frequently fix security issues. E.g., the latest version as of this writing (21 January 2009: Tor 0.2.0.33) comes with the following changelog entry: "Fix a heap-corruption bug that may be remotely triggerable on some platforms" (From http://archives.seul.org/or/announce/Jan-2009/msg0.html) In my view, Tor should either be removed from Ubuntu or updated regularly. Thanks Jens ** Affects: ubuntu Importance: Undecided Status: New ** Visibility changed to: Public -- Tor packages too old https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] Re: Security fixes in tor 0.2.0.32 and .33
Many thanks for your quick responses! As I wrote via e-mail already (hoping it would appear here automagically): I'm sorry, but I've never created a debdiff. To be honest I don't think that separate debdiffs are worth the trouble. Tor is under constant development, and lots of bugs (ordinary ones as well as attacks against its anonymity goal) are fixed frequently. In my view, this kind of software requires the use of the newest release. Otherwise, it's just dangerous. I filed a backport request as suggested by Hew McLachlan: https://bugs.launchpad.net/bugs/321520 -- Security fixes in tor 0.2.0.32 and .33 https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] [NEW] losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Public bug reported: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] [NEW] Build error: ‘struct bio’ has no member named ‘bi_hw_front_ size’
Public bug reported: Binary package hint: loop-aes-source loop-aes in jaunty is v3.2c. Build via "module-assistant auto-install loop-aes" fails. Changelog for v3.2d contains "Worked around block layer interface breakage on linux-2.6.28-rc kernels." Moreover, Changelog for v3.2e (current version) is "Fix null pointer dereference when loop was used to mount iso9660 CD-ROM image. This new bug was introduced in loop-AES-v3.2d, earlier versions are ok. Thanks to Peter Koek for reporting this issue." Please update to current version. ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] Re: Build error: ‘struct bi o’ has no member named ‘bi_hw_front_si ze’
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for "modprobe loop" I get "Invalid module format" (dmesg shows "loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)". I guess this happens as the jaunty kernel has "CONFIG_BLK_DEV_LOOP=y" whereas the loop-aes README clearly states "Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n." Did the build process via module-assistant ever work under Ubuntu? -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] Re: losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Added the "P.S." about acpi=off ** Description changed: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). + + P.S. losetup -d behaves as expected if I boot with "acpi=off". -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] [NEW] Tor packages too old
*** This bug is a security vulnerability *** Public security bug reported: Tor packages do not seem to be updated in Ubuntu. The list http://packages.ubuntu.com/search?keywords=tor contains only outdated packages. My 8.04installs package tor 0.1.2.19-2, which is one year old by now. This is very bad as Tor is security software, and new versions frequently fix security issues. E.g., the latest version as of this writing (21 January 2009: Tor 0.2.0.33) comes with the following changelog entry: "Fix a heap-corruption bug that may be remotely triggerable on some platforms" (From http://archives.seul.org/or/announce/Jan-2009/msg0.html) In my view, Tor should either be removed from Ubuntu or updated regularly. Thanks Jens ** Affects: ubuntu Importance: Undecided Status: New ** Visibility changed to: Public -- Tor packages too old https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] Re: Security fixes in tor 0.2.0.32 and .33
Many thanks for your quick responses! As I wrote via e-mail already (hoping it would appear here automagically): I'm sorry, but I've never created a debdiff. To be honest I don't think that separate debdiffs are worth the trouble. Tor is under constant development, and lots of bugs (ordinary ones as well as attacks against its anonymity goal) are fixed frequently. In my view, this kind of software requires the use of the newest release. Otherwise, it's just dangerous. I filed a backport request as suggested by Hew McLachlan: https://bugs.launchpad.net/bugs/321520 -- Security fixes in tor 0.2.0.32 and .33 https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] [NEW] losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Public bug reported: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] [NEW] Build error: ‘struct bio’ has no member named ‘bi_hw_front_ size’
Public bug reported: Binary package hint: loop-aes-source loop-aes in jaunty is v3.2c. Build via "module-assistant auto-install loop-aes" fails. Changelog for v3.2d contains "Worked around block layer interface breakage on linux-2.6.28-rc kernels." Moreover, Changelog for v3.2e (current version) is "Fix null pointer dereference when loop was used to mount iso9660 CD-ROM image. This new bug was introduced in loop-AES-v3.2d, earlier versions are ok. Thanks to Peter Koek for reporting this issue." Please update to current version. ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] Re: Build error: ‘struct bi o’ has no member named ‘bi_hw_front_si ze’
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for "modprobe loop" I get "Invalid module format" (dmesg shows "loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)". I guess this happens as the jaunty kernel has "CONFIG_BLK_DEV_LOOP=y" whereas the loop-aes README clearly states "Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n." Did the build process via module-assistant ever work under Ubuntu? -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] Re: losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Added the "P.S." about acpi=off ** Description changed: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). + + P.S. losetup -d behaves as expected if I boot with "acpi=off". -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] [NEW] Tor packages too old
*** This bug is a security vulnerability *** Public security bug reported: Tor packages do not seem to be updated in Ubuntu. The list http://packages.ubuntu.com/search?keywords=tor contains only outdated packages. My 8.04installs package tor 0.1.2.19-2, which is one year old by now. This is very bad as Tor is security software, and new versions frequently fix security issues. E.g., the latest version as of this writing (21 January 2009: Tor 0.2.0.33) comes with the following changelog entry: "Fix a heap-corruption bug that may be remotely triggerable on some platforms" (From http://archives.seul.org/or/announce/Jan-2009/msg0.html) In my view, Tor should either be removed from Ubuntu or updated regularly. Thanks Jens ** Affects: ubuntu Importance: Undecided Status: New ** Visibility changed to: Public -- Tor packages too old https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321102] Re: Security fixes in tor 0.2.0.32 and .33
Many thanks for your quick responses! As I wrote via e-mail already (hoping it would appear here automagically): I'm sorry, but I've never created a debdiff. To be honest I don't think that separate debdiffs are worth the trouble. Tor is under constant development, and lots of bugs (ordinary ones as well as attacks against its anonymity goal) are fixed frequently. In my view, this kind of software requires the use of the newest release. Otherwise, it's just dangerous. I filed a backport request as suggested by Hew McLachlan: https://bugs.launchpad.net/bugs/321520 -- Security fixes in tor 0.2.0.32 and .33 https://bugs.launchpad.net/bugs/321102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] [NEW] losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Public bug reported: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] [NEW] Build error: ‘struct bio’ has no member named ‘bi_hw_front_ size’
Public bug reported: Binary package hint: loop-aes-source loop-aes in jaunty is v3.2c. Build via "module-assistant auto-install loop-aes" fails. Changelog for v3.2d contains "Worked around block layer interface breakage on linux-2.6.28-rc kernels." Moreover, Changelog for v3.2e (current version) is "Fix null pointer dereference when loop was used to mount iso9660 CD-ROM image. This new bug was introduced in loop-AES-v3.2d, earlier versions are ok. Thanks to Peter Koek for reporting this issue." Please update to current version. ** Affects: loop-aes-source (Ubuntu) Importance: Undecided Status: New -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342902] Re: Build error: ‘struct bi o’ has no member named ‘bi_hw_front_si ze’
I just retried the build with loop.c-2.6.patched from loop-aes v3.2e. Now, for "modprobe loop" I get "Invalid module format" (dmesg shows "loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)". I guess this happens as the jaunty kernel has "CONFIG_BLK_DEV_LOOP=y" whereas the loop-aes README clearly states "Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n." Did the build process via module-assistant ever work under Ubuntu? -- Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’ https://bugs.launchpad.net/bugs/342902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345585] Re: losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
Added the "P.S." about acpi=off ** Description changed: This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom processor, internal ATA disk), booted from USB stick. The following script (inspired by loop-aes testsuite) fails, usually within 20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD: Device or resource busy #!/bin/bash TLD=/dev/loop1 declare -i i=0 rm -f test-file* dd if=/dev/zero of=test-file1 bs=1024 count=33 cp test-file1 test-file3 while true do echo "Iteration $((i+=1))" /sbin/losetup /dev/loop1 test-file1 dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc if ! /sbin/losetup -d $TLD ; then exit 1 ; fi /sbin/losetup /dev/loop1 test-file1 dd if=/dev/loop1 of=test-file4 bs=33792 count=1 if ! /sbin/losetup -d $TLD ; then exit 1 ; fi done When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1" before "losetup -d", the script runs endlessly, as expected. When using the patched losetup of loop-aes (binary package loop-aes-utils as well as hand-made patched v2.12r) with some form of encryption (e.g., XOR), the above problem even arises when booting with kernel options "nosmp" as well as with "single". I'm reporting this as "linux" bug, not as "util-linux" one, as the above script runs fine on the same hardware with a different distribution (systemrescuecd). + + P.S. losetup -d behaves as expected if I boot with "acpi=off". -- losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy" https://bugs.launchpad.net/bugs/345585 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
