delta/libgit2.git/src, branch hf/021_patch github.com: libgit2/libgit2.git Introduce core.protectHFS and core.protectNTFS 2014-12-17T21:43:45+00:00 Edward Thomson ethomson@microsoft.com 2014-12-17T00:53:55+00:00 2b37e33f13696e5946386fd026d98f5fce6119a2 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-17T21:43:39+00:00 Vicent Marti tanoku@gmail.com 2014-12-16T12:03:02+00:00 581368fff37a542a2e45f56dc1681e8038daa446 






checkout: disallow bad paths on HFS
2014-12-17T21:43:32+00:00

Edward Thomson
ethomson@microsoft.com

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

43201809f860108355e3de2238ffa9479c6d1793

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-17T21:43:25+00:00

Edward Thomson
ethomson@microsoft.com

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

8e7a95784440a348a8c3bc89af3b36d5781657cb

Validate loose reference names on Win32.





Validate loose reference names on Win32.







checkout: disallow bad paths on win32
2014-12-17T21:43:18+00:00

Edward Thomson
ethomson@microsoft.com

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

9686c6bbf42be0a8f6df7aab71d93ecbe66923ea

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-17T21:43:11+00:00

Vicent Marti
tanoku@gmail.com

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

12db885bbc85cef9a03152eda7a2e5365bd5e0b4












tree: Check for `.git` with case insensitivy
2014-12-17T21:43:05+00:00

Vicent Marti
tanoku@gmail.com

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

928429c5c96a701bcbcafacb2421a82602b36915












win32: use NT-prefixed "\\?\" paths
2014-12-17T21:42:58+00:00

Edward Thomson
ethomson@microsoft.com

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

09361dfe7b3206c9e2edd975ed71f1b74cd22ede

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:\)







global: clean up openssl_locks on shutdown
2014-10-26T22:48:40+00:00

Edward Thomson
ethomson@edwardthomson.com

2014-10-25T23:52:11+00:00

cc71348db9dbfa348199c357235fa30e61f1009a












Fixed memory leak in git_tag_delete()
2014-10-25T19:10:27+00:00

Pierre-Olivier Latour
pol@mac.com

2014-10-24T15:23:14+00:00

559528734fe8a6be148670ba34d79e58c1f48d3d