delta/libgit2.git/src, branch hf/master_patch github.com: libgit2/libgit2.git treebuilder: take a repository for path validation 2014-12-17T18:05:27+00:00 Edward Thomson ethomson@microsoft.com 2014-12-17T01:24:04+00:00 dce7b1a4e75551804a33591744d40d0582c57cfb Path validation may be influenced by `core.protectHFS` and `core.protectNTFS` configuration settings, thus treebuilders can take a repository to influence their configuration. 
Path validation may be influenced by `core.protectHFS` and
`core.protectNTFS` configuration settings, thus treebuilders
can take a repository to influence their configuration.
Introduce core.protectHFS and core.protectNTFS 2014-12-17T17:52:07+00:00 Edward Thomson ethomson@microsoft.com 2014-12-17T00:53:55+00:00 ec74b40ceef3dc3892c7d84bb4f5d99bab504ba4 Validate HFS ignored char ".git" paths when `core.protectHFS` is specified. Validate NTFS invalid ".git" paths when `core.protectNTFS` is specified. 
Validate HFS ignored char ".git" paths when `core.protectHFS` is
specified.  Validate NTFS invalid ".git" paths when `core.protectNTFS`
is specified.
path: Use UTF8 iteration for HFS chars 2014-12-16T16:24:18+00:00 Vicent Marti tanoku@gmail.com 2014-12-16T12:03:02+00:00 8e35527de25ac156f3600e2ce49b0c3483c258c4 






checkout: disallow bad paths on HFS
2014-12-16T16:08:59+00:00

Edward Thomson
ethomson@microsoft.com

2014-12-11T00:12:16+00:00

11d67b754d47967642570f796601e8850f001d73

HFS filesystems ignore some characters like U+200C.  When these
characters are included in a path, they will be ignored for the
purposes of comparison with other paths.  Thus, if you have a ".git"
folder, a folder of ".git<U+200C>" will also match.  Protect our
".git" folder by ensuring that ".git<U+200C>" and friends do not match it.





HFS filesystems ignore some characters like U+200C.  When these
characters are included in a path, they will be ignored for the
purposes of comparison with other paths.  Thus, if you have a ".git"
folder, a folder of ".git<U+200C>" will also match.  Protect our
".git" folder by ensuring that ".git<U+200C>" and friends do not match it.







reference_create: validate loose names
2014-12-16T16:08:56+00:00

Edward Thomson
ethomson@microsoft.com

2014-12-03T03:20:42+00:00

ee5da720e58f8870e5b6b272ef7514c2a717544a

Validate loose reference names on Win32.





Validate loose reference names on Win32.







checkout: disallow bad paths on win32
2014-12-16T16:08:53+00:00

Edward Thomson
ethomson@microsoft.com

2014-11-25T23:13:00+00:00

a64119e3963fcd358ba914c9e1a81a890666d15a

Disallow:
 1. paths with trailing dot
 2. paths with trailing space
 3. paths with trailing colon
 4. paths that are 8.3 short names of .git folders ("GIT~1")
 5. paths that are reserved path names (COM1, LPT1, etc).
 6. paths with reserved DOS characters (colons, asterisks, etc)

These paths would (without \\?\ syntax) be elided to other paths - for
example, ".git." would be written as ".git".  As a result, writing these
paths literally (using \\?\ syntax) makes them hard to operate with from
the shell, Windows Explorer or other tools.  Disallow these.





Disallow:
 1. paths with trailing dot
 2. paths with trailing space
 3. paths with trailing colon
 4. paths that are 8.3 short names of .git folders ("GIT~1")
 5. paths that are reserved path names (COM1, LPT1, etc).
 6. paths with reserved DOS characters (colons, asterisks, etc)

These paths would (without \\?\ syntax) be elided to other paths - for
example, ".git." would be written as ".git".  As a result, writing these
paths literally (using \\?\ syntax) makes them hard to operate with from
the shell, Windows Explorer or other tools.  Disallow these.







index: Check for valid paths before creating an index entry
2014-12-16T16:08:49+00:00

Vicent Marti
tanoku@gmail.com

2014-11-24T23:58:03+00:00

0d388adc86946f3c8cddc2493b470d47a653c4a5












tree: Check for `.git` with case insensitivy
2014-12-16T16:08:46+00:00

Vicent Marti
tanoku@gmail.com

2014-11-24T23:14:52+00:00

62155257d2d30d8f8d7108539df0681dce27ff61












win32: use NT-prefixed "\\?\" paths
2014-12-16T16:08:43+00:00

Edward Thomson
ethomson@microsoft.com

2014-12-01T18:09:58+00:00

cceae9a25d0bed8b00f4981e051d5f380ef54401

When turning UTF-8 paths into UCS-2 paths for Windows, always use
the \\?\-prefixed paths.  Because this bypasses the system's
path canonicalization, handle the canonicalization functions ourselves.

We must:
 1. always use a backslash as a directory separator
 2. only use a single backslash between directories
 3. not rely on the system to translate "." and ".." in paths
 4. remove trailing backslashes, except at the drive root (C:\)





When turning UTF-8 paths into UCS-2 paths for Windows, always use
the \\?\-prefixed paths.  Because this bypasses the system's
path canonicalization, handle the canonicalization functions ourselves.

We must:
 1. always use a backslash as a directory separator
 2. only use a single backslash between directories
 3. not rely on the system to translate "." and ".." in paths
 4. remove trailing backslashes, except at the drive root (C:\)







push: fold unpack_ok() into finish()
2014-12-10T17:55:54+00:00

Carlos Martín Nieto
cmn@dwim.me

2014-12-10T16:23:33+00:00

d524b2d3d13cd306f4405b2e48cf586c04e4e5dc

The push cannot be successful if we sent a bad packfile. We should
return an error in that case instead of storing it elsewhere.





The push cannot be successful if we sent a bad packfile. We should
return an error in that case instead of storing it elsewhere.