headers
George K Colley | 1 Aug 2011 02:50
Picon
Favicon

Re: [MAC Lion] smbclient "Open AndX Request->STATUS_NOT_SUPPORTED"


On Jul 31, 2011, at 10:43 AM, Volker Lendecke wrote:

> On Sat, Jul 30, 2011 at 09:15:54PM -0500, Christopher R. Hertel wrote:
>> That should work.
>> 
>> ...but if smbclient negotiates "NT LM 0.12", receives CAP_NT_SMBS from the
>> server, and sends CAP_NT_SMBS back to the server, then it should always use
>> NT_CREATE&X, not OPEN&X.
> 
> I'd rather go with try-and-error method. We might put down
> in the client structure that open&x is not supported, but
> relying on capability bits is a bad idea IMO. Too many
> broken or deliberately crippled CIFS servers out there.
I have never ran into a server that didn't work in the way that Chris says above. But I will leave the decision
on how the smbclient should work up to the Samba Team. 

George
> 
> Volker
> 
> -- 
> SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
> phone: +49-551-370000-0, fax: +49-551-370000-9
> AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
Permalink | Reply | 8 comments |
headers
Andrew Bartlett | 1 Aug 2011 14:27
Picon
Favicon

Re: Fwd: Re: Missing log file in 4.0.0alpha17-GIT-233ba37

On Thu, 2011-07-28 at 14:43 +0200, Daniele Dario wrote:
> Same here.
> 
> With version 4.0.0alpha16-GIT-b25f7d4 built with standard prefix the log
> was in /usr/local/samba/var/log/
> With version 4.0.0alpha17-GIT-481f05c no log found (I've tried with and
> without the "log file = ..." directive in smb.conf).
> 
> Anyway thanks for your great job guys.

Sorry about that.  I broke this recently, and fixed it in
481f1e601daafd186c504476f7efa1b557099105

Please let me know if current master still fails.

Andrew Bartlett

--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Permalink | Reply | 2 comments |
headers
Fatman | 1 Aug 2011 15:10
Picon

Re: SAMBA_4.0.0ALPHA17_DEVELOPERBUILD not found (required by samba)

I really ran "sudo samba". I will check the output of "which samba" later but I suspect it will be
"/usr/local/bin/samba", or similar.
Permalink | Reply | 0 comments |
headers
Daniele Dario | 1 Aug 2011 15:31
Picon

Re: Fwd: Re: Missing log file in 4.0.0alpha17-GIT-233ba37

Hi Andrew,
I made a git pull than ./configure.developer, make but with make
quicktest now I get:

FAILED (4 failures and 2 errors in 6 testsuites)

A summary with detailed information can be found in:
  ./st/summary
ERROR: test failed with exit code 1
make: *** [quicktest] Error 1

and .st/summary contains

= Failed tests =
== samba4.smb.signing disabled on with -k no --signing=off
domain-creds(s3member) ==
command: /root/samba4/samba-master/bin/smbtorture --configfile=
$SMB_CONF_PATH --maximum-runtime=$SELFTEST_MAXTIME --target=samba4
--basedir=$SELFTEST_TMPDIR --option=torture:progress=no --format=subunit
--option=torture:quick=yes $LISTOPT //$NETBIOSNAME/tmp -k no
--signing=off -U$DC_USERNAME%$DC_PASSWORD base.xcopy $LOADLIST 2>&1
| /root/samba4/samba-master/selftest/filter-subunit $LISTOPT
--fail-on-empty --prefix="samba4.smb.signing disabled on with -k no
--signing=off domain-creds."
expanded command: /root/samba4/samba-master/bin/smbtorture
--configfile=/root/samba4/samba-master/st/client/client.conf
--maximum-runtime=1200 --target=samba4
--basedir=/root/samba4/samba-master/st/tmp --option=torture:progress=no
--format=subunit --option=torture:quick=yes
$LISTOPT //LOCALADMEMBER29/tmp -k no --signing=off -UAdministrator%
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lukasz Zalewski | 1 Aug 2011 16:46
Picon
Favicon

Re: Fwd: Re: Missing log file in 4.0.0alpha17-GIT-233ba37

On 01/08/11 13:27, Andrew Bartlett wrote:
> On Thu, 2011-07-28 at 14:43 +0200, Daniele Dario wrote:
>> Same here.
>>
>> With version 4.0.0alpha16-GIT-b25f7d4 built with standard prefix the log
>> was in /usr/local/samba/var/log/
>> With version 4.0.0alpha17-GIT-481f05c no log found (I've tried with and
>> without the "log file = ..." directive in smb.conf).
>>
>> Anyway thanks for your great job guys.
>
> Sorry about that.  I broke this recently, and fixed it in
> 481f1e601daafd186c504476f7efa1b557099105
>
> Please let me know if current master still fails.
>
> Andrew Bartlett
>
>

Hi Andrew,
The log file is back :)

Many thanks

Luk
Permalink | Reply | 0 comments |
headers
Lukasz Zalewski | 1 Aug 2011 17:37
Picon
Favicon

Forwarded krb ticket causes crash in Version 4.0.0alpha17-GIT-2d23dff

Hi list,
Our attempts to use a forwardable krb ticket result in a crash. Below is 
a sniplet of the log entry:

[2011/08/01 16:29:10,  3] 
../source4/auth/kerberos/krb5_init_context.c:69(smb_krb5_debug_wrapper)
   Kerberos: TGS-REQ user <at> MYDOM from ipv4:xxx.xxx.xxx.xxx:xxxxx for 
ldap/myldaphost <at> MYDOM [canonicalize, renewable, forwardable]
*** glibc detected *** /usr/local/samba/sbin/samba: malloc(): smallbin 
double linked list corrupted: 0x0000000002c27cd0 ***

Please let me know what other debug information i should provide

Regards

Luk
Permalink | Reply | 0 comments |
headers
Christopher R. Hertel | 1 Aug 2011 17:43

Re: [MAC Lion] smbclient "Open AndX Request->STATUS_NOT_SUPPORTED"

In theory, theory and practice are the same.  In practice, they're not.

Volker:  You're right to be cautious here, but I think that counting
         on a broken CIFS server to send back a correct error code is
         just as risky as counting on the CAP_NT_SMBS bit to be correct.

Sending the NT_STATUS_NOT_SUPPORTED error is correct behavior if the command
is recognized but not supported.  We made that clear in [MS-CIFS], but I
don't believe that it was clearly specified in any earlier documentation.
The use of CAP_NT_SMBS was documented earlier.

I'm not sure why CAP_NT_SMBS is there.  It's fairly silly to negotiate NT LM
0.12 and then not support the full set of NT SMB commands.

Chris -)-----

George K Colley wrote:
> On Jul 31, 2011, at 10:43 AM, Volker Lendecke wrote:
> 
>> On Sat, Jul 30, 2011 at 09:15:54PM -0500, Christopher R. Hertel wrote:
>>> That should work.
>>>
>>> ...but if smbclient negotiates "NT LM 0.12", receives CAP_NT_SMBS from the
>>> server, and sends CAP_NT_SMBS back to the server, then it should always use
>>> NT_CREATE&X, not OPEN&X.
>> I'd rather go with try-and-error method. We might put down
>> in the client structure that open&x is not supported, but
>> relying on capability bits is a bad idea IMO. Too many
>> broken or deliberately crippled CIFS servers out there.
> I have never ran into a server that didn't work in the way that Chris says above. But I will leave the decision
(Continue reading)

Permalink | Reply | 7 comments |
headers
Christopher R. Hertel | 2 Aug 2011 00:08

Upcoming CIFS Plugfest and SNIA SDC.

Just a reminder to everyone that the SNIA CIFS Plugfest is just over a month
away.

If you're a LinkedIn user, please go ahead and RSVP:
  http://events.linkedin.com/Storage-Developer-Conference-2011/pub/720311

  That'll draw some attention to the event.

If you are also a member of the Samba group on LinkedIn, please post your
comments under the discussion topic for this year's SNIA SDC.

Chris -)-----

--

-- 
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh <at> ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh <at> ubiqx.org
Permalink | Reply | 0 comments |
headers
Andrew Bartlett | 2 Aug 2011 01:01
Picon
Favicon

Re: [PATCH] support for kerberos in plugin DC code

On Fri, 2011-07-29 at 17:09 +0200, Stefan (metze) Metzmacher wrote:
> >> I'd like you to give quite some time to review and decide if it is ok.
> >> I have been opposed on introducing gensec in s3 for a few reasons. One
> >> is dependencies, the other is that IIRC gensec does not create new event
> >> loops bu allows nesting of loops. That is something too dangerous for
> >> the file server imho.
> > 
> > Yes, this needs a lot of review, I hope to get some time in the next days.
> 
> Here're my first result, but I'll do more review on monday:

I've addressed all these issues (including the
auth_ntlmssp_steal_session_info(), but not removing the auth4_context
for the reasons I've explained).  Can you please let me know soon if you
have any further comments that cannot be addressed in-tree, as I would
like to move forward with this work.

Simo,

You asked for time to review these changes.  Have you found that time,
or can we work our any remaining issues after this lands in master?

Thanks,

Andrew Bartlett

--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
(Continue reading)

Permalink | Reply | 3 comments |
headers
Andrew Bartlett | 2 Aug 2011 05:34
Picon
Favicon

Re: Of challenges in loadparm

On Fri, 2011-07-29 at 14:08 +0200, Michael Adam wrote:
> Hi Andrew,
> 
> Andrew Bartlett wrote:
> > 
> > I guess I don't really see why the 'loop' here is an issue, given the
> > separate build stages involved.  As to the significance of leading
> > spaces, aside from being a convention that has worked quite well for
> > Samba for quite some time, I don't mind if it's changed to a CPP token
> > that is defined away. 
> 
> Yeah, with a token I would feel more comfortable. It is more
> explicit. It is so easy for the human eye (especially mine) to
> overlook a little whitespace here and there.
> 
> Apart from that it is a matter of personal taste probably,
> or paranoia, that I don't like to have some script parse
> the C file to generate headers that the C file (and other files)
> then include. I just feel more comfortable with having to
> explicitly maintain prototype headers. But again, this is
> a personal thing, I can't really give better arguments right now.
> 
> > I would like to see this stage extended to restore automatic prototype
> > generation of loadparm functions, in the interim before a more grand
> > scheme can be achieved.  Doing so would make changes in this area much
> > less error prone (I'm pretty sure there are both missing and extra
> > prototypes at the moment). 
> 
> Well, I think I will start out with creating dedicated header
> file(s) for the param/ modules.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane