Re: what's next for the linux kernel?

From: Julian Blake Kongslie (jblake_at_omgwallhack.org)
Date: 10/05/05

  • Next message: Aurelien Jarno: "[PATCH 2.6.14-rc3] sis5513.c: enable ATA133 for the SiS965 southbridge"
    Date:	Wed, 5 Oct 2005 13:57:04 -0700
    To: Bas Westerbaan <bas.westerbaan@gmail.com>
    
    
    

    On Wed, 5 Oct 2005 22:51:32 +0200
    Bas Westerbaan <bas.westerbaan@gmail.com> wrote:

    > You can delete a directory entry to a file if you have proper
    > permission to the directory.
    >
    > You cannot read or write the file if the file doesn't give you
    permission to.
    >
    > A hard link makes an additional directory entry to a certain file. You
    > delete the directory entry to the file, not the file.
    >
    > And permissions are the same for all instances of the file.
    >
    > My 2 cents.

    That is the UNIX model, yes. And I think it makes perfect sense. And as
    a side effect, we can delete links to files which we do not own, and
    cannot write to.

    Does NetWare have an equivalent of hardlinks?

    -- 
    -Julian Blake Kongslie
    <jblake@omgwallhack.org>
    
    

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



  • Next message: Aurelien Jarno: "[PATCH 2.6.14-rc3] sis5513.c: enable ATA133 for the SiS965 southbridge"

    Relevant Pages

    • Re: whats next for the linux kernel?
      ... You can delete a directory entry to a file if you have proper ... You cannot read or write the file if the file doesn't give you permission to. ... A hard link makes an additional directory entry to a certain file. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: Call for review: restricted hardlinks.
      ... > Seems somewhat paranoid to me. ... You already need write permission on the ... The "classic hard link attack" is to find a writable directory in a ...
      (FreeBSD-Security)
    • Re: Call for review: restricted hardlinks.
      ... +> When you restrict links, do you want to restrict copying as well? ... You already need write permission on the ... For example he is able to create hard link to some set-uid binary. ... Administrator have to be really careful when fixing such problems ...
      (FreeBSD-Security)
    • Re: [PATCH] Realtime LSM
      ... There's no added security risk if gid changes ... > halfway through the permission check, and the other variables are used ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: freed_symbols [Re: People, not GPL [was: Re: Driver Model]]
      ... > combined work and make it so others could not use that version without ... Not without being in violation of the original licence. ... but about your permission to use the ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)