| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
When the repository is opened with `GIT_REPOSITORY_OPEN_FROM_ENV`, honor
the `GIT_CONFIG_GLOBAL`, `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_NOSYSTEM`
environment variables.
|
| |
|
|
|
| |
When the repository is opened with `GIT_REPOSITORY_OPEN_FROM_ENV`, honor
the `GIT_COMMON_DIR` environment variable.
|
| |
|
|
|
| |
When the repository is opened with `GIT_REPOSITORY_OPEN_FROM_ENV`, honor
the `GIT_WORK_TREE` environment variable.
|
| |
|
|
| |
Shocked that our leak checkers didn't find this earlier.
|
| | |
|
| | |
|
| |
|
|
|
| |
The longest path within a git repository is now a SHA256 format
packfile. Adjust our max length checking to match.
|
| |
|
|
|
| |
Ensure that we maintain the `core.repositoryFormatVersion` value instead
of always overwriting it with the default.
|
| |
|
|
|
|
| |
Teach the repository about the `objectformat` extension, supporting
`sha1` always and `sha256` when the experimental sha256 support is
active.
|
| |
|
|
| |
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|
| | |
|
| |
|
|
|
| |
The experimental function signature is only available when
`GIT_EXPERIMENTAL_SHA256` is enabled.
|
| |\
| |
| | |
RFC: SHA256 proof of concept
|
| | |
| |
| |
| |
| | |
Users will need to be able to specify the object id type for the given
object database; add a new `git_odb_options` with that option.
|
| | |
| |
| |
| |
| | |
The git_odb_hash helper functions should not assume SHA1, and instead
should be given the oid type that they're producing.
|
| | |
| |
| |
| |
| | |
`git_oid`s now have a type, and we require the oid type when creating
the object id from creation functions.
|
| | |
| |
| |
| |
| | |
In preparation for SHA256 support, `GIT_OID_RAWSZ` and `GIT_OID_HEXSZ`
need to indicate that they're the size of _SHA1_ OIDs.
|
| | |
| |
| |
| |
| | |
Allow users in the administrator group to use git configs that are owned
by administrators.
|
| | |
| |
| |
| |
| |
| | |
The file ownership concepts can reflect the actual file ownership, they
are not necessarily limited to mocking the interface. Rename them so
that they can be more broadly applicable.
|
| | |
| |
| |
| | |
Ensure that we test opening a bare repository with odd permissions.
|
| |/
|
|
|
|
|
|
| |
This reverts commit cdff2f0237f663e0f68155655a8b66d05c1ec716.
This change erroneously allowed system users to own a worktree; this
should only be allowed when the current user is in the Administrator
group on Windows as well.
|
| |
|
|
|
|
|
| |
Update our ownership checks that were introduced in libgit2 v1.4.3
(to combat CVE 2022-24765). These were not compatible with git's; git
itself allows administrators to own the path. Our checks now match
this behavior.
|
| |
|
|
|
| |
Introduce the `GIT_OPT_SET_OWNER_VALIDATION` option, so that users can
disable repository ownership validation.
|
| |
|
|
|
|
|
| |
Obey the `safe.directory` configuration variable if it is set in the
global or system configuration. (Do not try to load this from the
repository configuration - to avoid malicious repositories that then
mark themselves as safe.)
|
| |
|
|
|
| |
Test that we prevent opening directories that are not owned by
ourselves.
|
|
|
Like we want to separate libgit2 and utility source code, we want to
separate libgit2 and utility tests. Start by moving all the tests into
libgit2.
|