Bug#310982: plan to include in sarge 2.4 update

2006-11-27 Thread dann frazier
On Thu, Nov 16, 2006 at 10:51:24AM +0100, Bill Allombert wrote: I am a bit concerned by the comment in the link you posted: To fully work, some modifications are needed to samba smbmount.c and smbmnt.c files. Those patches are available at Samba and Kernel Bug Tracker pages.

Bug#310982: plan to include in sarge 2.4 update

2006-11-27 Thread Steve Langasek
On Mon, Nov 27, 2006 at 07:27:39PM -0700, dann frazier wrote: The downside is that any sarge users who might be relying on the use-the-server-provided-value behavior will no longer have that option. I don't understand this case enough to know if it has any practical implications. I would guess

Bug#310982: plan to include in sarge 2.4 update

2006-11-27 Thread Haroldo Gamal
Dear sirs, It's been a long time since I've made those patches but I have never known why the user level patches were not applied. I still think they are necessary. Haroldo On Mon, 2006-11-27 at 19:27 -0700, dann frazier wrote: On Thu, Nov 16, 2006 at 10:51:24AM +0100, Bill Allombert wrote:

Bug#310982: plan to include in sarge 2.4 update

2006-11-16 Thread Martin Schulze
dann frazier wrote: On Mon, Nov 13, 2006 at 12:22:59PM -0800, Steve Langasek wrote: Yes, because this is a kernel security bug. The smbmount patch was entertained pre-sarge only as a stopgap due to the proximity to release; the right place to fix this is still in the kernel (upstream as

Bug#310982: plan to include in sarge 2.4 update

2006-11-16 Thread Bill Allombert
On Wed, Nov 15, 2006 at 05:54:52PM -0700, dann frazier wrote: On Mon, Nov 13, 2006 at 12:22:59PM -0800, Steve Langasek wrote: Yes, because this is a kernel security bug. The smbmount patch was entertained pre-sarge only as a stopgap due to the proximity to release; the right place to fix

Bug#310982: plan to include in sarge 2.4 update

2006-11-15 Thread dann frazier
On Mon, Nov 13, 2006 at 12:22:59PM -0800, Steve Langasek wrote: Yes, because this is a kernel security bug. The smbmount patch was entertained pre-sarge only as a stopgap due to the proximity to release; the right place to fix this is still in the kernel (upstream as appropriate). I've done

Bug#310982: plan to include in sarge 2.4 update

2006-11-15 Thread Horms
On Wed, Nov 15, 2006 at 05:54:52PM -0700, dann frazier wrote: On Mon, Nov 13, 2006 at 12:22:59PM -0800, Steve Langasek wrote: Yes, because this is a kernel security bug. The smbmount patch was entertained pre-sarge only as a stopgap due to the proximity to release; the right place to fix

Bug#310982: plan to include in sarge 2.4 update

2006-11-13 Thread Horms
On Sun, Nov 12, 2006 at 10:28:10PM -0700, dann frazier wrote: On Mon, Nov 13, 2006 at 01:30:19PM +0900, Horms wrote: If you point me at the patch I'll be happy to rack my brains and tell you want I was thinking at the time. Thanks Horms, here's the link:

Bug#310982: plan to include in sarge 2.4 update

2006-11-13 Thread Bill Allombert
On Sun, Nov 12, 2006 at 09:28:14PM -0700, dann frazier wrote: Moritz pointed out that this issue has been overlooked for sarge updates so far. From my reading of this report, it sounds like our best option for sarge is to incorporate Horms' patch for 2.4.27. Thanks for looking at this. I

Bug#310982: plan to include in sarge 2.4 update

2006-11-13 Thread dann frazier
On Mon, Nov 13, 2006 at 10:09:52AM +0100, Bill Allombert wrote: Thanks for looking at this. I initially reported this issue to samba and then I provided a patch for smbmout. Now if the issue is fixed in the kernel instead, then all kernel providing smbfs need to be fixed, not only

Bug#310982: plan to include in sarge 2.4 update

2006-11-13 Thread Bill Allombert
On Mon, Nov 13, 2006 at 09:26:10AM -0700, dann frazier wrote: On Mon, Nov 13, 2006 at 10:09:52AM +0100, Bill Allombert wrote: Thanks for looking at this. I initially reported this issue to samba and then I provided a patch for smbmout. Now if the issue is fixed in the kernel instead,

Bug#310982: plan to include in sarge 2.4 update

2006-11-13 Thread Steve Langasek
On Mon, Nov 13, 2006 at 05:49:56PM +0100, Bill Allombert wrote: On Mon, Nov 13, 2006 at 09:26:10AM -0700, dann frazier wrote: On Mon, Nov 13, 2006 at 10:09:52AM +0100, Bill Allombert wrote: Thanks for looking at this. I initially reported this issue to samba and then I provided a

Bug#310982: plan to include in sarge 2.4 update

2006-11-12 Thread dann frazier
Moritz pointed out that this issue has been overlooked for sarge updates so far. From my reading of this report, it sounds like our best option for sarge is to incorporate Horms' patch for 2.4.27. Does anyone object to this? I'll make builds available for testing prior to uploading, in case

Bug#310982: plan to include in sarge 2.4 update

2006-11-12 Thread Horms
On Sun, Nov 12, 2006 at 09:28:14PM -0700, dann frazier wrote: Moritz pointed out that this issue has been overlooked for sarge updates so far. From my reading of this report, it sounds like our best option for sarge is to incorporate Horms' patch for 2.4.27. Does anyone object to this?

Bug#310982: plan to include in sarge 2.4 update

2006-11-12 Thread dann frazier
On Mon, Nov 13, 2006 at 01:30:19PM +0900, Horms wrote: If you point me at the patch I'll be happy to rack my brains and tell you want I was thinking at the time. Thanks Horms, here's the link: http://bugs.debian.org/cgi-bin/bugreport.cgi/smbfs.no_cap_unix.patch?bug=310982;msg=101;att=1 --