| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Directory/File Access Permissions for COPY and Generic File Access Functions |
| Date: | 2014-10-29 21:22:22 |
| Message-ID: | CAM-w4HNtR=nu1jV_536AmDPt5uYSm=xpu_J2bgUuD3YpB39ceQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 29, 2014 at 3:52 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> And it still doesn't protect against the case where you hardlink to a file
> and then the permissions on that file are later changed.
Fwiw that's not how hard links work, at least UFS semantics
permissions such as ext2 etc. Hard links are links to the same inode
and permissions are associated with the file. There are other
filesystems out there though. AFS for example associates permissions
with directories.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-10-29 21:46:32 | Re: Directory/File Access Permissions for COPY and Generic File Access Functions |
| Previous Message | Kevin Grittner | 2014-10-29 21:18:28 | Re: Directory/File Access Permissions for COPY and Generic File Access Functions |