in reply to Re: Re: File::Find considered hard?
in thread File::Find considered hard?

A fine perpetuation of ignorance.
Really? etcshadow was claiming he could create a file on my system. The only way to do that is to break in - if he can do that, problems with find are the least of my worries.

Abigail

Replies are listed 'Best First'.
Re: Re: File::Find considered hard?
by tilly (Archbishop) on Mar 15, 2004 at 10:47 UTC
    I'm glad that you trust all of your users.

    Many sysadmins can't. For an extreme example, any sysadmin at a university.

    Would you recommend your technique for them?

[reply]
      I'm glad that you trust all of your users.
      I trust myself, yes. But I also trust myself that if I were to have users again, they would only have write access to a limited set of directores.
      Would you recommend your technique for them?
      It entirely depends on what they are using find for, (that is, what they are going to do with the results), under which UID they run, and on which directory they run find. Turning on taintness is usually a good idea when running programs with UID == 0. Checking to see whether the returned values start with the expected prefix doesn't hurt. Using -print0 and $/ = "\0" might work too.

      Abigail

[reply]

In Section Meditations