neulab/tldr huggingface dataset:
An update command placed in the procedure ::ftp::DisplayMsg may run into persistent errors or infinite loops. The solution to this problem is to use update idletasks instead of update.
BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems.  Please report such in the category ftp of the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist].  Please also report any ideas for enhancements you may have for either package and/or documentation.
When proposing code changes, please provide unified diffs, i.e the output of diff -u.
Note further that attachments are strongly preferred over inlined patches. Attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar.
ftpd, mime, pop3, smtp
ftp, internet, net, rfc 959
NCDU(1)                            ncdu manual                           NCDU(1)
ncdu - NCurses Disk Usage
ncdu [options] dir
ncdu (NCurses Disk Usage) is a curses-based version of the well-known 'du', and provides a fast way to see what directories are using your disk space.
Mode Selection -h, --help Print a short help message and quit.
-v, -V, --version Print ncdu version and quit.
-f FILE Load the given file, which has earlier been created with the "-o" option. If FILE is equivalent to "-", the file is read from standard input.
For the sake of preventing a screw-up, the current version of ncdu will assume that the directory information in the imported file does not represent the filesystem on which the file is being imported. That is, the refresh, file deletion and shell spawning options in the browser will be disabled.
dir Scan the given directory.
-o FILE Export all necessary information to FILE instead of opening the browser interface. If FILE is "-", the data is written to standard output.  See the examples section below for some handy use cases.
Be warned that the exported data may grow quite large when exporting a directory with many files. 10.000 files will get you an export in the order of 600 to 700 KiB uncompressed, or a little over 100 KiB when compressed with gzip. This scales linearly, so be prepared to handle a few tens of megabytes when dealing with millions of files.
-e  Enable extended information mode. This will, in addition to the usual file information, also read the ownership, permissions and last modification time for each file. This will result in higher memory usage (by roughly ~30%) and in a larger output file when exporting.
When using the file export/import function, this flag will need to be added both when exporting (to make sure the information is added to the export), and when importing (to read this extra information in memory). This flag has no effect when importing a file that has been exported without the extended information.
This enables viewing and sorting by the latest child mtime, or modified time, using 'm' and 'M', respectively.
Interface options -0  Don't give any feedback while scanning a directory or importing a file, other than when a fatal error occurs. Ncurses will not be initialized until the scan is complete. When exporting the data with "-o", ncurses will not be initialized at all. This option is the default when exporting to standard output.
-1  Similar to "-0", but does give feedback on the scanning progress with a single line of output. This option is the default when exporting to a file.
In some cases, the ncurses browser interface which you'll see after the scan/import is complete may look garbled when using this option. If you're not exporting to a file, "-2" is probably a better choice.
-2  Provide a full-screen ncurses interface while scanning a directory or importing a file. This is the only interface that provides feedback on any non-fatal errors while scanning.
-q  Quiet mode. While scanning or importing the directory, ncdu will update the screen 10 times a second by default, this will be decreased to once every 2 seconds in quiet mode. Use this feature to save bandwidth over remote connections. This option has no effect when "-0" is used.
-r  Read-only mode. This will disable the built-in file deletion feature. This option has no effect when "-o" is used, because there will not be a browser interface in that case. It has no effect when "-f" is used, either, because the deletion feature is disabled in that case anyway.
WARNING: This option will only prevent deletion through the file browser. It is still possible to spawn a shell from ncdu and delete or modify files from there. To disable that feature as well, pass the "-r" option twice (see "-rr").
-rr In addition to "-r", this will also disable the shell spawning feature of the file browser.
--si List sizes using base 10 prefixes, that is, powers of 1000 (KB, MB, etc), as defined in the International System of Units (SI), instead of the usual base 2 prefixes, that is, powers of 1024 (KiB, MiB, etc).
--confirm-quit Requires a confirmation before quitting ncdu. Very helpful when you accidentally press 'q' during or after a very long scan.
--color SCHEME Select a color scheme. Currently only two schemes are recognized: off to disable colors (the default) and dark for a color scheme intended for dark backgrounds.
Scan Options These options affect the scanning progress, and have no effect when importing directory information from a file.
-x  Do not cross filesystem boundaries, i.e. only count files and directories on the same filesystem as the directory being scanned.
--exclude PATTERN Exclude files that match PATTERN. The files will still be displayed by default, but are not counted towards the disk usage statistics. This argument can be added multiple times to add more patterns.
-X FILE, --exclude-from FILE Exclude files that match any pattern in FILE. Patterns should be separated by a newline.
--exclude-caches Exclude directories containing CACHEDIR.TAG.  The directories will still be displayed, but not their content, and they are not counted towards the disk usage statistics.  See http://www.brynosaurus.com/cachedir/
-L, --follow-symlinks Follow symlinks and count the size of the file they point to. As of ncdu 1.14, this option will not follow symlinks to directories and will count each symlinked file as a unique file (i.e. unlike how hard links are handled). This is subject to change in later versions.
--exclude-firmlinks (MacOS only) Exclude firmlinks.
--exclude-kernfs (Linux only) Exclude Linux pseudo filesystems, e.g. /proc (procfs), /sys (sysfs).
The complete list of currently known pseudo filesystems is: binfmt, bpf, cgroup, cgroup2, debug, devpts, proc, pstore, security, selinux, sys, trace.
?   Show help + keys + about screen
up, down j, k Cycle through the items
right, enter, l Open selected directory
left, <, h Go to parent directory
n   Order by filename (press again for descending order)
s   Order by filesize (press again for descending order)
C   Order by number of items (press again for descending order)
a   Toggle between showing disk usage and showing apparent size.
M   Order by latest child mtime, or modified time. (press again for descending order) Requires the -e flag.
d   Delete the selected file or directory. An error message will be shown when the contents of the directory do not match or do not exist anymore on the filesystem.
t   Toggle dirs before files when sorting.
g   Toggle between showing percentage, graph, both, or none. Percentage is relative to the size of the current directory, graph is relative to the largest item in the current directory.
c   Toggle display of child item counts.
m   Toggle display of latest child mtime, or modified time. Requires the -e flag.
e   Show/hide 'hidden' or 'excluded' files and directories. Please note that even though you can't see the hidden files and directories, they are still there and they are still included in the directory sizes. If you suspect that the totals shown at the bottom of the screen are not correct, make sure you haven't enabled this option.
i   Show information about the current selected item.
r   Refresh/recalculate the current directory.
b   Spawn shell in current directory.
Ncdu will determine your preferred shell from the "NCDU_SHELL" or "SHELL" variable (in that order), or will call "/bin/sh" if neither are set.  This allows you to also configure another command to be run when he 'b' key is pressed. For example, to spawn the vifm(1) file manager instead of a shell, run ncdu as follows:
export NCDU_SHELL=vifm ncdu
Ncdu will set the "NCDU_LEVEL" environment variable or increment it before spawning the shell. This variable allows you to detect when your shell is running from within ncdu, which can be useful to avoid nesting multiple instances of ncdu. Ncdu itself does not (currently) warn when attempting to run nested instances.
q   Quit
Entries in the browser interface may be prefixed by a one-character flag. These flags have the following meaning:
!   An error occurred while reading this directory.
.   An error occurred while reading a subdirectory, so the indicated size may not be correct.
<   File or directory is excluded from the statistics by using exclude patterns.
>   Directory is on another filesystem.
^   Directory is excluded from the statistics due to being a Linux pseudo filesystem.
@   This is neither a file nor a folder (symlink, socket, ...).
H   Same file was already counted (hard link).
e   Empty directory.
To scan and browse the directory you're currently in, all you need is a simple:
If you want to scan a full filesystem, your root filesystem, for example, then you'll want to use "-x":
ncdu -x /
Since scanning a large directory may take a while, you can scan a directory and export the results for later viewing:
ncdu -1xo- / | gzip >export.gz # ...some time later: zcat export.gz | ncdu -f-
To export from a cron job, make sure to replace "-1" with "-0" to suppress any unnecessary output.
You can also export a directory and browse it once scanning is done:
ncdu -o- | tee export.file | ./ncdu -f-
The same is possible with gzip compression, but is a bit kludgey:
ncdu -o- | gzip | tee export.gz | gunzip | ./ncdu -f-
To scan a system remotely, but browse through the files locally:
ssh -C user@system ncdu -o- / | ./ncdu -f-
The "-C" option to ssh enables compression, which will be very useful over slow links. Remote scanning and local viewing has two major advantages when compared to running ncdu directly on the remote system: You can browse through the scanned directory on the local system without any network latency, and ncdu does not keep the entire directory structure in memory when exporting, so you won't consume much memory on the remote system.
Every disk usage analysis utility has its own way of (not) counting hard links.  There does not seem to be any universally agreed method of handling hard links, and it is even inconsistent among different versions of ncdu. This section explains what each version of ncdu does.
ncdu 1.5 and below does not support any hard link detection at all: each link is considered a separate inode and its size is counted for every link. This means that the displayed directory sizes are incorrect when analyzing directories which contain hard links.
ncdu 1.6 has basic hard link detection: When a link to a previously encountered inode is detected, the link is considered to have a file size of zero bytes.  Its size is not counted again, and the link is indicated in the browser interface with a 'H' mark. The displayed directory sizes are only correct when all links to an inode reside within that directory. When this is not the case, the sizes may or may not be correct, depending on which links were considered as "duplicate" and which as "original". The indicated size of the topmost directory (that is, the one specified on the command line upon starting ncdu) is always correct.
ncdu 1.7 and later has improved hard link detection. Each file that has more than two links has the "H" mark visible in the browser interface. Each hard link is counted exactly once for every directory it appears in. The indicated size of each directory is therefore, correctly, the sum of the sizes of all unique inodes that can be found in that directory. Note, however, that this may not always be same as the space that will be reclaimed after deleting the directory, as some inodes may still be accessible from hard links outside it.
Directory hard links are not supported. They will not be detected as being hard links, and will thus be scanned and counted multiple times.
Some minor glitches may appear when displaying filenames that contain multibyte or multicolumn characters.
All sizes are internally represented as a signed 64bit integer. If you have a directory larger than 8 EiB minus one byte, ncdu will clip its size to 8 EiB minus one byte. When deleting items in a directory with a clipped size, the resulting sizes will be incorrect.
Item counts are stored in a signed 32-bit integer without overflow detection.  If you have a directory with more than 2 billion files, quite literally anything can happen.
On macOS 10.15 and later, running ncdu on the root directory without `--exclude-firmlinks` may cause directories to be scanned and counted multiple times. Firmlink cycles are currently (1.16) not detected, so it may also cause ncdu to get stuck in an infinite loop and eventually run out of memory.
Please report any other bugs you may find at the bug tracker, which can be found on the web site at https://dev.yorhel.nl/ncdu
Written by Yoran Heling <projects@yorhel.nl>.
du(1)
RPCINFO(7)            BSD Miscellaneous Information Manual            RPCINFO(7)
rpcinfo â€” report RPC information
rpcinfo [-m | -s] [host] rpcinfo -p [host] rpcinfo -T transport host prognum [versnum] rpcinfo -l [-T transport] host prognum versnum rpcinfo [-n portnum] -u host prognum [versnum] rpcinfo [-n portnum] [-t] host prognum [versnum] rpcinfo -a serv_address -T transport prognum [versnum] rpcinfo -b [-T transport] prognum versnum rpcinfo -d [-T transport] prognum versnum
rpcinfo makes an RPC call to an RPC server and reports what it finds.
In the first synopsis, rpcinfo lists all the registered RPC services with rpcbind on host.  If host is not specified, the local host is the default. If -s is used, the information is displayed in a concise format.
In the second synopsis, rpcinfo lists all the RPC services registered with rpcbind, version 2.  Also note that the format of the information is different in the first and the second synopsis.  This is because the second synopsis is an older protocol used to collect the information displayed (version 2 of the rpcbind protocol).
The third synopsis makes an RPC call to procedure 0 of prognum and versnum on the specified host and reports whether a response was received. transport is the transport which has to be used for contacting the given service.  The remote address of the service is obtained by making a call to the remote rpcbind.
The prognum argument is a number that represents an RPC program number.  If a versnum is specified, rpcinfo attempts to call that version of the specified prognum.  Otherwise, rpcinfo attempts to find all the registered version numbers for the specified prognum by calling version 0, which is presumed not to exist; if it does exist, rpcinfo attempts to obtain this information by calling an extremely high version number instead, and attempts to call each registered version.  Note: the version number is required for -b and -d options.
-T transport Specify the transport on which the service is required.  If this option is not specified, rpcinfo uses the transport specified in the NETPATH environment variable, or if that is unset or null, the transport in the netconfig(5) database is used.  This is a generic option, and can be used in conjunction with other options as shown in the SYNOPSIS.
-a serv_address Use serv_address as the (universal) address for the service on transport to ping procedure 0 of the specified prognum and report whether a response was received.  The -T option is required with the -a option.
If versnum is not specified, rpcinfo tries to ping all available version numbers for that program number.  This option avoids calls to remote rpcbind to find the address of the service.  The serv_address is specified in universal address format of the given transport.
-b      Make an RPC broadcast to procedure 0 of the specified prognum and versnum and report all hosts that respond.  If transport is specified, it broadcasts its request only on the specified transport.  If broadcasting is not supported by any transport, an error message is printed.  Use of broadcasting should be limited because of the potential for adverse effect on other systems.
-d      Delete registration for the RPC service of the specified prognum and versnum.  If transport is specified, unregister the service on only that transport, otherwise unregister the service on all the transports on which it was registered.  Only the owner of a service can delete a registration, except the super-user who can delete any service.
-l      Display a list of entries with a given prognum and versnum on the specified host.  Entries are returned for all transports in the same protocol family as that used to contact the remote rpcbind.
-m      Display a table of statistics of rpcbind operations on the given host.  The table shows statistics for each version of rpcbind (versions 2, 3 and 4), giving the number of times each procedure was requested and successfully serviced, the number and type of remote call requests that were made, and information about RPC address lookups that were handled. This is useful for monitoring RPC activities on host.
-n portnum Use portnum as the port number for the -t and -u options instead of the port number given by rpcbind.  Use of this option avoids a call to the remote rpcbind to find out the address of the service. This option is made obsolete by the -a option.
-p      Probe rpcbind on host using version 2 of the rpcbind protocol, and display a list of all registered RPC programs.  If host is not specified, it defaults to the local host.  Note: Version 2 of the rpcbind protocol was previously known as the portmapper protocol.
-s      Display a concise list of all registered RPC programs on host.  If host is not specified, it defaults to the local host.
-t      Make an RPC call to procedure 0 of prognum on the specified host using TCP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis.
-u      Make an RPC call to procedure 0 of prognum on the specified host using UDP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis.
To show all of the RPC services registered on the local machine use:
example% rpcinfo
To show all of the RPC services registered with rpcbind on the machine named klaxon use:
example% rpcinfo klaxon
The information displayed by the above commands can be quite lengthy.  Use the -s option to display a more concise list:
example$ rpcinfo -s klaxon
program   version   netid                     service    owner 100000    2,3,4     local,tcp,udp,tcp6,udp6   rpcbind    super-user 100008    1         udp,tcp,udp6,tcp6         walld      super-user 100002    2,1       udp,udp6                  rusersd    super-user 100001    2,3,4     udp,udp6                  rstatd     super-user 100012    1         udp,tcp                   sprayd     super-user 100007    3         udp,tcp                   ypbind     super-user
To show whether the RPC service with program number prognum and version versnum is registered on the machine named klaxon for the transport TCP use:
example% rpcinfo -T tcp klaxon prognum versnum
To show all RPC services registered with version 2 of the rpcbind protocol on the local machine use:
example% rpcinfo -p
To delete the registration for version 1 of the walld (program number 100008 ) service for all transports use:
example# rpcinfo -d 100008 1
example# rpcinfo -d walld 1
rpc(3), netconfig(5), rpc(5), rpcbind(8)
Hashcat(1)                   General Commands Manual                  Hashcat(1)
hashcat - Advanced CPU-based password recovery utility
hashcat [options] hashfile [mask|wordfiles|directories]
Hashcat is the world’s fastest CPU-based password recovery tool.
While it's not as fast as its GPU counterpart oclHashcat, large lists can be easily split in half with a good dictionary and a bit of knowledge of the command switches.
Hashcat is the self-proclaimed world’s fastest CPU-based password recovery tool, Examples of hashcat supported hashing algorithms are Microsoft LM Hashes, MD4, MD5, SHA-family, Unix Crypt formats, MySQL, Cisco PIX.
-m, --hash-type=NUM Hash-type, see references below
-a, --attack-mode=NUM Attack-mode, see references below
--quiet Suppress output
--force Ignore warnings
--stdin-timeout-abort Abort if there is no input from stdin for X seconds
--machine-readable Display the status view in a machine-readable format
--keep-guessing Keep guessing the hash after it has been cracked
--self-test-disable Disable self-test functionality on startup
--loopback Add new plains to induct directory
-b, --benchmark Run benchmark
--hex-salt Assume salt is given in hex
--hex-charset Assume charset is given in hex
--hex-wordlist Assume words in wordlist are given in hex
--runtime=NUM Abort session after NUM seconds of runtime
--status Enable automatic update of the status-screen
--status-timer=NUM Seconds between status-screen update
-o, --outfile=FILE Define outfile for recovered hash
--outfile-format=NUM Define outfile-format for recovered hash, see references below
--outfile-autohex-disable Disable the use of $HEX[] in output plains
-p, --separator=CHAR Define separator char for hashlists/outfile
--show Show cracked passwords only (see --username)
--left Show uncracked passwords only (see --username)
--username Enable ignoring of usernames in hashfile (Recommended: also use --show)
--remove Enable remove of hash once it is cracked
--stdout Stdout mode
--potfile-disable Do not write potfile
--debug-mode=NUM Defines the debug mode (hybrid only by using rules), see references below
--debug-file=FILE Output file for debugging rules (see --debug-mode)
-c, --segment-size=NUM Size in MB to cache from the wordfile
-r, --rules-file=FILE Rules-file use: -r 1.rule
-g, --generate-rules=NUM Generate NUM random rules
--generate-rules-func-min=NUM Force NUM functions per random rule min
--generate-rules-func-max=NUM Force NUM functions per random rule max
--generate-rules-seed=NUM Force RNG seed to NUM
-1, --custom-charset1=CS User-defined charsets example --custom-charset1=?dabcdef : sets charset ?1 to 0123456789abcdef -1 mycharset.hcchr : sets charset ?1 to chars contained in file
-2, --custom-charset2=CS User-defined charsets example --custom-charset2=?dabcdef : sets charset ?2 to 0123456789abcdef -2 mycharset.hcchr : sets charset ?2 to chars con$
-3, --custom-charset3=CS User-defined charsets example --custom-charset3=?dabcdef : sets charset ?3 to 0123456789abcdef -3 mycharset.hcchr : sets charset ?3 to chars con$
-4, --custom-charset4=CS User-defined charsets example --custom-charset4=?dabcdef : sets charset ?4 to 0123456789abcdef -4 mycharset.hcchr : sets charset ?4 to chars con$
--increment Enable increment mode
--increment-min=NUM Start incrementing at NUM
--increment-max=NUM Stop incrementing at NUM
--markov-hcstat2 Specify hcstat2 file to use
--markov-disable Disables markov-chains, emulates classic brute-force
--markov-classic Enables classic markov-chains, no per-position
-t, --markov-threshold Threshold X when to stop accepting new markov-chains
--session=STR Define specific session name
--restore Restore session from --session
--restore-disable Do not write restore file
--restore-file-path=FILE Specific path to restore file
--outfile-check-timer=NUM Sets seconds between outfile checks to X
--wordlist-autohex-disable Disable the conversion of $HEX[] from the wordlist
--remove-timer=NUM Update input hash file each X seconds
--potfile-path=FILE Specific path to potfile
--encoding-from=CODE Force internal wordlist encoding from X
--encoding-to=CODE Force internal wordlist encoding to X
--induction-dir=DIR Specify the induction directory to use for loopback
--outfile-check-dir=DIR Specify the outfile directory to monitor for plains
--logfile-disable Disable the logfile
--hccapx-message-pair=NUM Load only message pairs from hccapx matching X
--nonce-error-corrections=NUM The BF size range to replace AP's nonce last bytes
--keyboard-layout-mapping=FILE Keyboard layout mapping table for special hash-modes
--truecrypt-keyfiles=FILE Keyfiles to use, separated with commas
--veracrypt-keyfiles=FILE Keyfiles to use, separated with commas
--veracrypt-pim=NUM VeraCrypt personal iterations multiplier
--benchmark-all Run benchmark of all hash-modes
--speed-only Return expected speed of the attack, then quit
--progress-only Return ideal progress step size and time to process
--bitmap-min=NUM Sets minimum bits allowed for bitmaps to X
--bitmap-max=NUM Sets maximum bits allowed for bitmaps to X
--cpu-affinity=STR Locks to CPU devices, separated with commas
--example-hashes Show an example hash for each hash-mode
-I, --opencl-info Show info about detected OpenCL platforms/devices
--opencl-platforms=STR OpenCL platforms to use, separated with commas
-d, --opencl-devices=STR OpenCL devices to use, separated with commas
-D, --opencl-device-types=STR OpenCL device-types to use, separated with commas
--opencl-vector-width=NUM Manually override OpenCL vector-width to X
-O, --optimized-kernel-enable Enable optimized kernels (limits password length)
-w, --workload-profile=NUM Enable a specific workload profile, see pool below
-n, --kernel-accel=NUM Manual workload tuning, set outerloop step size to X
-u, --kernel-loops=NUM Manual workload tuning, set innerloop step size to X
-T, --kernel-threads=NUM Manual workload tuning, set thread count to X
--spin-damp=NUM Use CPU for device synchronization, in percent
--hwmon-disable Disable temperature and fanspeed reads and triggers
--hwmon-temp-abort=NUM Abort if temperature reaches X degrees Celsius
--scrypt-tmto=NUM Manually override TMTO value for scrypt to X
-s, --skip=NUM Skip X words from the start
-l, --limit=NUM Limit X words from the start + skipped words
--keyspace Show keyspace base:mod values and quit
-j, --rule-left RULE Single rule applied to each word from left wordlist
-k, --rule-right RULE Single rule applied to each word from right wordlist
-S, --slow-candidates Enable slower (but advanced) candidate generators
--brain-server Enable brain server
-z, --brain-client Enable brain client, activates -S
--brain-client-features=NUM Define brain client features, see below
--brain-host=STR Brain server host (IP or domain)
--brain-port=PORT Brain server port
--brain-password=STR Brain server authentication password
--brain-session=HEX Overrides automatically calculated brain session
--brain-session-whitelist=HEX Allow given sessions only, separated with commas
Permutation attack-mode options
Outfile formats 1 = hash[:salt] 2 = plain 3 = hash[:salt]:plain 4 = hex_plain 5 = hash[:salt]:hex_plain 6 = plain:hex_plain 7 = hash[:salt]:plain:hex_plain 8 = crackpos 9 = hash[:salt]:crack_pos 10 = plain:crack_pos 11 = hash[:salt]:plain:crack_pos 12 = hex_plain:crack_pos 13 = hash[:salt]:hex_plain:crack_pos 14 = plain:hex_plain:crack_pos 15 = hash[:salt]:plain:hex_plain:crack_pos
Debug mode output formats (for hybrid mode only, by using rules) 1 = save finding rule 2 = save original word 3 = save original word and finding rule 4 = save original word, finding rule and modified plain
Built-in charsets ?l = abcdefghijklmnopqrstuvwxyz ?u = ABCDEFGHIJKLMNOPQRSTUVWXYZ ?d = 0123456789 ?h = 0123456789abcdef ?H = 0123456789ABCDEF ?s =  !"#$%&'()*+,-./:;<=>?@[]^_`{|}~ ?a = ?l?u?d?s ?b = 0x00 - 0xff
Attack mode 0 = Straight 1 = Combination 3 = Brute-force 6 = Hybrid Wordlist + Mask 7 = Hybrid Mask + Wordlist
Hash types 0 = MD5 10 = md5($pass.$salt) 20 = md5($salt.$pass) 30 = md5(unicode($pass).$salt) 40 = md5($salt.unicode($pass)) 50 = HMAC-MD5 (key = $pass) 60 = HMAC-MD5 (key = $salt) 100 = SHA1 110 = sha1($pass.$salt) 120 = sha1($salt.$pass) 130 = sha1(unicode($pass).$salt) 140 = sha1($salt.unicode($pass)) 150 = HMAC-SHA1 (key = $pass) 160 = HMAC-SHA1 (key = $salt) 200 = MySQL323 300 = MySQL4.1/MySQL5 400 = phpass, MD5(Wordpress), MD5(phpBB3), MD5(Joomla) 500 = md5crypt, MD5(Unix), FreeBSD MD5, Cisco-IOS MD5 900 = MD4 1000 = NTLM 1100 = Domain Cached Credentials (DCC), MS Cache 1400 = SHA256 1410 = sha256($pass.$salt) 1420 = sha256($salt.$pass) 1430 = sha256(unicode($pass).$salt) 1431 = base64(sha256(unicode($pass))) 1440 = sha256($salt.unicode($pass)) 1450 = HMAC-SHA256 (key = $pass) 1460 = HMAC-SHA256 (key = $salt) 1600 = md5apr1, MD5(APR), Apache MD5 1700 = SHA512 1710 = sha512($pass.$salt) 1720 = sha512($salt.$pass) 1730 = sha512(unicode($pass).$salt) 1740 = sha512($salt.unicode($pass)) 1750 = HMAC-SHA512 (key = $pass) 1760 = HMAC-SHA512 (key = $salt) 1800 = SHA-512(Unix) 2400 = Cisco-PIX MD5 2410 = Cisco-ASA MD5 2500 = WPA/WPA2 2600 = Double MD5 3200 = bcrypt, Blowfish(OpenBSD) 3300 = MD5(Sun) 3500 = md5(md5(md5($pass))) 3610 = md5(md5($salt).$pass) 3710 = md5($salt.md5($pass)) 3720 = md5($pass.md5($salt)) 3800 = md5($salt.$pass.$salt) 3910 = md5(md5($pass).md5($salt)) 4010 = md5($salt.md5($salt.$pass)) 4110 = md5($salt.md5($pass.$salt)) 4210 = md5($username.0.$pass) 4300 = md5(strtoupper(md5($pass))) 4400 = md5(sha1($pass)) 4500 = Double SHA1 4600 = sha1(sha1(sha1($pass))) 4700 = sha1(md5($pass)) 4800 = MD5(Chap), iSCSI CHAP authentication 4900 = sha1($salt.$pass.$salt) 5000 = SHA-3(Keccak) 5100 = Half MD5 5200 = Password Safe SHA-256 5300 = IKE-PSK MD5 5400 = IKE-PSK SHA1 5500 = NetNTLMv1-VANILLA / NetNTLMv1-ESS 5600 = NetNTLMv2 5700 = Cisco-IOS SHA256 5800 = Android PIN 6300 = AIX {smd5} 6400 = AIX {ssha256} 6500 = AIX {ssha512} 6700 = AIX {ssha1} 6900 = GOST, GOST R 34.11-94 7000 = Fortigate (FortiOS) 7100 = OS X v10.8+ 7200 = GRUB 2 7300 = IPMI2 RAKP HMAC-SHA1 7400 = sha256crypt, SHA256(Unix) 7900 = Drupal7 8400 = WBB3, Woltlab Burning Board 3 8900 = scrypt 9200 = Cisco $8$ 9300 = Cisco $9$ 9800 = Radmin2 10000 = Django (PBKDF2-SHA256) 10200 = Cram MD5 10300 = SAP CODVN H (PWDSALTEDHASH) iSSHA-1 11000 = PrestaShop 11100 = PostgreSQL Challenge-Response Authentication (MD5) 11200 = MySQL Challenge-Response Authentication (SHA1) 11400 = SIP digest authentication (MD5) 99999 = Plaintext
Specific hash type 11 = Joomla < 2.5.18 12 = PostgreSQL 21 = osCommerce, xt:Commerce 23 = Skype 101 = nsldap, SHA-1(Base64), Netscape LDAP SHA 111 = nsldaps, SSHA-1(Base64), Netscape LDAP SSHA 112 = Oracle S: Type (Oracle 11+) 121 = SMF > v1.1 122 = OS X v10.4, v10.5, v10.6 123 = EPi 124 = Django (SHA-1) 131 = MSSQL(2000) 132 = MSSQL(2005) 133 = PeopleSoft 141 = EPiServer 6.x < v4 1421 = hMailServer 1441 = EPiServer 6.x > v4 1711 = SSHA-512(Base64), LDAP {SSHA512} 1722 = OS X v10.7 1731 = MSSQL(2012 & 2014) 2611 = vBulletin < v3.8.5 2612 = PHPS 2711 = vBulletin > v3.8.5 2811 = IPB2+, MyBB1.2+ 3711 = Mediawiki B type 3721 = WebEdition CMS 7600 = Redmine Project Management Web App
hashcat was written by Jens Steube <jens.steube@gmail.com>
MKISOFS(8)                   System Manager's Manual                  MKISOFS(8)
mkisofs - create an hybrid ISO-9660/JOLIET/HFS/UDF filesystem-image with optional Rock Ridge attributes.
mkisofs [ options ] [ -o filename ] pathspec [pathspec ...] mkisofs [ options ] [ -o filename ] -find [find expression]
mkisofs is effectively a pre-mastering program to generate an ISO-9660/JOLIET/HFS/UDF hybrid filesystem.
ISO-9660/JOLIET/UDF filesystems are limited to a maximum size of 8 TB. The maximum size of a single file is 8 TB (single files in UDF are currently limited to aprox. 200 GB).  If you like to have files larger than 2 GB, you need to specify -iso-level 3 or above.  If a HFS hybrid is created, the maximum file size for files in the HFS hybrid is 2 GB in any case.
Hybrid filesystem support mkisofs is capable of generating the System Use Sharing Protocol records (SUSP) specified by the Rock Ridge Interchange Protocol.  This is used to further describe the files in the ISO-9660 filesystem to a UNIX host, and provides information such as longer filenames, uid/gid, posix permissions, symbolic links, hard links, block and character devices.
If Joliet, HFS or UDF hybrid command line options are specified, mkisofs will create additional separate filesystem meta data for Joliet, HFS or UDF.  The file content in this case refers to the same data blocks on the media.  It will generate a pure ISO-9660 filesystem unless the Joliet, HFS or UDF hybrid command line options are given.
mkisofs can generate a true (or shared) HFS hybrid filesystem. The same files are seen as HFS files when accessed from a Macintosh and as ISO-9660 files when accessed from other machines. HFS stands for Hierarchical File System and is the native file system used on Macintosh computers up to Mac OS 9.
As an alternative, mkisofs can generate the Apple Extensions to ISO-9660 or UDF for each file. These extensions provide each file with CREATOR, TYPE and certain Finder Flags when accessed from a Macintosh. See the HFS MACINTOSH FILE FORMATS section below.
Functional description mkisofs takes a snapshot of a given directory tree, and generates a binary image which will correspond to an ISO-9660 or Joliet/HFS/UDF filesystem when written to a block device.
Each file written to the ISO-9660 filesystem must have a filename in the 8.3 format (8 characters, period, 3 characters, all upper case), even if Rock Ridge attributes are in use.  This filename is used on systems that are not able to make use of the Rock Ridge extensions (such as MS-DOS), and each filename in each directory must be different from the other filenames in the same directory.  mkisofs generally tries to form correct names by forcing the UNIX filename to upper case and truncating as required, but often times this yields unsatisfactory results when there are cases where the truncated names are not all unique.  mkisofs assigns weightings to each filename, and if two names that are otherwise the same are found the name with the lower priority is renamed to have a 3 digit number as an extension (where the number is guaranteed to be unique).  An example of this would be the files foo.bar and foo.bar.~1~ - the file foo.bar.~1~ would be written as FOO000.BAR;1 and the file foo.bar would be written as FOO.BAR;1
When used with various HFS or UDF options, mkisofs will attempt to recognise files stored in a number of Apple/Unix file formats and will copy the data and resource forks as well as any relevant finder information. See the HFS MACINTOSH FILE FORMATS section below for more about formats mkisofs supports.
Note that mkisofs is not designed to communicate with writers for optical media directly.  Most writers have proprietary command sets which vary from one manufacturer to another, and you need a specialized tool like cdrecord to actually burn the disk.
The cdrecord utility is a utility capable of burning an actual disc.  The latest version of cdrecord is available from https://sourceforge.net/projects/cdrtools/files/ or https://sourceforge.net/projects/cdrtools/files/alpha/
Also you should know that most CD writers are very particular about timing.  Once you start to burn a disc, you cannot let their buffer empty before you are done, or you will end up with a corrupt disc.  Thus it is critical that you be able to maintain an uninterrupted data stream to the writer for the entire time that the disc is being written.
Dealing with path names pathspec is the path of the directory tree to be copied into the ISO-9660 filesystem.  Multiple paths can be specified, and mkisofs will merge the files found in all of the specified path components to form the cdrom image.
If the option -graft-points has been specified, it is possible to graft the paths at points other than the root directory, and it is possible to graft files or directories onto the cdrom image with names different than what they have in the source filesystem.  This is easiest to illustrate with a couple of examples.   Let's start by assuming that a local file ../old.lis exists, and you wish to include it in the cdrom image.
foo/bar/=../old.lis
will include the file old.lis in the cdrom image at /foo/bar/old.lis, while
foo/bar/xxx=../old.lis
will include the file old.lis in the cdrom image at /foo/bar/xxx.  The same sort of syntax can be used with directories as well.  mkisofs will create any directories required such that the graft points exist on the cdrom image - the directories do not need to appear in one of the paths. By default, any directories that are created on the fly like this will have permissions 0555 and appear to be owned by the person running mkisofs.  If you wish other permissions or owners of the intermediate directories, see -uid, -gid, -dir-mode, -file-mode and -new-dir-mode.
mkisofs will also run on Win9x/NTx machines when compiled with Cygnus' cygwin (available from http://sourceware.cygnus.com/cygwin/). Therefore most references in this man page to Unix also apply to Win32 or Win64.
-abstract FILE Specifies the abstract file name in the primary volume descriptor. There is space on the disc for 37 characters of information.  The related Joliet entry is limited to 18 characters.  This parameter can also be set in the file .mkisofsrc with ABST=filename.  If specified in both places, the command line version is used.
It is up to the user of mkisofs to include a file with the apropriate name in the created filesystem tree.
-A application_id
-appid application_id Specifies a text string that will be written into the volume header.  This should describe the application that will be on the disc.  There is space on the disc for 128 characters of information.  The related Joliet entry is limited to 64 characters.  This parameter can also be set in the file .mkisofsrc with APPI=id.  If specified in both places, the command line version is used.
-allow-leading-dots
-ldots Allow ISO-9660 filenames to begin with a period.  Usually, a leading dot is replaced with an underscore in order to maintain MS-DOS compatibility. This violates the ISO-9660 standard, but it happens to work on many systems.  Use with caution.
-allow-lowercase This options allows lower case characters to appear in ISO-9660 filenames. This violates the ISO-9660 standard, but it happens to work on some systems.  Use with caution.
-no-allow-lowercase This resets the effect of -allow-lowercase and even works when -U, -untranslated-filenames or -iso-level 4 have been used to allow lowercase filenames.
-allow-multidot This options allows more than one dot to appear in ISO-9660 filenames.  A leading dot is not affected by this option, it may be allowed separately using the -allow-leading-dots option. This violates the ISO-9660 standard, but it happens to work on many systems.  Use with caution.
-biblio FILE Specifies the bibliographic file name in the primary volume descriptor.  There is space on the disc for 37 characters of information.  The related Joliet entry is limited to 18 characters.  This parameter can also be set in the file .mkisofsrc with BIBLO=filename.  If specified in both places, the command line version is used.
-cache-inodes Cache inode and device numbers to find hard links to files.  If mkisofs finds a hard link (a file with multiple names), then the file will only appear once on the CD. This helps to save space on the CD.  The option -cache-inodes is default on UNIX like operating systems.  Be careful when using this option on a filesystem without unique inode numbers as it may result in files containing the wrong content on CD.
See the option -duplicates-once for a method that works on filesystems without unique inode numbers.
If inodes are not cached, mkisofs will revert to the old Rrip Version-1.10 (see -rrip110) and mkisofs will not be able to create correct inode numbers for zero sized files.
-no-cache-inodes Do not cache inode and device numbers.  This option is needed whenever a filesystem does not have unique inode numbers. It is the default on old Cygwin versions.  As the Microsoft operating system that runs below Cygwin uses 64 bit inode numbers for NTFS, it does not have unique inode numbers in the 32 bit range.  Old Cygwin versions create fake 32-bit inode numbers from a hash algorithm and thus create non-unique numbers.  If mkisofs would cache inodes on old Cygwin versions, it would believe that some files are identical although they are not. The result in this case are files that contain the wrong content if a significant amount of different files (> ~5000) is in inside the tree that is to be archived.  This does not happen when the -no-cache-inodes is used, but the disadvantage is that mkisofs cannot detect hardlinks anymore and the resulting CD image may be larger than expected.
-duplicates-once Tells mkisofs to use a message digest checksum to identify identical files as apparently hard linked files.  This allows mkisofs to archive inode numbers and hard links even when it is run on non-POSIX platforms like DOS.
-b eltorito_boot_image
-eltorito-boot eltorito_boot_image Specifies the path and filename of the boot image to be used when making an "El Torito" bootable CD. The pathname must be relative to the source path and inside the source tree specified to mkisofs.  This option is required to make an "El Torito" bootable CD.  The boot image must be exactly the size of either a 1200, 1440, or a 2880 kB floppy, and mkisofs will use this size when creating the output ISO-9660 filesystem. It is assumed that the first 512 byte sector should be read from the boot image (it is essentially emulating a normal floppy drive).  This will work, for example, if the boot image is a boot floppy.
If the boot image is not an image of a floppy, you need to add one of the options: -hard-disk-boot or -no-emul-boot.  If the system should not boot off the emulated disk, use -no-boot.
More than one boot entry may be specified, see -eltorito-platform and -eltorito-alt-boot on how to specify more boot entries.  The first boot entry is the default boot entry.  Additional boot entries are members for a multi boot configuration.
If the -sort option has not been specified, the boot images are sorted with low priority (+2) to the beginning of the medium.  If you don't like this, you need to specify a sort weight of 0 for the boot images.
-eltorito-alt-boot Start with a new set of "El Torito" boot parameters.  This allows to have more than one El Torito boot entry on a CD.  A maximum of 63 El Torito boot entries may be put on a single CD.
The -eltorito-alt-boot option starts a new boot entry with the same platform id but no new boot section except when it appears past the first boot entry which is the default boot entry.
-eltorito-platform id Set the "El Torito" platform id for a boot record or a section of boot records.  The.  id parameter may be either:
x86    This is the default platform id value and specifies entries for the PC platform.  If no -eltorito-platform option appears before the first -eltorito-boot option, the default boot entry becomes an entry for the x86 PC platform.
PPC    Boot entries for the Power PC platform.
Mac    Boot entries for the Apple Mac platform.
efi    Boot entries for EFI based PCs.
#      A numeric value specifying any platform id.
If the option -eltorito-platform appears before the first -eltorito-boot option, it sets the platform id for the default boot entry.
If the option -eltorito-platform appears after an -eltorito-boot option and sets the platform id to a value different from the previous value, it starts a new set of boot entries.
The second boot entry and any new platform id creates a new section header and reduces the number of boot entries per CD by one.
errctl= name
errctl= error control spec Add the content from file name to the error control definitions or add error control spec to the error control definitions.  More than one error control file and more than one error control spec as well as a mixture of both forms is possible.
The reason for using error control is to make mkisofs quiet about error conditions that are known to be irrelevant on the quality of the created filesystem or to tell mkisofs to abort on certain error conditions instead of trying to continue with the filesystem.
A typical reason to use error control is to suppress warnings about growing log files while doing a backup on a live file system.  Another typical reason to use error control is to tell mkisofs to abort if e.g. a file could not be archived instead of continuing to archive other files from a list.
The error control file contains a set of lines, each starting with a list of error conditions to be ignored followed by white space followed by a file name pattern (see match(1) or patmatch(3) for more information).  The error control spec uses the same syntax as a single line from the error control file.  If the file name pattern needs to start with white space, use a backslash to escape the start of the file name. It is not possible to have new line characters in the file name pattern.  Whenever an error situation is encountered, mkisofs checks the lines in the error control file starting from the top.  If the current error condition is listed on a line in the error control file, then mkisofs checks whether the pattern on the rest of the line matches the current file name. If this is the case, mkisofs uses the current error control specification to control the current error condition.
The list of error conditions to be handled may use one or more (in this case separated by a '|' character) identifiers from the list below:
ABORT       If this meta condition is included in an error condition, mkisofs aborts (exits) as soon as possible after this error condition has been seen instead of making mkisofs quiet about the condition.  This error condition flag may only be used together with at another error condition or a list of error conditions (separated by a '|' character).
WARN        If this meta condition is included in an error condition, mkisofs prints the warning about the error condition but the error condition does not affect the exit code of mkisofs and the error statistics (which is printed to the end) does not include the related errors.  This error condition flag may only be used together with at another error condition or a list of error conditions (separated by a '|' character).  The WARN meta condition has a lower precedence than ABORT.
ALL         This is a shortcut for all error conditions below.
STAT        Suppress warnings that mkisofs could not stat(2) a file.
GETACL      Suppress warnings about files on which mkisofs had problems to retrieve the ACL information.
OPEN        Suppress warnings about files that could not be opened.
READ        Suppress warnings read errors on files.
WRITE       Suppress warnings write errors on files.
READLINK    Suppress warnings readlink(2) errors on symbolic links.
GROW        Suppress warnings about files that did grow while they have been archived.
SHRINK      Suppress warnings about files that did shrink while they have been archived.
MISSLINK    Suppress warnings about files for which mkisofs was unable to archive all hard links.
NAMETOOLONG Suppress warnings about files that could not be archived because the name of the file is too long for the archive format.
FILETOOBIG  Suppress warnings about files that could not be archived because the size of the file is too big for the archive format.
SPECIALFILE Suppress warnings about files that could not be archived because the file type is not supported by the archive format.
GETXATTR    Suppress warnings about files on that mkisofs could not retrieve the extended file attribute information.
SETTIME     Suppress warnings about files on that mkisofs could not set the time information during extraction.
SETMODE     Suppress warnings about files on that mkisofs could not set the access modes during extraction.
SECURITY    Suppress warnings about files that have been skipped on extraction because they have been considered to be a security risk.  This currently applies to all files that have a '/../' sequence inside when -..  has not been specified.
LSECURITY   Suppress warnings about links that have been skipped on extraction because they have been considered to be a security risk.  This currently applies to all link names that start with '/' or have a '/../' sequence inside when -secure-links has been specified.  In this case, mkisofs tries to match the link name against the pattern in the error control file.