Re: problems with latest smbfs changes on 2.4.34 and security backports
On Mon, 22 Jan 2007 10:18:16 +0100, Willy Tarreau <w@1wt.eu> wrote:
>Grant, just to be sure, are you really certain that you tried the fixed kernel ?
>It is possible that you booted a wrong kernel during one of your tests. I'm
>intrigued by the fact that it changed nothing for you and that it fixed the
>problem for Santiago.
Closest I get to Santiago's results are with the 2.4.33.7 plus the patch,
with 'use default NLS' option turned on, as well as the unix extensions.
2.4.34 was a no go for me. Changing the default NLS made no difference,
now trying with unix extensions turned on. . . Yeah, that works, apart
from the test file gaining execute bits, compared to operation under
2.4.33.3, this is 2.4.34 + patch + default NLS and unix extensions:
grant@sempro:/home/other$ cat dirlink/filelink
this is a test
grant@sempro:/home/other$ echo "this is a test" > testfile
grant@sempro:/home/other$ ls -l
total 4096
drwxr-xr-x 1 grant wheel 0 2007-01-21 11:44 dir/
lrwxr-xr-x 1 grant wheel 3 2007-01-21 11:43 dirlink -> dir/
-rwxr-xr-x 1 grant wheel 15 2007-01-21 11:43 file*
lrwxr-xr-x 1 grant wheel 4 2007-01-21 11:44 filelink -> file*
drwxr-xr-x 1 grant wheel 0 2007-01-22 10:45 test/
-rwxr-xr-x 1 grant wheel 15 2007-01-22 21:31 testfile*
lrwxr-xr-x 1 grant wheel 4 2007-01-22 21:29 testlink -> test/
grant@sempro:/home/other$ ln -s testfile testfilelink
grant@sempro:/home/other$ cat testfilelink
this is a test
The fix depends on the smbfs configuration? Is this the requirement?
I ask as the other mode of operation (unix extensions turned off): do
not display symlinks, prevent creation of symlinks, seems to be logically
self-consistent, as well as matching what I see from a 'doze box.
Grant.
Reply to: