All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@blue-labs.org>
To: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: vda@port.imtp.ilyichevsk.odessa.ua,
	James A Sutherland <jas88@cam.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: x bit for dirs: misfeature?
Date: Mon, 19 Nov 2001 12:15:34 -0500	[thread overview]
Message-ID: <3BF93E36.5040603@blue-labs.org> (raw)
In-Reply-To: <200111191647.KAA36330@tomcat.admin.navo.hpc.mil>

>
>
>>I know. I'd like to hear anybody who have a directory with r!=x
>>on purpose (and quite curious on that purpose). UNIX gugus, anybody?
>>
>
>It's used to hide files in anonymous FTP for for one. It prevents you from
>retrieving files that you don't know the name of. Yes, a brute force attempt
>to open MAY work to find the unknown file, it will take a long time, and you
>are most likely to be detected. The anonymous FTP use is usually in an incoming
>directory - the files are put there from remote individuals, and are hidden
>(unless someone is a good guesser/or a poor name chosen) until the
>administrator examines/moves them.
>

I use it for more than just ftp.  I chmod 710 ~ and have ~ in the 
web/email groups.  It stops prying eyes unless they know what the 
filename is.

David


  reply	other threads:[~2001-11-19 17:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 16:22 x bit for dirs: misfeature? vda
2001-11-19 14:36 ` James A Sutherland
2001-11-19 16:58   ` vda
2001-11-19 15:04     ` Tim Waugh
2001-11-19 15:29       ` Richard B. Johnson
2001-11-19 16:00     ` James A Sutherland
2001-11-19 17:43       ` Kai Henningsen
2001-11-19 18:24       ` vda
2001-11-19 16:44         ` Horst von Brand
2001-11-19 17:24           ` James A Sutherland
2001-11-19 19:39             ` vda
2001-11-19 19:07               ` James A Sutherland
2001-11-20 13:03                 ` vda
2001-11-19 21:01               ` Flavio Stanchina
2001-11-19 19:21           ` vda
2001-11-19 18:14             ` Horst von Brand
2001-11-20 11:20               ` Anton Altaparmakov
2001-11-20 12:01                 ` Alexander Viro
2001-11-20 15:08                 ` Anton Altaparmakov
2001-11-20 17:18                 ` Mike Castle
2001-11-20 17:37                   ` Alexander Viro
2001-11-20 12:58               ` vda
2001-11-19 16:47     ` Jesse Pollard
2001-11-19 17:15       ` David Ford [this message]
2001-11-19 17:37     ` Pascal Schmidt
2001-11-19 18:42     ` J Sloan
2001-11-19 14:46 ` Alexander Viro
2001-11-19 17:03   ` vda
2001-11-19 15:07     ` Shaya Potter
2001-11-19 15:12     ` Alexander Viro
2001-11-19 15:19     ` Mathijs Mohlmann
2001-11-19 15:36     ` Gerhard Mack
2001-11-19 16:19     ` Horst von Brand
2001-11-19 22:36     ` Lionel Bouton
2001-11-19 15:12 ` Mathijs Mohlmann
2001-11-19 17:41   ` vda
2001-11-20  0:38 ` Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2001-11-20 16:05 Thomas Hood
2001-11-21 10:34 ` Helge Hafting
2001-11-21 23:00   ` Mike Fedyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BF93E36.5040603@blue-labs.org \
    --to=david@blue-labs.org \
    --cc=jas88@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pollard@tomcat.admin.navo.hpc.mil \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.