Date: Mon, 18 Jul 2011 10:55:58 +0200 From: Frank Bonnet <f.bonnet@esiee.fr> To: freebsd-questions@freebsd.org Subject: Re: Tools to find "unlegal" files ( videos , music etc ) Message-ID: <4E23F51E.7040907@esiee.fr> In-Reply-To: <20110718104545.2aacbd1b.freebsd@edvax.de> References: <4E23E6DD.6050901@esiee.fr> <20110718101029.531397d9.freebsd@edvax.de> <4E23F0FE.3070305@esiee.fr> <20110718104545.2aacbd1b.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/18/2011 10:45 AM, Polytropon wrote: > On Mon, 18 Jul 2011 10:38:22 +0200, Frank Bonnet wrote: >> On 07/18/2011 10:10 AM, Polytropon wrote: >>> On Mon, 18 Jul 2011 09:55:09 +0200, Frank Bonnet wrote: >>>> Hello >>>> >>>> Anyone knows an utility that I could pipe to the "find" command >>>> in order to detect video, music, games ... etc files ? >>>> >>>> I need a tool that could "inspect" inside files because many users >>>> rename those filename to "inoffensive" ones :-) >>> One way could be to define a list of file extensions that >>> commonly matches the content you want to track. Of course, >>> the file name does not directly correspond to the content, >>> but it often gives a good hint to search for *.wmv, *.flv, >>> *.avi, *.mp(e)g, *.mp3, *.wma, *.exe - and of course all >>> the variations of the extensions with uppercase letters. >>> Also consider *.rar and maybe *.zip for compressed content. >>> >>> If file extensions have been manipulated (rare case), the >>> "file" command can still identify the correct file type. >>> >>> >>> >>> >> yes thanks , gonna try with the file command > You could make a simple script that lists "file" output for > all files (just to be sure because of possible suffix renaming) > for further inspection. Sometimes, you can also run "strings" > for a given file - maybe that can be used to identify typical > suspicious string patters for a "strings + grep" combination > so less manual identification has to be done. > > yes , my main problem is the huge number of files but anyway I'm gonna first check files greater than 500 Mb it could be a good start
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E23F51E.7040907>