Pavel, does this happen for smb as well as for smb2 also? Not sure how can authentication mechanism affect accessibility (since ntlmssp uses ntlmv2 underneath anyway!) Regards, Shirish On Mon, Jul 29, 2013 at 11:41 AM, Pavel Shilovsky <piastryyy@xxxxxxxxx> wrote: > For sec=ntlmssp unix query path info call returns OK for a > non-existing uppercase filename if a lowercase one exists. E.g.: stat > ABC return info about 'abc' file. > > But for sec=ntlmv2 or sec=ntlm this call fails with > STATUS_OBJECT_NAME_NOT_FOUND error code. > > This difference was found on upgrade from v3.7 to v3.8 kernel due to > changing the default security mechanism to NTLMSSP. > > Any thoughts on this? > > -- > Best regards, > Pavel Shilovsky. > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
