Re: [Bug 242869] Re: dnsmasq's dhcp blocked to clients by firestarter
It could also be that you have a adsl modem what does not resolve all the names for you as you want, like say a Tomson modem, but if you are correct in this, why does it do what it has to do, with the ' user-pre' addition in my case and probably someone elses' . regards. On wo, 2009-07-08 at 15:48 +, ded wrote: > dnsmasq takes care of so many headaches for a small network, this > problem was really killing me since firestarter is probably the best gui > front-end to iptables I've found. > > But the above problem was plaguing me and the fix to user-pre above > didn't seem to help. > > In case anyone does what I did, I want to post the solution. I cut and > pated the above-line from my browser into the user-pre file and it > didn't work. What I finally discovered after banging my head on this > one for several days was that the --sport and --dport argument got > converted to and en-dash or some such non-ascii character by the browser > and were invalid. > > When you past the above, make sure to change them! > > I found this by running "firestarter --start" from the command line, > which will echo all the iptables errors to the console. I found several > other problems with my firestarter configuration this way as well. For > example, I found that it was unable to resolve the "hostnames" I used in > several rules, so they weren't getting into the firewall. I had to > hard-code IP addresses instead. > > I hope this helps someone else. > > Regards, > > ded > -- dnsmasq's dhcp blocked to clients by firestarter https://bugs.launchpad.net/bugs/242869 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 380715] Re: samba shares of symlinks are always read-only
I've attached my smb.conf file, if it helps. -- Scott ** Attachment added: "smb.conf" http://launchpadlibrarian.net/28840002/smb.conf -- samba shares of symlinks are always read-only https://bugs.launchpad.net/bugs/380715 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 380715] Re: samba shares of symlinks are always read-only
Hi Thierry, I tried what you suggested and had the same problem. However, I did discovered something. It seems that it is the *name* of the share that is causing the problem rather than what it is pointing to. On my system, anything shared using the name "shared" is read-only, whether it points to a folder (i.e., /home/scott/real) or a symlink (i.e., /home/scott/shared). The smb.conf entry above is read-only from my windows machines (I've tried it from two different machines). However, if I simply change the name of the share to "shared2" then it works as expected, i.e., I change it to read: [shared2] path = /home/scott/shared writeable = yes browseable = yes valid users = scott I've looked through my smb.conf file and there are no other instances of "shared" other than that above. Also, the read-only problem is happening from two different windows computers. So, I think it's still something happening on the server side. Is it possible that samba has some other configuration information somewhere or that "shared" is somehow reserved? Any other ideas to try? Thanks, -- Scott -- samba shares of symlinks are always read-only https://bugs.launchpad.net/bugs/380715 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 360689] Re: Default Ubuntu configuration is backscatter source in Jaunty
** Branch linked: lp:ubuntu/karmic/amavisd-new -- Default Ubuntu configuration is backscatter source in Jaunty https://bugs.launchpad.net/bugs/360689 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 394350] Re: RLimitCPU has no effect in Apache
I appreciate the attempts Ubuntu people have made to reproduce the problem, and I'm baffled that myself and my users are still easily reproducing the problem. I once again reproduced the problem on one of my Ubuntu configurations, and observed through "/proc//limits" that the limits are "unlimited" on the process. We have had multiple people reproduce this problem here, on multiple systems, at multiple sites, with fresh installs, on both i386 and amd64, and everyone saw the same erroneous behavior with Ubuntu packagings but not with upstream. Nor did Debian exhibit this problem. We have also been aware that the limit was in CPU seconds, not wall clock time. (I was very skeptical myself, when they first called me in as a fresh pair of eyes, after very experienced people there were stumped.) I suppose the only thing to do at this point, as far as this bug report is concerned,are: (1) for me to start once again with a fresh Ubuntu install, and this time to carefully log each step in a form appropriate for this bug report (perhaps video it, too! :); and (2) for me to get the problematic Apache process debuggable and locate the erroneous behavior that way. Realistically, this problem is so bizarre and has been so time-consuming that (though I wouldn't attribute "fault" til we know the cause), my users will also have to consider known-good options, such as running upstream Apache or switching the distro to Debian "stable" or RHEL/CentOS. -- RLimitCPU has no effect in Apache https://bugs.launchpad.net/bugs/394350 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 392236] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS
A backport of 5.0.38 doesn't produce a mysqld crash: math...@t-mysqld-d:~$ mysql -u root Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 8 Server version: 5.0.38-Ubuntu_0ubuntu1-log Ubuntu 7.04 distribution Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> use mysql Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION SELECT mu.user FROM mysql.user mu ORDER BY mu.User) a; ERROR 1054 (42S22): Unknown column 'mu.User' in 'order clause' -- MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS https://bugs.launchpad.net/bugs/392236 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)
On hardy and above the server doesn't crash. Instead the following error is reported: ERROR 1436 (HY000): Thread stack overrun: 250312 bytes used of a 262144 byte stack, and 12000 bytes needed. Use 'mysqld -O thread_stack=#' to specify a bigger stack. Marking bug Fixed Released for hardy and above. ** Changed in: mysql-dfsg-5.0 (Ubuntu) Status: New => Fix Released ** Also affects: mysql-dfsg-5.0 (Ubuntu Dapper) Importance: Undecided Status: New ** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper) Importance: Undecided => Medium ** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper) Status: New => Triaged -- MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...) https://bugs.launchpad.net/bugs/394036 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 392236] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS
Both hardy (5.0.51a) and karmic (5.0.75) don't allow the use of such a query: mysql> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION SELECT mu.user FROM mysql.user mu ORDER BY mu.User) a; ERROR 1054 (42S22): Unknown column 'mu.User' in 'order clause' which seems to be right behavior. Marking this bug Fixed Released in hardy and above. ** Changed in: mysql-dfsg-5.0 (Ubuntu) Status: New => Fix Released ** Also affects: mysql-dfsg-5.0 (Ubuntu Dapper) Importance: Undecided Status: New ** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper) Importance: Undecided => Medium ** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper) Status: New => Triaged -- MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS https://bugs.launchpad.net/bugs/392236 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328874] Re: getent group crashes winbindd on domain controller
I've tried to put together a test case in the bug description, but apparently I've overlooked something in the setup that isn't covered very clearly in the samba howtos, because even 'wbinfo -g' fails for me when trying to run this test. ** Description changed: Binary package hint: samba I encountered this bug on a hardy domain controller using winbind to fetch user/group informations from another NT domain (the Samba domain trusts the NT domain). Calling getent group just crashes winbindd, as seen in the log attached. - This is a bug known and fixed upstream [0] (in 3.2.6 and 3.3.0). - Fixing jaunty is a matter of uploading the latest 3.2 version or 3.3. - Fixing hardy requires backporting the patch (I successfully tested it already). Actually the bug is not fixed in any maintenance release of 3.0, and I'm not sure it will ever be (as it seems to be EOL), but I got upstream to confirm the fix is appropriate for this branch as well [1] and commit it [2]. - If someone is interested, we could also fix intrepid. I don't know about other releases. + TEST CASE: - [0] https://bugzilla.samba.org/show_bug.cgi?id=5906 - [1] http://lists.samba.org/archive/samba-technical/2009-February/063155.html - [2] http://gitweb.samba.org/?p=samba.git;a=commit;h=db4a435d235bedf48d668a0f4418dd46f38044ed + 1. Install samba and winbind 3.0.28a-1ubuntu4.7 from hardy-updates. + 2. Configure samba as an NT4 domain controller by setting 'domain logons = yes' in /etc/samba/smb.conf, and also set 'winbind enum users = yes' and 'winbind enum groups = yes' + 3. Restart samba and winbind with sudo /etc/init.d/winbind restart; sudo /etc/init.d/samba restart + 4. Set up a domain trust to another NT4 domain (Windows NT, or a second Samba instance) using the instructions at http://man.chinaunix.net/newsoft/samba/docs/man/Samba-HOWTO-Collection/InterdomainTrusts.html#id2577358 + 5. edit /etc/nsswitch.conf to list 'group: compat winbind' + 6. run 'getent group' and verify that the winbind service has stopped. + 7. upgrade samba and winbind to version 3.0.28a-1ubuntu4.8 in hardy-proposed. + 8. run 'getent group' again to verify that the winbind service no longer crashes. -- getent group crashes winbindd on domain controller https://bugs.launchpad.net/bugs/328874 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 328874] Re: getent group crashes winbindd on domain controller
On Tue, Jun 23, 2009 at 01:32:18PM -, Adrien Cunin wrote: > given that it's been in -proposed for more than 3 > months with no negative feedback (nor positive, right), would it be > possible to assume it's safe to move it to -updates? The lack of positive feedback makes this a risk, since this means we have no evidence that anyone has tested this upload at all and there may be regressions when cherry-picking this one patch. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- getent group crashes winbindd on domain controller https://bugs.launchpad.net/bugs/328874 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
(err, yes, obviously that approach only works with netboot not CD) -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
open-iscsi-udeb isn't in the installer initrd, but instead is retrieved from the archive at run-time; so booting the installer with apt- setup/proposed=true (once this has built and published) should be sufficient. -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 328874] Re: getent group crashes winbindd on domain controller
Adrien, Please note that the SRU verification team consists of a handful of folks trying to do verifications across a wide range of packages; for bugs that require deep configurations to reproduce (like setting up an entire NT4 domain), it's far better if users of the package test the uploads since they're already familiar with it. I'll distill the information in this bug report down to a test case that will hopefully let the verification team finish this up. -- getent group crashes winbindd on domain controller https://bugs.launchpad.net/bugs/328874 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
Colin, as the bug is in the installer part of the package, I would need an ISO to test. Or can I test using the netboot installer? -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
Accepted into hardy-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Tags added: verification-needed -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 397203] [NEW] ldap.so missing from package
Public bug reported: Binary package hint: winbind Winbind has lost LDAP support because ldap.so is missing from /usr/lib/samba/idmap/ldap.so I discovered this when trying to use winbind to map to LDAP: /var/log/samba/log.winbind-idmap reported the following: [2009/07/08 17:10:26, 5] lib/module.c:smb_probe_module(111) Probing module 'ldap' [2009/07/08 17:10:26, 5] lib/module.c:smb_probe_module(130) Probing module 'ldap': Trying to load from /usr/lib/samba/idmap/ldap.so [2009/07/08 17:10:26, 3] lib/module.c:do_smb_load_module(48) Error loading module '/usr/lib/samba/idmap/ldap.so': /usr/lib/samba/idmap/ldap.so: cannot open shared object file: No such file or directory [2009/07/08 17:10:26, 1] winbindd/idmap.c:idmap_alloc_init(578) could not find idmap alloc module ldap:ldap://ldap-north.healthstudies.umn.edu/ ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: idmap ldap winbind -- ldap.so missing from package https://bugs.launchpad.net/bugs/397203 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
I do not have the problem Kevin reports above; iscsi=true works just fine for me. I tested using the karmic server CD image dated 08-Jul-2009 10:32 from the same location he does. I am pleased to report the iSCSI installer support works just fine now for me. The iSCSI dialog come up fine, the partitioner present the iSCSI target as a valid block device, and configuring a file system on said iSCSI target to be mounted on boot work as expected. It sounds like the last upload actually fixed the bug! -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 397143] Re: Please merge drbd8 2:8.3.2-1 (main) from Debian unstable
** Attachment added: "debdiff for 8.3.2-1ubuntu1" http://launchpadlibrarian.net/28822809/drbd-merge.debdiff ** Changed in: drbd8 (Ubuntu) Importance: Undecided => Medium ** Changed in: drbd8 (Ubuntu) Status: New => Confirmed -- Please merge drbd8 2:8.3.2-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/397143 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 397143] Re: Please merge drbd8 2:8.3.2-1ubuntu1 (main) from Debian unstable
** Attachment added: "debdiff for 8.3.2-1ubuntu1" http://launchpadlibrarian.net/28822687/drbd-merge.debdiff ** Attachment removed: "debdiff for 8.3.2-1ubuntu1" http://launchpadlibrarian.net/28822687/drbd-merge.debdiff ** Summary changed: - Please merge drbd8 2:8.3.2-1ubuntu1 (main) from Debian unstable + Please merge drbd8 2:8.3.2-1 (main) from Debian unstable ** Description changed: Changes: drbd8 (2:8.3.2-1ubuntu1) karmic; urgency=low . * Resync with Debian package, drop all previous Ubuntu changes +* Closes: LP #397143 . [ New Ubuntu packaging ] . * debian/control: - replace Maintainer field - remove dpatch from Build-Depends - add drbd8-source to drbd8-utils' Depends - remove module-assistant, add dkms and headers to drbd8-source Depends * debian/dkms.conf - dkms configuration file * remove debian/drbd8-source.dirs * add drbd8-source.[postinst|prerm] scripts * remove 10_different-kernels patch and patch subsystem * debian/rules - change it to set up dkms bits and remove module-assistant . drbd8 (2:8.3.2-1) unstable; urgency=low . * New upstream release. * Section of drbd8-source is kernel. . drbd8 (2:8.3.2~rc2-1) unstable; urgency=low . * New upstream release candidate. . drbd8 (2:8.3.2~rc1-1) unstable; urgency=low . * New upstream release candidate. + Make it compile on Linux 2.6.30. (closes: #533261, #533654) * Update Standards-Version to 3.8.2, no changes required. * Fix maintainer-script-ignores-errors lintian warning. -- Please merge drbd8 2:8.3.2-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/397143 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 397143] [NEW] Please merge drbd8 2:8.3.2-1 (main) from Debian unstable
Public bug reported: Changes: drbd8 (2:8.3.2-1ubuntu1) karmic; urgency=low . * Resync with Debian package, drop all previous Ubuntu changes * Closes: LP #397143 . [ New Ubuntu packaging ] . * debian/control: - replace Maintainer field - remove dpatch from Build-Depends - add drbd8-source to drbd8-utils' Depends - remove module-assistant, add dkms and headers to drbd8-source Depends * debian/dkms.conf - dkms configuration file * remove debian/drbd8-source.dirs * add drbd8-source.[postinst|prerm] scripts * remove 10_different-kernels patch and patch subsystem * debian/rules - change it to set up dkms bits and remove module-assistant . drbd8 (2:8.3.2-1) unstable; urgency=low . * New upstream release. * Section of drbd8-source is kernel. . drbd8 (2:8.3.2~rc2-1) unstable; urgency=low . * New upstream release candidate. . drbd8 (2:8.3.2~rc1-1) unstable; urgency=low . * New upstream release candidate. + Make it compile on Linux 2.6.30. (closes: #533261, #533654) * Update Standards-Version to 3.8.2, no changes required. * Fix maintainer-script-ignores-errors lintian warning. ** Affects: drbd8 (Ubuntu) Importance: Medium Status: Confirmed -- Please merge drbd8 2:8.3.2-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/397143 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 395105] Re: Could not install 'smbclient'
No information available that would let us address this, and no other reports of uninstallability. Closing. ** Changed in: samba (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: samba (Ubuntu) Assignee: 3n!Gma (wm3) => (unassigned) -- Could not install 'smbclient' https://bugs.launchpad.net/bugs/395105 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
I just acquired karmic-server-i386.iso from http://cdimage.ubuntu.com /ubuntu-server/daily/current/ and booted with the iscsi=true commandline option. I was not prompted for any iscsi information, nor is "Configure iSCSI" present in the installer main menu. -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
** Branch linked: lp:ubuntu/gutsy-updates/gnutls13 ** Branch linked: lp:~ubuntu-branches/ubuntu/gutsy/gnutls13/gutsy- proposed ** Branch linked: lp:~ubuntu-branches/ubuntu/hardy/gnutls13/hardy- security ** Branch linked: lp:~ubuntu-branches/ubuntu/hardy/gnutls13/hardy- proposed -- gnutls regression: failure in certificate chain validation https://bugs.launchpad.net/bugs/305264 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 236640] Re: iSCSI install fails under hardy
Etienne, I'm preparing an SRU upload of open-iscsi for hardy including the latest fixes that you've indicated, which I'll be uploading today. In the meantime, would it be possible for you to do a full install test with the latest karmic daily, which includes the fixes from open-iscsi 2.0.870.1-0ubuntu5, to confirm that this addresses the problem there? -- iSCSI install fails under hardy https://bugs.launchpad.net/bugs/236640 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 242869] Re: dnsmasq's dhcp blocked to clients by firestarter
dnsmasq takes care of so many headaches for a small network, this problem was really killing me since firestarter is probably the best gui front-end to iptables I've found. But the above problem was plaguing me and the fix to user-pre above didn't seem to help. In case anyone does what I did, I want to post the solution. I cut and pated the above-line from my browser into the user-pre file and it didn't work. What I finally discovered after banging my head on this one for several days was that the --sport and --dport argument got converted to and en-dash or some such non-ascii character by the browser and were invalid. When you past the above, make sure to change them! I found this by running "firestarter --start" from the command line, which will echo all the iptables errors to the console. I found several other problems with my firestarter configuration this way as well. For example, I found that it was unable to resolve the "hostnames" I used in several rules, so they weren't getting into the firewall. I had to hard-code IP addresses instead. I hope this helps someone else. Regards, ded -- dnsmasq's dhcp blocked to clients by firestarter https://bugs.launchpad.net/bugs/242869 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
This bug was fixed in the package gnutls13 - 2.0.4-1ubuntu2.5 --- gnutls13 (2.0.4-1ubuntu2.5) hardy-security; urgency=low * Fix for certificate chain regressions introduced by fixes for CVE-2008-4989 * debian/patches/91_CVE-2008-4989.diff: updated to upstream's final 2.4.2 - 2.4.3 patchset for lib/x509/verify.c to fix CVE-2008-4989 and address all known regressions. To summarize from upstream: - Fix X.509 certificate chain validation error (CVE-2008-4989) - Fix chain verification for chains that end with RSA-MD2 CAs (LP: #305264) - Deprecate X.509 validation chains using MD5 and MD2 signatures - Accept chains where intermediary certs are trusted (LP: #305264) -- Jamie StrandbogeFri, 20 Feb 2009 13:02:36 -0600 ** Changed in: gnutls13 (Ubuntu Hardy) Status: Fix Committed => Fix Released -- gnutls regression: failure in certificate chain validation https://bugs.launchpad.net/bugs/305264 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 397054] Re: package samba-common 2:3.3.2-1ubuntu3.1 failed to install/upgrade: Unterprozess post-installation script gab den Fehlerwert 1 zur?ck
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/28800437/Dependencies.txt ** Attachment added: "DpkgTerminalLog.txt" http://launchpadlibrarian.net/28800438/DpkgTerminalLog.txt -- package samba-common 2:3.3.2-1ubuntu3.1 failed to install/upgrade: Unterprozess post-installation script gab den Fehlerwert 1 zur?ck https://bugs.launchpad.net/bugs/397054 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 397054] [NEW] package samba-common 2:3.3.2-1ubuntu3.1 failed to install/upgrade: Unterprozess post-installation script gab den Fehlerwert 1 zur?ck
Public bug reported: Binary package hint: samba update fail ProblemType: Package Architecture: amd64 DistroRelease: Ubuntu 9.04 ErrorMessage: Unterprozess post-installation script gab den Fehlerwert 1 zurück Package: samba-common 2:3.3.2-1ubuntu3.1 SourcePackage: samba Title: package samba-common 2:3.3.2-1ubuntu3.1 failed to install/upgrade: Unterprozess post-installation script gab den Fehlerwert 1 zurück Uname: Linux 2.6.28-11-generic x86_64 ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package -- package samba-common 2:3.3.2-1ubuntu3.1 failed to install/upgrade: Unterprozess post-installation script gab den Fehlerwert 1 zur?ck https://bugs.launchpad.net/bugs/397054 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
For the openldap/hardy SRU: I have: (1) reproduced the acceptance of the v1 certificates as outlined in Mathias' test case by the ldap clients with ldap 2.4.9-0ubuntu0.8.04.2 and gnutls13 2.0.4-1ubuntu2. (2) reproduced the rejection of v1 certificates by the ldap clients with ldap 2.4.9-0ubuntu0.8.04.2 and gnutls13 versions 2.0.4-1ubuntu2.3 and 2.0.4-1ubuntu2.5. (3) confirmed that the with the version of the ldap packages in hardy-proposed, 2.4.9-0ubuntu0.8.04.3, that the v1 certificates are once again accepted when using gnutls13 versions 2.0.4-1ubuntu2.3 and 2.0.4-1ubuntu2.5. I have also run the ldap packages in hardy-proposed through the openldap testcases in the lp:qa-regression-testing bzr tree with all three available versions of gnutls13 (gnutls13 2.0.4-1ubuntu2, 2.0.4-1ubuntu2.3, 2.0.4-1ubuntu2.5) and confirmed that there were no introduced regressions seen there as well. I consider the openldap packages verification-done for hardy. -- gnutls regression: failure in certificate chain validation https://bugs.launchpad.net/bugs/305264 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 305264] Re: gnutls regression: failure in certificate chain validation
For the gnutls/hardy SRU: I have reproduced the acceptance of rsa/md2 v1 certificates by the version of gnutls13 in hardy-updates, 2.0.4-1ubuntu2.3, and can confirm that the version of gnutls13 in hardy-proposed does not accept rsa/md2 certificates. I have added a testcase for this situation in the gnutls test script in the lp:qa-regression-testing bzr tree. The package passes the rest of the regression test in the testsuite, with the exception of known bug 292604 which is not a regression (2.0.4-1ubuntu2.3 also fails this test and it looks like it won't get fixed in hardy). -- gnutls regression: failure in certificate chain validation https://bugs.launchpad.net/bugs/305264 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 393450] Re: [SRU] pam_winbind Use incorrect value for password expiry calculation
Please add a test case for SRU verification. -- [SRU] pam_winbind Use incorrect value for password expiry calculation https://bugs.launchpad.net/bugs/393450 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 393450] Re: [SRU] pam_winbind Use incorrect value for password expiry calculation
Accepted samba into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: samba (Ubuntu Jaunty) Status: New => Fix Committed ** Tags added: verification-needed -- [SRU] pam_winbind Use incorrect value for password expiry calculation https://bugs.launchpad.net/bugs/393450 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs