[Fsp-users] Enable remote directory deletion on FSP-Server?
UDP File transfer protocol
Brought to you by:
hsn
Menu
▾
▴
[Fsp-users] Enable remote directory deletion on FSP-Server?
|
From: Stefan B. <sb...@fr...> - 2009-08-19 16:01:49
|
Hello all
I live in a city with an Ad-Hoc meshed WLAN-network (Freifunk firmware
on Linksys WRT54GL). Packetloss, unstable latency and routing errors are
always a challenge for TCP-connections, so I try FSP on our network. :-)
My idea is to run a FSP-Server with full read/write rights as first
filesharing experiment on our network. The server is only accessible on
the public WLAN meshnetwork, access from Internet is not possible.
After many tests this is my current situation:
Now I can create directories, up- and download files, rename files and
directories and delete files.
But it's not possible to delete such a created directory!!!
Error on client:
$ frmdircmd test
Can't remove test: rmdir: cannot unlink
Logmessages on console on server in debug mode:
rcv (DELDIR,key=0x2F61,seq=0xE460,len=14,len2=0,pos=0) <---
sbraun-laptop.lan
Validating path = Incoming/test len=14
looking for directory Incoming/test in statcache.
putting into statcache: Incoming/test
[LOG] Wed Aug 19 17:11:06 2009 sbraun-laptop.lan
DELDIR /Incoming/test: ERROR rmdir: cannot unlink
snd (ERR,key=0x9668,seq=0xE460,len=21,len2=0,pos=0) ---> 10.248.9.58
Info about client:
Linux Ubuntu Hardy (8.04), fsp 2.81.b24-2ubuntu1
Info about server:
Linux Ubuntu Hardy (8.04), fspd 2.81.b24-2ubuntu1
$ fver
Remote FSP version: fspd 2.8.1b24
Logging of all server transactions is ENABLED.
Remote server is run in READ/WRITE mode.
Server DOESN'T REQUIRE connections to reverse.
Remote server is run in PUBLIC mode.
Remote server throughput control is DISABLED.
Max. payload size supported by server is 1370 bytes.
-fspd is running in public mode as root (I know, a security risk...)
-fspd uses the dotfiles as access control
-I see no error in file/directory ownership/permissions:
/home/fsp# ls -ali
insgesamt 20
6488065 drwxr-xr-x 3 root root 4096 2009-08-19 16:14 .
2 drwxr-xr-x 11 root root 4096 2009-03-03 17:08 ..
6488112 -rw------- 1 root root 53 2009-08-19 16:14 .FSP_CONTENT
6488103 drwxr-xr-x 4 root root 4096 2009-08-19 17:08 Incoming
6488068 -rw-r--r-- 1 root root 127 2009-08-19 14:41 .README
/home/fsp/Incoming# ls -ali
insgesamt 5840
6488103 drwxr-xr-x 4 root root 4096 2009-08-19 17:08 .
6488065 drwxr-xr-x 3 root root 4096 2009-08-19 16:14 ..
6488111 -rw------- 1 root root 89 2009-08-19 17:10 .FSP_CONTENT
6488067 -rw------- 1 root root 0 2009-08-19 16:16 .FSP_OK_ADD
6488066 -rw------- 1 root root 0 2009-08-19 16:16 .FSP_OK_DEL
6488069 -rw------- 1 root root 0 2009-08-19 16:16 .FSP_OK_MKDIR
6488083 -rw------- 1 root root 0 2009-08-19 16:16 .FSP_OK_RENAME
6488104 -rw------- 1 root root 29 2009-08-19 16:16 .FSP_OWNER
6488071 drwx------ 2 root root 4096 2009-08-19 17:11 test
6488113 drwx------ 2 root root 4096 2009-08-19 16:36 test2
6488105 -rw-r--r-- 1 root root 5940851 2009-08-19 16:16 Will_Smith.mp3
/home/fsp# cat Incoming/.FSP_OWNER
0-255.0-255.0-255.0-255 O
/home/fsp/Incoming# ls -ali test*
test:
insgesamt 12
6488071 drwx------ 2 root root 4096 2009-08-19 17:11 .
6488103 drwxr-xr-x 4 root root 4096 2009-08-19 17:08 ..
6488114 -rw------- 1 root root 36 2009-08-19 17:11 .FSP_OWNER
test2:
insgesamt 12
6488113 drwx------ 2 root root 4096 2009-08-19 16:36 .
6488103 drwxr-xr-x 4 root root 4096 2009-08-19 17:08 ..
6488107 -rw------- 1 root root 0 2009-08-19 16:36 .FSP_OK_ADD
6488106 -rw------- 1 root root 0 2009-08-19 16:36 .FSP_OK_DEL
6488108 -rw------- 1 root root 0 2009-08-19 16:36 .FSP_OK_MKDIR
6488109 -rw------- 1 root root 0 2009-08-19 16:36 .FSP_OK_RENAME
6488110 -rw------- 1 root root 36 2009-08-19 16:36 .FSP_OWNER
/home/fsp/Incoming# cat test/.FSP_OWNER
10-10.248-248.9-9.58-58 O Creator
I set the owner to *.*.*.*, but fspd converted it to
0-255.0-255.0-255.0-255. I think that's ok and should work.
The IP on the client is 10.258.9.58, and fspd wrote
10-10.248-248.9-9.58-58 as owner. Is that correct behaving?
As mentioned above, when I try to delete the empty directory "test",
then I get "Can't remove test: rmdir: cannot unlink". I think fspd can't
remove this directory because it isn't really empty because of the
generated .FSP_OWNER file!
After deleting this .FSP_OWNER file manually on the server, I get this
error message on client: "Can't remove test: Permission denied".
The server debug log says no more on this topic:
rcv (DELDIR,key=0x03D8,seq=0x7C70,len=14,len2=0,pos=0) <---
sbraun-laptop.lan
Validating path = Incoming/test len=14
looking for directory Incoming/test in statcache.
putting into statcache: Incoming/test
[LOG] Wed Aug 19 17:35:36 2009 sbraun-laptop.lan
DELDIR /Incoming/test: ERROR Permission denied
snd (ERR,key=0x7095,seq=0x7C70,len=18,len2=0,pos=0) ---> 10.248.9.58
Do you need more info on this topic?
Thank you very much for your help.
Greetings,
Stefan Braun.
|
