git | Kali-Linux-Tools (2023)

git

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package provides the core Git components with minimal dependencies. Additional functionality, e.g. a graphical user interface and a revision tree viewer, tools for collaborating with other VCS or a web interface are provided as separate git* packages.

Installed size: 36,90MB
How to install: sudo apt install git

git

Perl interface to the version control system GitThe stupid content crawler

[email protected]:~# git --helpusage: git [--version] [--help] [-C <path>] [-c <name>=<value>] [--exec path[=<path>]] [--path-html] [--path-man] [--path-info] [-p | --pagination | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name> ] [--super-prefix=<path>] [--config-env=<name>=<envvar>] <command> [<args>] These are general Git commands used in different situations: Start a workspace (see also: Git Help Tutorial) Clone a repository to a new directory. init Create an empty git repository or reinitialize an existing one on the current change (see also: Git daily help). a file, directory, or symbolic link , commit and working tree, etc. grep print lines that match a pattern record show commit records show show different types of objects status show the status of the working tree grow, mark, and modify the common history tree branch commits list, create, or delete record changes to the repository merge join two or more reorganize trajectories reorganize commits to another core reset tip reset current HEAD to specified state change branch tag Create, list, delete, or verify tag object signed with GPGcollaborate (see also: Git help for workflows) Search Download objects and references from another repository Pull checkout and integrate with another repository or a local branch Push remote references along with related objects update "git help -a" and "gi t help -g" lists the available subcommands and some concept guides. See "git help <command>" or "git help <concept>" for information on a specific subcommand or concept. See 'git help git' for an overview of the system.

git-receive-pack

Receive what is sent to the repository

[email protected]:~# git-receive-pack --helpGIT-RECEIVE-PACK(1) Git Guide GIT-RECEIVE-PACK(1)NAME git-receive-pack - Receive what's pushed into the repository OVERVIEW git-receive-pack <directory> DESCRIPTION Called by git send-pack and updates the repository with the information fed in from the remote end. This command is generally not invoked directly by the end user. The UI for the log is on the Git Send Pack page, and the program pair is intended to be used to push updates to the remote repository. For pull operations, see git-fetch-pack(1). The command allows for the creation and fast forwarding of sha1 references (headers/labels) on the remote side (strictly speaking, it's the local side running git-receive-pack, but for the user running on the git-receive-pack pack sits end).shipping) , upgrade the remote control. Confused?) There are other real world examples of using upgrade and post-upgrade hooks in the documentation/howto directory. git-receive-pack honors the receive.denyNonFastForwards configuration option, which tells you whether to deny updates to a reference when they are not in fast forward. Several other Receive.* configuration options are available to change its behavior, see git-config(1).OPTIONS <directory> The repository to sync with. --http-backend-info-refs Used by git-http-backend(1) to serve requests for $GIT_URL/info/refs?service=git-receive-pack. See --http-backend-info-refs in git-upload-pack(1).PRE-RECEIVE HOOK Before a ref is updated, the $GIT_DIR/hooks/pre-receive file is called if it exists and is executable. once without parameters. The hook's default input is one line per ref to update: sha1-old SP sha1-new SP refname LF The value of refname is relative to $GIT_DIR; eg for the main master this is "refs/heads/master". The two sha1 values ​​in front of each refname are the object names for the refname before and after the update. References to create have sha1-old equal to 0{40}, while references to remove have sha1-new equal to 0{40}; otherwise sha1-old and sha1-new should be valid objects in the repository. When accepting a signed push (see git-push(1)), the signed push certificate is stored in a blob and a GIT_PUSH_CERT environment variable can be queried for its object name. See the post-receive hook description for an example. In addition, the certificate is verified with GPG and the result is exported with the following environment variables: GIT_PUSH_CERT_SIGNER The name and email address of the key owner who signed the push certificate. GIT_PUSH_CERT_KEY The GPG key ID of the key that signed the push certificate. GIT_PUSH_CERT_STATUS The status of the GPG verification of the push certificate using the same mnemonic string as in %G? Format of the git log family of commands (see git-log(1)). GIT_PUSH_CERT_NONCE The nonce string that the process asked the signer to include in the push certificate. If this doesn't match the value recorded in the "nonce" header in the push certificate, this may indicate that the certificate is valid and being replayed from a separate git push session. GIT_PUSH_CERT_NONCE_STATUS NOT REQUESTED "git push --signed" sent a nonce even though we didn't ask them to. MISSING "git push --signed" didn't send any nonce headers. BAD "git push --signed" sent an incorrect nonce. OK, "git push --signed" sent the nonce we asked for. SLOP "git push --signed" sent a different nonce than what we requested now, but in a previous session. See the GIT_PUSH_CERT_NONCE_SLOP environment variable. GIT_PUSH_CERT_NONCE_SLOP "git push --signed" sent a different nonce than the one we've asked it to send now, but in a different session whose start time differs by that many seconds from the current session. It only makes sense if GIT_PUSH_CERT_NONCE_STATUS says SLOP. Also read about the Receive.certNonceSlop variable in git-config(1). This hook is called before a refname is updated and before fast forward checks are performed. If the pre-receive link exits with a non-zero exit status, no updates are performed, nor are the update, post-receive, and post-update links invoked. This can be useful to quickly rescue if the update is not supported. See the quarantine environment notes below. UPDATE HOOK Before each refname is updated, if the file $GIT_DIR/hooks/update exists and is executable, it is called once per refname with three parameters: $GIT_DIR/hooks/update refname sha1-old sha1-new The refname parameter is relative to $GIT_DIR; eg for the main master this is "refs/heads/master". The two sha1 arguments are the object names for the reference name before and after the update. Note that the binding is invoked before the reference name is updated, so sha1-old is 0{40} (meaning no such reference exists yet), or it should match what is registered in the reference name. The link must exit with a non-null status if it wants to prevent the named reference from being updated. Otherwise it should come out with zero. Successful execution (a null exit status) of this hook does not guarantee that the reference will actually be updated, it is only a prerequisite. So it's not a good idea to send notifications (e.g. email) via this link. Consider using the post receipt link instead. is called once without parameters. The binding's standard input consists of one line for each successfully updated ref: sha1-old SP sha1-new SP refname LF The value of refname is relative to $GIT_DIR; eg for the main master this is "refs/heads/master". The two sha1 values ​​in front of each refname are the object names for the refname before and after the update. For created references, sha1-old is 0{40}, while for removed references, sha1-new is 0{40}; otherwise sha1-old and sha1-new should be valid objects in the repository. The GIT_PUSH_CERT* environment variables can be checked just like in the pre-receive hook after accepting a signed push. With this hook, it's easy to generate emails describing updates to the repository. This example script sends a mail-by-reference message listing the commits sent to the repository and records the push certificates of signed pushes with good signatures using a registry service: #!/bin/sh # sends the commit update information by email. while read oval nval ref do if expr "$oval" : '0*$' >/dev/null then echo "Created a new ref, with the following commits:" git rev-list --pretty "$nval" else echo "New commits:" git rev-list --pretty "$nval" "^$oval" fi | mail -s "Changes to ref $ref"[email protected]done # register signed push certificate if available if test -n "${GIT_PUSH_CERT-}" && test ${GIT_PUSH_CERT_STATUS} = G then (expected nonce echo is ${GIT_PUSH_NONCE} git cat-file blob ${GIT_PUSH_CERT } ) | mail -s "Send certificate from $GIT_PUSH_CERT_SIGNER"[email protected]fi exit 0 The exit code of this hook call is ignored, but a non-zero exit code generates an error message. Note that refname may not have sha1-new when this hook runs. This can easily happen if another user changes the reference after git-receive-pack has updated it but before the hook has had a chance to evaluate it. It is recommended that hooks be based on sha1-new instead of the current value of refname. POST-UPDATE HOOK After all other processing, if at least one reference has been updated and the file $GIT_DIR/hooks/post-update exists and is executable, post-update is called with the list of updated references. This can be used to implement any repository-wide cleanup task. The exit code of this hook call is ignored; The only thing git-receive-pack needs to do at this point is exit anyway. For example, this hook can be used to run git update-server-info when the repository is packaged and deployed via a dummy transport. #!/bin/sh exec git update-server-info QUARANTINE ENVIRONMENT When the receive packet receives objects, they are placed in a temporary "quarantine" directory inside the $GIT_DIR/objects directory and only after the pre receive hook has completed. If the insert fails before that date, the temporary directory will be removed entirely. This has some user-visible implications and warnings: 1. Inserts that fail because of problems with the incoming packet, missing objects, or because of the pre-receive hook leave no data on disk. This is often useful to prevent repeated failed inserts from filling up disk, but it can make debugging difficult. 2. All objects created by the pre-receive hook are created in the quarantine directory (and only migrated if successful). 3. The pre-receive binding MUST NOT update references to point to isolated objects. Other programs accessing the repository cannot see the objects (and if the pre-receive hook fails, these references will be broken). For security reasons, all reference updates within Pre-Receive are automatically rejected. SEE ALSO git-send-pack(1), gitnamespaces(7)GIT Part of git(1) suiteGit 2.35.1 02/14/2022 GIT-RECEIVE -PACKAGE(1)

git shell

Restricted login shell for SSH access to Git only

[email protected]:~# git-shell -hfatal: Run with no arguments or with -c cmd

git-upload-archivo

Submit the file back to the git archive

[email protected]:~# git-upload-archive --helpGIT-UPLOAD-ARCHIVE(1) Git Guide GIT-UPLOAD-ARCHIVE(1)NAME git-upload-archive - Send file back to git-archiveSYNOPSIS git upload-archive <directory> DESCRIPTION Called by git archive --remote and sends a generated file to the other end via the Git protocol. This command is generally not invoked directly by the end user. The UI for the log is on the Git file side, and the pair of programs is intended to be used to retrieve a file from a remote repository. SECURITY To protect the privacy of items that have been removed from history but not yet removed. has been truncated, git-upload-archive avoids serving files for commits and trees that are not accessible from repository references. However, since calculating the accessibility of objects is computationally intensive, git-upload-archive implements a stricter but easier to check set of rules: 1. Clients can request a commit or a tree directly referenced by a reference. Example: git archive --remote=origin v1.0. 2. Clients can request a subtree within a commit or tree using the ref:path syntax. Example: git archive --remote=origin v1.0:Documentation. 3. Clients cannot use other sha1 expressions even if the end result can be reached. For example, a relative commit like master^ and a sha1 literal like abcd1234 are not allowed, even if the result is accessible from references. Note that Rule 3 disallows many cases that have no privacy impact. These rules may change in future versions of git, and the server accessed by git archive --remote may or may not follow these exact rules. If the configuration option uploadArchive.allowUnreachable is true, these rules are ignored and clients can use any sha1 expression. This is useful if you don't care about the privacy of unreachable objects, or if your object database is already publicly available for access via dumb HTTP. OPTIONS <directory> The repository to fetch a tar file from.GIT Part of the Git(1) suiteGit 2.35.1 02/14/2022 GIT-UPLOAD-ARCHIVE(1)

git-Upload-Package

Send packed objects back to git-fetch-pack

[email protected]:~# git-upload-pack --helpGIT-UPLOAD-PACK(1) Git manual GIT-UPLOAD-PACK(1)NAME git-upload-pack - Send packed objects back to git-fetch-packSYNOPSIS git-upload- pack [--[no-]strict] [--timeout=<n>] [--stateless-rpc] [--advertise-refs] <directory>DESCRIPTION When called from git fetch-pack, learn what object that other is missing side and will send it after packing. This command is generally not invoked directly by the end user. The UI for the log is on the git fetch-pack side, and the pair of programs are intended to be used to fetch updates from a remote repository. For push operations, see git send-pack.OPTIONS --[no-]strict <directory>/.git/ don't try if <directory> is not a git directory. --timeout=<n> Abort transmission after <n> seconds of inactivity. --stateless-rpc Perform only a single read and write cycle on stdin and stdout. This fits the HTTP POST request processing model, which requires a program to read the request, write a response, and exit. --http-backend-info-refs Used by git-http-backend(1) to serve requests for $GIT_URL/info/refs?service=git-upload-pack. See "Smart Clients" in the HTTP Transport Protocols documentation[1] and "HTTP Transport" in the Git Wire Protocol Version 2 documentation[2]. Also understood by git-receive-pack(1). <directory> The repository to sync from. ENVIRONMENT GIT_PROTOCOL Internal variable for building the connection protocol. Server administrators may need to configure some transports to pass this variable. See the discussion at git(1). SEE ALSO gitnamespaces(7)GIT Part of the git(1) suite. NOTES 1. the file transfer protocols HTTP:///usr/share/doc/git/html/technical/ http-protocol .html 2. the Git Wire protocol version 2 file:///usr/share/doc/git/ html/technical/protocol-v2.htmlGit 2.35.1 02/14/2022 GIT-UPLOAD-PACK( 1)

git-everything

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This is a dummy package containing all subpackages.

Installed size: 957 KB
How to install: sudo apt install git-all

git-cvs

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package provides the Git tools cvsimport, cvsexportcommit, and cvsserver, which allow Git to read and write to CVS repositories and access Git repositories over the CVS protocol.

The git cvsimport tool can import incrementally from a repository that is under active development and requires only remote access via the CVS protocol. Unfortunately, the import leads to incorrect results in many situations. For reliable one-time imports, cvs2git from the cvs2svn or parsecvs package might be a better choice.

Installed size: 1,30MB
How to install: sudo apt install git-cvs

git-cvsserver

A CVS server emulator for Git

[email protected]:~# git-cvsserver --helpUnknown Option: helpusage: git cvsserver [options] [pserver|server] [<directory> ...] --base-path <path> : Prefix the requested CVSROOT Can be read from GIT_CVSSERVER_BASE_PATH - -strict-paths: don't allow recursion in subdirectories --export-all: don't check gitcvs.enabled in configuration --version, -V: print version information and exit -h, -H: print usage information and exit <directory>.. .is a list of allowed directories. If no directories are specified, all are allowed. This is an additional constraint, gitcvsaccess still needs to be enabled via the gitcvs.enabled configuration option. Alternatively, a directory can be specified in GIT_CVSSERVER_ROOT.

git - daemon - run

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

git-daemon, as provided by the git package, is a simple server for git repositories, ideal for read-only updates, i.e. pulling git repositories over the network. This package provides a runit service to keep git-daemon running. This configuration is simpler and more reliable than git-daemon-sysvinit, but at the expense of less-familiar administrators used to sysvinit.

Installed size: 969 KB
How to install: sudo apt install git-daemon-run

git-daemon-sysvinit

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

git-daemon, as provided by the git package, is a simple server for git repositories, ideal for read-only updates, i.e. pulling git repositories over the network. This package provides a sysvinit service to run git-daemon continuously. Unlike git-daemon-run, this package provides the usual sysvinit service management commands ("git-daemon start/stop service") for git-daemon.

Installed size: 972 KB
How to install: sudo apt install git-daemon-sysvinit

git-doc

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package contains the documentation.

Installed size: 11,95MB
How to install: sudo apt install git-doc

git-e-mail

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package provides the git-send-email program to send a series of patch emails.

Installed size: 1,00MB
How to install: sudo apt install git-email

git-gui

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package provides the git graphical user interface.

If a spell is installed, it can check the spelling of commit messages as the user types.

When installed, Meld can be used to view diffs and resolve merge conflicts interactively.

Installed size: 2,32MB
How to install: sudo apt install git-gui

git man

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package contains reference documentation for using the man utility and the git help command.

Installed size: 1,91MB
How to install: sudo apt install git-man

git-mediawiki

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package contains the Mediawiki remote helper, which allows Git to read and write a wiki like Wikipedia as if it were a remote Git repository, and a "git mw" command that can preview how markup is rendered before submission.

Installed size: 1017 KB
How to install: sudo apt install git-mediawiki

git-svn

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package provides tools for collaborating with Subversion repositories and importing SVN development history.

Installed size: 1,17MB
How to install: sudo apt install git-svn

git

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package contains the gitk program, a tcl/tk revision tree viewer.

Installed size: 1,74MB
How to install: sudo apt install gitk

git

Der Git-Repository-Browser

[email protected]:~# gitk -Application-specific initialization failed: failed to connect to display ""Initiation script error: Command-specific options: -sync: use synchronous mode for display server -colormap: colormap for main window -display: display for use -geometry: initial geometry for window -name: name for the application -visual: visual for the main window -use: ID of the window in which to embed the application --: mark end of options -help: print command summary -line and cancel options (processing of arguments in argv variables) called within "load /usr/lib/x86_64-linux-gnu/libtk8 .6.so" ("package if required" Tk 8.6.12 script) within "package required Tk " (file "/usr/bin/gitk" line 10)

gitweb

Git is a popular version control system designed to handle very large projects quickly and efficiently. It is used for many high-profile open source projects, most notably the Linux kernel.

Git falls under the category of distributed source code management tools. Each Git working directory is a complete repository with full revision tracking capabilities that doesn't depend on network access or a central server.

This package sets up a web interface for browsing Git repositories.

If Apache2 is installed, the web interface is automatically available at http://localhost/gitweb. Other servers that support CGI or mod_perl are supported through manual configuration.

If libcgi-fast-perl is installed, gitweb can also run on top of FastCGI (and be served by nginx, for example).

Installed size: 978 KB
How to install: sudo apt install gitweb