1#!/bin/sh
2
3test_description='check handling of .. in submodule names
4
5Exercise the name-checking function on a variety of names, and then give a
6real-world setup that confirms we catch this in practice.
7'
8. ./test-lib.sh
9. "$TEST_DIRECTORY"/lib-pack.sh
10
11test_expect_success 'check names' '
12 cat >expect <<-\EOF &&
13 valid
14 valid/with/paths
15 EOF
16
17 git submodule--helper check-name >actual <<-\EOF &&
18 valid
19 valid/with/paths
20
21 ../foo
22 /../foo
23 ..\foo
24 \..\foo
25 foo/..
26 foo/../
27 foo\..
28 foo\..\
29 foo/../bar
30 EOF
31
32 test_cmp expect actual
33'
34
35test_expect_success 'create innocent subrepo' '
36 git init innocent &&
37 git -C innocent commit --allow-empty -m foo
38'
39
40test_expect_success 'submodule add refuses invalid names' '
41 test_must_fail \
42 git submodule add --name ../../modules/evil "$PWD/innocent" evil
43'
44
45test_expect_success 'add evil submodule' '
46 git submodule add "$PWD/innocent" evil &&
47
48 mkdir modules &&
49 cp -r .git/modules/evil modules &&
50 write_script modules/evil/hooks/post-checkout <<-\EOF &&
51 echo >&2 "RUNNING POST CHECKOUT"
52 EOF
53
54 git config -f .gitmodules submodule.evil.update checkout &&
55 git config -f .gitmodules --rename-section \
56 submodule.evil submodule.../../modules/evil &&
57 git add modules &&
58 git commit -am evil
59'
60
61# This step seems like it shouldn't be necessary, since the payload is
62# contained entirely in the evil submodule. But due to the vagaries of the
63# submodule code, checking out the evil module will fail unless ".git/modules"
64# exists. Adding another submodule (with a name that sorts before "evil") is an
65# easy way to make sure this is the case in the victim clone.
66test_expect_success 'add other submodule' '
67 git submodule add "$PWD/innocent" another-module &&
68 git add another-module &&
69 git commit -am another
70'
71
72test_expect_success 'clone evil superproject' '
73 git clone --recurse-submodules . victim >output 2>&1 &&
74 ! grep "RUNNING POST CHECKOUT" output
75'
76
77test_expect_success 'fsck detects evil superproject' '
78 test_must_fail git fsck
79'
80
81test_expect_success 'transfer.fsckObjects detects evil superproject (unpack)' '
82 rm -rf dst.git &&
83 git init --bare dst.git &&
84 git -C dst.git config transfer.fsckObjects true &&
85 test_must_fail git push dst.git HEAD
86'
87
88test_expect_success 'transfer.fsckObjects detects evil superproject (index)' '
89 rm -rf dst.git &&
90 git init --bare dst.git &&
91 git -C dst.git config transfer.fsckObjects true &&
92 git -C dst.git config transfer.unpackLimit 1 &&
93 test_must_fail git push dst.git HEAD
94'
95
96# Normally our packs contain commits followed by trees followed by blobs. This
97# reverses the order, which requires backtracking to find the context of a
98# blob. We'll start with a fresh gitmodules-only tree to make it simpler.
99test_expect_success 'create oddly ordered pack' '
100 git checkout --orphan odd &&
101 git rm -rf --cached . &&
102 git add .gitmodules &&
103 git commit -m odd &&
104 {
105 pack_header 3 &&
106 pack_obj $(git rev-parse HEAD:.gitmodules) &&
107 pack_obj $(git rev-parse HEAD^{tree}) &&
108 pack_obj $(git rev-parse HEAD)
109 } >odd.pack &&
110 pack_trailer odd.pack
111'
112
113test_expect_success 'transfer.fsckObjects handles odd pack (unpack)' '
114 rm -rf dst.git &&
115 git init --bare dst.git &&
116 test_must_fail git -C dst.git unpack-objects --strict <odd.pack
117'
118
119test_expect_success 'transfer.fsckObjects handles odd pack (index)' '
120 rm -rf dst.git &&
121 git init --bare dst.git &&
122 test_must_fail git -C dst.git index-pack --strict --stdin <odd.pack
123'
124
125test_expect_success 'index-pack --strict works for non-repo pack' '
126 rm -rf dst.git &&
127 git init --bare dst.git &&
128 cp odd.pack dst.git &&
129 test_must_fail git -C dst.git index-pack --strict odd.pack 2>output &&
130 # Make sure we fail due to bad gitmodules content, not because we
131 # could not read the blob in the first place.
132 grep gitmodulesName output
133'
134
135test_expect_success 'fsck detects symlinked .gitmodules file' '
136 git init symlink &&
137 (
138 cd symlink &&
139
140 # Make the tree directly to avoid index restrictions.
141 #
142 # Because symlinks store the target as a blob, choose
143 # a pathname that could be parsed as a .gitmodules file
144 # to trick naive non-symlink-aware checking.
145 tricky="[foo]bar=true" &&
146 content=$(git hash-object -w ../.gitmodules) &&
147 target=$(printf "$tricky" | git hash-object -w --stdin) &&
148 {
149 printf "100644 blob $content\t$tricky\n" &&
150 printf "120000 blob $target\t.gitmodules\n"
151 } | git mktree &&
152
153 # Check not only that we fail, but that it is due to the
154 # symlink detector; this grep string comes from the config
155 # variable name and will not be translated.
156 test_must_fail git fsck 2>output &&
157 grep gitmodulesSymlink output
158 )
159'
160
161test_expect_success 'fsck detects non-blob .gitmodules' '
162 git init non-blob &&
163 (
164 cd non-blob &&
165
166 # As above, make the funny tree directly to avoid index
167 # restrictions.
168 mkdir subdir &&
169 cp ../.gitmodules subdir/file &&
170 git add subdir/file &&
171 git commit -m ok &&
172 git ls-tree HEAD | sed s/subdir/.gitmodules/ | git mktree &&
173
174 test_must_fail git fsck 2>output &&
175 grep gitmodulesBlob output
176 )
177'
178
179test_expect_success 'fsck detects corrupt .gitmodules' '
180 git init corrupt &&
181 (
182 cd corrupt &&
183
184 echo "[broken" >.gitmodules &&
185 git add .gitmodules &&
186 git commit -m "broken gitmodules" &&
187
188 git fsck 2>output &&
189 grep gitmodulesParse output &&
190 test_i18ngrep ! "bad config" output
191 )
192'
193
194test_done