Date: Tue, 19 Sep 2006 22:00:07 -0700 From: Deomid Ryabkov <myself@rojer.pp.ru> To: freebsd-hackers@freebsd.org Subject: Re: Symlinks on read-only FS Message-ID: <4510CAD7.5080001@rojer.pp.ru> In-Reply-To: <10609200356.AA21953@pluto.rain.com> References: <10609200101.AA21405@pluto.rain.com> <4510AF6D.2060809@rojer.pp.ru> <10609200356.AA21953@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Perry Hutchison wrote: > So the sort of write access being validated here would be writing to > the symlink itself (i.e. the definition)? symlinks are dereferenced during name lookup and are not affected by the write mount options of the filesystems they reside on. you can open a file for write by accessing a symlink pointing to it, even though the symlink itself may reside on a read-only filesystem. and you can disregard what i said in my previous post: there's no interface to change the symlink after it was created. actually, i'm not sure there is a real-world case in which this code would be invoked with VLNK. checking write permissions on a symlink? access(2)/eaccess(2) dereference symlinks. but if, for whatever reason, someone calls VOP_ACCESS on read-only UFS filesystem, checking if writing to symlink itself is ok, it will be denied. which makes sense. -- Deomid Ryabkov aka Rojer myself@rojer.pp.ru rojer@sysadmins.ru ICQ: 8025844 [-- Attachment #2 --] 0 *H 01 0 + 0 *H =00b;^`@3[m0 *H 0b1 0 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 060401182654Z 070401182654Z0_10URyabkov10 U*Deomid10UDeomid Ryabkov1!0 *H myself@rojer.pp.ru0"0 *H 0 sQIk\c!yX6.ܧѧcAƖ THQX>TMrhL2#UK,Uv [CLGsk/=eopy|?aNx*;9;8S06"'+ePzNt; Ȋ.*'Ɔkc$!YuDW27˦UxPT+g|*%qe=T_-%ΈY /0-0 U 0myself@rojer.pp.ru0 U 0 0 *H &7fd·%3WĭcpƐp++N }qfPT0[ 5IXe3A9Gv_*zYvv;bɢ @`E6&2Rߙ00b;^`@3[m0 *H 0b1 0 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 060401182654Z 070401182654Z0_10URyabkov10 U*Deomid10UDeomid Ryabkov1!0 *H myself@rojer.pp.ru0"0 *H 0 sQIk\c!yX6.ܧѧcAƖ THQX>TMrhL2#UK,Uv [CLGsk/=eopy|?aNx*;9;8S06"'+ePzNt; Ȋ.*'Ɔkc$!YuDW27˦UxPT+g|*%qe=T_-%ΈY /0-0 U 0myself@rojer.pp.ru0 U 0 0 *H &7fd·%3WĭcpƐp++N }qfPT0[ 5IXe3A9Gv_*zYvv;bɢ @`E6&2Rߙ0?0 0 *H 01 0 UZA10U Western Cape10U Cape Town10U Thawte Consulting1(0&U Certification Services Division1$0"UThawte Personal Freemail CA1+0) *H personal-freemail@thawte.com0 030717000000Z 130716235959Z0b1 0 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00 *H 0 Ħ<UsUNʙZ hup [v :aQP 0cZ,p+Z?qV˯< 6$*+w=+>@dקe*TH<a@ dr` 00U 0 0CU <0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0 U 0)U "0 0 10UPrivateLabel2-1380 *H HP . fgCL!6 -6/ P p<ab:~ t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$ F]_eO1d0`0v0b1 0 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA;^`@3[m0 + 0 *H 1 *H 0 *H 1 060920050007Z0# *H 1a 4\7\[ K+D%^0R *H 1E0C0 *H 0*H 0 *H @0+0 *H (0 +71x0v0b1 0 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA;^`@3[m0 *H 1xv0b1 0 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA;^`@3[m0 *H ]HJsyk=`DK=Yg-'T/ڇ%Fgr}e?" \nXp(B(~ /Z Gьj9ܸR<ktuh 8uYgPu#T:#A<iM8EUJ|phGu=[UJcdZƢ/ Og8N,f şKq6SAaGuwm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4510CAD7.5080001>