assetutil(1) [mojave man page]
assetutil(1) BSD General Commands Manual assetutil(1) NAME
assetutil process asset catalog .car files SYNOPSIS
assetutil [-ViotshMgpT] inputfile DESCRIPTION
assetutil processes a .car file generated from a image catalog removing requested scale factors, device idioms, subtypes, performance and memory classes. When thinning scale, idiom, subtype, performance, memory, and graphicsclassfallbacks can be given multiple times, the result- ing file will contain all of the assets that match all of the parameters given. If scale, idiom, subtype and graphics class are given in one set, the same parameters must all be present in the subsequent set of parmeters. (IE the count must match) A list of flags and their descriptions: -V version information for assetutil -I Produce a JSON description of the asset catalog object with the given name to --output directory if given or to stdout if no output path given. If no name is provided, report on the contents of the entire car file. -i Keep all assets that have idiom that is given on the command line. -s Keep all assets that have scale factor that is given on the command line, present scale factors will not be removed if there is no fallback available. -p Keep all assets that have the display gamut that is given on the command line, present display gamuts will not be removed if there is no fall back avaliable. -M Keep all assets that have memory class that is given on the command line, present memory class will not be removed if there is no fallback available. -g Keep all assets that have graphics class that is given on the command line. The present graphics class will not be removed if there is no fallback available. -h process the hosted idioms list, this is a list of the idioms that must always be preserved in the car file. This list cannot contain universal, and the different idioms should be given in a comma separated list. -i Idiom to keep. Can be one of universal/phone/pad. -t Subtype to keep (integer) -c Main Assets.car file used to supply the names of the assets to the -I (--info) and the dump options -d (--dump) and -D (--dump- stack). -o Output file name, if no output file is given then input file is overwritten. -T compare thinning attributes 'scale=2:idiom=phone:memory=2:graphicsclass=MTL1,2/scale=2:idiom=phone:memory=1:graphicsclass=MTL2,2' will print to stdout if the files was thinned with the above thinning attributes, would the same Asset file result in both cases. Darwin Jan 3, 2018 Darwin
Check Out this Related Man Page
PADS(8) System Manager's Manual PADS(8) NAME
pads - Passive Asset Detection System SYNOPSIS
pads <DhUvV> <-c file > <-d file > <-g group > <-i interface > <-n network(s) > <-p file > <-r file > <-u file > <-w file > <expression> DESCRIPTION
PADS is a libpcap based detection engine used to passively detect network assets. It is designed to complement IDS technology by providing context to IDS alerts. Goals: - Passive: Records and identifies traffic seen on a network without actively "scanning" a system. There will never be a packet sent from the pads application. - Portable: Has the ability to be placed easily on a remote system. Does not require additional external libraries other than those associated with libpcap. - Lightweight: Logging is sent to a simple CSV file. There is no need for a database or other data repository installed on the local machine. All correlation is done outside of the pads program. OPTIONS
-h Display help / usage information. -D Run PADS in the background (daemon mode). -d file Dump banner data into a libpcap formatted file. This feature will dump the matched packet or the first 4 packets of an unmatched connection into a specified file. This can be used to further identify a service and also aid with signature development. Please keep in mind that this feature must be compiled into the application in order to use it. This can be done by adding '--enable-banner-grab' to the 'configure' step. -g group This switch allows you to specify a group that PADS will drop to after the libpcap interface has been initialized. -h Display help -i interface Specify an interface to be used. -n network list Specify a set of networks to be monitored. Only assets that exist within these networks will be recorded. The networks should be specified in the following format: 10.10.10.0/24,192.168.0.0/16 . -p pid file This switch allows you to specify a PID file to be used in conjunction with daemon (-D) mode. -r file Read packets from a libpcap formatted file. -u user This switch allows you to specify a user that PADS will drop to after the libpcap interface has been initialized. -w file Dump data into a file other than assets.csv. expression selects which packets will be processed. Please see tcpdump(1) for details on the libpcap primitives. SEE ALSO
pads.conf(8), pads-report(8), pads-archiver(8), tcpdump(8), pcre(3) COPYRIGHT
Copyright (C) 2004 Matt Shelton <matt@mattshelton.com> BUGS
Please send bug reports to the author. AUTHORS
Matt Shelton <matt@mattshelton.com> 2005/06/17 PADS(8)