Control: reassign -1 src:linux 4.13.4-1
Control: tag -1 moreinfo

On Thu, 2017-10-05 at 10:18 +0200, matecs wrote:
> Package: linux-image-amd64
> Version: 4.13+86
> Severity: normal
> 
> Dear Maintainer,
> 
> i'm mounting my shares through cifs for years.
> when sid pulled the 4.13 kernel, i noticed that these mounts
> automatically get the file_mode=0755 and dir_mode=0755 options.

It appears that this indicates the server does not support Unix
extensions.

What is the file server running?

> the fstab looks like this:
> //nas.mchome.nop.hu/mc36     /nfs   cifs 
> user=mc36,password=***,uid=mc36,gid=mc36   0   0
> 
> then the resulting mount looks like this:
> //nas.mchome.nop.hu/mc36 on /nfs type cifs 
> (rw,relatime,vers=3.0,cache=strict,username=mc36,domain=,uid=1000,for
> ceuid,gid=1000,forcegid,addr=2001:0db8:1001:0255:0200:4eff:fe36:4e35,
> file_mode=0755,dir_mode=0755,nounix,serverino,mapposix,rsize=1048576,
> wsize=1048576,echo_interval=60,actimeo=1,user=mc36)

And the 'nounix' confirms that.

Are there any messages in the kernel log relating to cifs?

> things look similarly if i add vers=2.0 to the fstab. only vers=1.0 
> solves the issue.
[...]

Version 1 should no longer be used as it has well-known and unfixable
security issues.  The default protocol version for the cifs filesystem
was changed to 3 in Linux 4.13:
https://git.kernel.org/linus/eef914a9eb5eb83e60eb498315a491cd1edc13a1

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to