linux-kernel - Re: problems with latest smbfs changes on 2.4.34 and security backports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <po0uq29lb4fk9pepuh67d4dlmsfc3koshe@4ax.com>
Date:	Thu, 18 Jan 2007 16:59:24 +1100
From:	Grant Coady <grant_lkml@...o.com.au>
To:	Willy Tarreau <w@....eu>
Cc:	Grant Coady <gcoady.lk@...il.com>,
	Santiago Garcia Mantinan <manty@...ian.org>,
	linux-kernel@...r.kernel.org, debian-kernel@...ts.debian.org,
	dannf@...nf.org
Subject: Re: problems with latest smbfs changes on 2.4.34 and security backports

On Thu, 18 Jan 2007 05:21:16 +0100, Willy Tarreau <w@....eu> wrote:

>Hi Grant !
>
>On Thu, Jan 18, 2007 at 11:09:57AM +1100, Grant Coady wrote:
>(...)
>> > 	} else {
>> >-		mnt->file_mode = mnt->dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
>> >-						S_IROTH | S_IXOTH | S_IFREG;
>> >-		mnt->dir_mode = mnt->dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
>> >-						S_IROTH | S_IXOTH | S_IFDIR;
>> >+		mnt->file_mode = S_IRWXU | S_IRGRP | S_IXGRP |
>> >+				S_IROTH | S_IXOTH | S_IFREG | S_IFLNK;
>> >+		mnt->dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
>> >+				S_IROTH | S_IXOTH | S_IFDIR;
>> > 		if (parse_options(mnt, raw_data))
>> > 			goto out_bad_option;
>> 
>> I'm comparing 2.4.33.3 with 2.4.34, with 2.4.34 and above patch symlinks 
>> to directories seen as target, nor can they be created (Operation not 
>> permitted...)
>
>Thanks very much Grant for the test. Could you try a symlink to a file ?

"Operation not permitted"

>And while we're at it, would you like to try to add "|S_IFLNK" to
>mnt->dir_mode ? If my suggestion was stupid, at least let's test it to
>full extent ;-)

Yep, already tried the obvious ;)  no difference :(

2.4.33.5 onwards also have a problem with symlinks, but it is slightly 
different presentation, the directory symlinks appear as normal files.

With 2.4.33.7 one is able to create file and directory symlinks, though 
the links appear as files.  Content problem as noted by OP:

grant@...pro:/home/other$ uname -r
2.4.33.7
grant@...pro:/home/other$ cat file
this is a test
grant@...pro:/home/other$ cat filelink
thisgrant@...pro:/home/other$

grant@...pro:/home/other$ mkdir directory
grant@...pro:/home/other$ ln -s directory directorylink
grant@...pro:/home/other$ cp file* directory
grant@...pro:/home/other$ ls directory
file*  filelink*
grant@...pro:/home/other$ ls directorylink
directorylink*

Now, WinXP sees the contents of directorylink:

X:\>cd directorylink

X:\directorylink>dir
 Volume in drive X is other
 Volume Serial Number is 107E-052F

 Directory of X:\directorylink

2007-01-18  16:36    <DIR>          .
2007-01-18  16:33    <DIR>          ..
2007-01-18  16:36                15 file
2007-01-18  16:36                 4 filelink
               2 File(s)             19 bytes
               2 Dir(s)   2,558,922,752 bytes free

X:\directorylink>type file
this is a test

X:\directorylink>type filelink
this
X:\directorylink>
>
>I had another idea looking at the code but since I really don't know it,
>I would not like to propose random changes till this magically works. I'd
>wait for Dann who understood the code.

Grant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/