Arup Biswas | 1 Aug 01:41 2006

RE: DSRoleGetPrimaryDomainInformation()


I have ported my changes to the Samba trunk. However, while testing I
discovered a problem
in the case of a out of domain client in NTLM mode. I was hoping the
porting should be simple,
but it seems, there are few more wrinkles to it. I will look at it
whenever I get some time.

Thanks,
-Arup  

-----Original Message-----
From: Jeremy Allison [mailto:jra <at> samba.org] 
Sent: Saturday, July 29, 2006 12:15 PM
To: Arup Biswas
Cc: Jeremy Allison; Gerald (Jerry) Carter;
samba-technical <at> lists.samba.org
Subject: Re: DSRoleGetPrimaryDomainInformation()

On Sat, Jul 29, 2006 at 11:30:17AM -0700, Arup Biswas wrote:
> 
> I assume I should modify the latest Samba release i.e. 3.0.23a at this

> point?

If you can get at the SAMBA_3_0 SVN source that would be best, if not
then the 3.0.23a source would work fine.

Thanks,

(Continue reading)

Andrew Bartlett | 1 Aug 01:47 2006
Picon

Re: trans2 response handling

On Mon, 2006-07-31 at 09:22 -0700, Murali Bashyam wrote:
> Stefan
> 
> To fix the issue, could we do something like not serialize when we are
> handling trans2 request/responses i.e turn off the serialise flag just
> before and during the whole exchange, and turn it on after the exchange?
> Would this work?

The correct fix is to return to the main event loop, and handle the
remainder on a callback.

Andrew Bartlett

--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Red Hat Inc.                  http://redhat.com
Murali Bashyam | 1 Aug 01:55 2006
Picon

smbpasswd in samba4

Does the old smbpasswd accounts and database continue to work in samba4? I
am seeing that the users added through the smbpasswd utility are
unsuccessful in logging in, is this an issue or could there be a
mis-configuration ?

Thx,
Murali

Andrew Bartlett | 1 Aug 02:04 2006
Picon

Re: smbpasswd in samba4

On Mon, 2006-07-31 at 16:55 -0700, Murali Bashyam wrote:
> Does the old smbpasswd accounts and database continue to work in samba4? I
> am seeing that the users added through the smbpasswd utility are
> unsuccessful in logging in, is this an issue or could there be a
> mis-configuration ?

In current Samba4 SVN there is a 'newuser' and 'setpassword' script in
the source/setup directory, which allows this.  We need much more work
on admin tools.

Andrew Bartlett

--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Red Hat Inc.                  http://redhat.com
Jelmer Vernooij | 1 Aug 01:59 2006
Picon

Re: smbpasswd in samba4

On Mon, 2006-07-31 at 16:55 -0700, Murali Bashyam wrote:
> Does the old smbpasswd accounts and database continue to work in samba4? I
> am seeing that the users added through the smbpasswd utility are
> unsuccessful in logging in, is this an issue or could there be a
> mis-configuration ?
No, the file format has changed; we are now storing all user information
in LDAP-like databases (either LDB, or native LDAP).
There is an experimental upgrade script that converts a Samba3
installation to a Samba4 installation - see source/setup/upgrade in the
Samba 4 tarball.

Cheers,

Jelmer
Andrew Bartlett | 1 Aug 03:00 2006
Picon

Re: trans2 response handling

On Sun, 2006-07-30 at 16:04 -0700, Murali Bashyam wrote:
> On samba4 TP2, i am noticing the following problem when there are multiple
> trans2 responses to a single trans2 request.
> 
> After processing the first response, smb_raw_trans2_recv calls
> smbcli_request_receive_more to handle the next response message, and ends up
> blocking in epoll_wait waiting for a read event. Some time later when the
> next trans2 response message is received, the wait unblocks, and then ends
> up calling packet_receive (via smbcli_transport_event_handler). packet_recv
> checks for the 'processing' flag in the packet context, and since this flag
> is still set, it simply marks the fde not readable and returns without
> picking up the next message, ultimately leading to a timeout. The
> 'processing' flag in the packet context is not reset until we return from
> smb_raw_trans2_recv back to the smbcli_transport_finish_recv function. This
> seems to be leading to a deadlock in the multiple trans2 response scenario
> where the smb client raw layer thinks there is no message pending for it
> even though there is one and it is ready to process it, and the packet layer
> is serializing the next response waiting for the smb client raw layer to
> indicate to the packet layer somehow that it's finished with the previous
> response. Is this a known issue with the tp2 snapshot?
> 
> I don't see any change to fix this problem in these code segments in the
> latest version of samba 4, and was wondering whether anyone else has
> observed this.

I've been looking into this (thankyou very much for your clear
analysis), and I think there are a few issues here:

Firstly, we should be passing the trans requests though the ntvfs layer,
not directly to the remote server.  That issue is in
(Continue reading)

Picon

The Most Misunderstood Windows Security Setting of All Time

Hello,

an interesting read:

http://www.microsoft.com/technet/technetmag/issues/2006/08/SecurityWatch/default.aspx

Jean-Baptiste Marchand

Murali Bashyam | 1 Aug 07:29 2006
Picon

Re: trans2 response handling

On 7/31/06, Andrew Bartlett <abartlet <at> samba.org> wrote:
>
> On Sun, 2006-07-30 at 16:04 -0700, Murali Bashyam wrote:
> > On samba4 TP2, i am noticing the following problem when there are
> multiple
> > trans2 responses to a single trans2 request.
> >
> > After processing the first response, smb_raw_trans2_recv calls
> > smbcli_request_receive_more to handle the next response message, and
> ends up
> > blocking in epoll_wait waiting for a read event. Some time later when
> the
> > next trans2 response message is received, the wait unblocks, and then
> ends
> > up calling packet_receive (via smbcli_transport_event_handler).
> packet_recv
> > checks for the 'processing' flag in the packet context, and since this
> flag
> > is still set, it simply marks the fde not readable and returns without
> > picking up the next message, ultimately leading to a timeout. The
> > 'processing' flag in the packet context is not reset until we return
> from
> > smb_raw_trans2_recv back to the smbcli_transport_finish_recv function.
> This
> > seems to be leading to a deadlock in the multiple trans2 response
> scenario
> > where the smb client raw layer thinks there is no message pending for it
> > even though there is one and it is ready to process it, and the packet
> layer
> > is serializing the next response waiting for the smb client raw layer to
(Continue reading)

Andrew Bartlett | 1 Aug 07:48 2006
Picon

Re: trans2 response handling

On Mon, 2006-07-31 at 22:29 -0700, Murali Bashyam wrote:
> 
> 
> On 7/31/06, Andrew Bartlett <abartlet <at> samba.org> wrote:
>         On Sun, 2006-07-30 at 16:04 -0700, Murali Bashyam wrote:
>         > On samba4 TP2, i am noticing the following problem when
>         there are multiple
>         > trans2 responses to a single trans2 request.
>         >
>         > After processing the first response, smb_raw_trans2_recv
>         calls 
>         > smbcli_request_receive_more to handle the next response
>         message, and ends up
>         > blocking in epoll_wait waiting for a read event. Some time
>         later when the
>         > next trans2 response message is received, the wait unblocks,
>         and then ends 
>         > up calling packet_receive (via
>         smbcli_transport_event_handler). packet_recv
>         > checks for the 'processing' flag in the packet context, and
>         since this flag
>         > is still set, it simply marks the fde not readable and
>         returns without 
>         > picking up the next message, ultimately leading to a
>         timeout. The
>         > 'processing' flag in the packet context is not reset until
>         we return from
>         > smb_raw_trans2_recv back to the smbcli_transport_finish_recv
>         function. This 
>         > seems to be leading to a deadlock in the multiple trans2
(Continue reading)

Friend | 1 Aug 09:52 2006
Picon

Samba problem

Hi,

I am working in samba 3 in hpux11.11 platform.Here v r having more than 50
samba shares in a 4TB size SAN.One of those share s having 400 GB size(share
name is mabudata).The total no of write list permissions to groups to that
share is more than 110 now.Now the recently added users r having some
problems with that share like someone cant read,someine cant write.When i
check the smb.conf file, its showing some miscellanious letters in the place
of the recently added goups place.I replace with an old smb.conf file and
added the new goups there,but after sometime the file again gets
corrupted.Is there any limitations in maximum no of groups per share,if
there how can i increase it?I m sending u my smb.conf file as an attchment,
i have marked the particular share with red colour and that corrupted part
as bold(page no 8).Pls check it and reply to me soon
Attachment (smb.conf detaild.doc): application/msword, 95 KiB

Gmane