| Age | Commit message (Collapse) | Author | Lines |
|
The links have been written through html_attr since b8adfd6, so with
the percent-encoding dropped a quote came out as an entity the absence
check could not match, and the presence check was met by the file
links above the diff. The test now reads the line links themselves,
for a name holding a hash and a question mark as well.
|
|
Only the commit page was checked, and only for onchange, though a site
policy without unsafe-inline blocks every inline handler on any page.
|
|
The escaped script tag alone matched either readme, so the markdown
page showing the text readme passed.
|
|
The test took any page holding the word top, with no status checked.
The refusal half lives in t0204, so the fixture now says why its limit
is set so low.
|
|
The refusal was read from a page the previous test had left, which
--run could skip, and both requests went through the shared page
cache. The marker is also named apart from the one the filter test
plants, so a failure in one cannot fail the other.
|
|
Only head-content and logo-link were tried, so logo, clone-url and
both module-link forms could have been taken from a repository's own
cgitrc unnoticed. A trusted control shows each value would reach the
page, and the refused disk readmes are now checked against a file that
would show if read.
|
|
No test asserted the Content-Security-Policy header, though it is all
that keeps script in an SVG from running when the plain page serves it
under its own type.
|
|
Every candidate name meets check_refname_format first, which refuses
the old payload, so the slash rule never answered it and could go
unnoticed. A tag holding a slash reaches it, and a name in revision
syntax without a slash now pins the ref name check of its own.
|
|
dash reports a write to a closed pipe as an I/O error and never names
a broken pipe, so where sh is dash the test passed with the reset
removed. The writer now leaves a marker when it outlives the closed
pipe, which it can only do with the signal ignored. That holds under
dash, bash and ksh.
|
|
The posted body was 22 bytes, so an unclamped read stopped at its end
and nothing overflowed, and the test could not fail. The filter now
counts what it was handed from a body larger than the buffer.
|
|
The unedited copy and the login page were requested through cgit_rc,
so a page cut short or an error logged on the way passed. The owner and
description checks on the login page could not fail either if the
config lost them, so the same config with a filter that lets the
visitor in now has to show both.
|
|
With no standalone Lua on the path the unit checks were never
registered, so they counted as neither run nor skipped, and t0505
passed on its cgit checks alone.
|
|
|
|
No hook ran the way git runs it, so the shebang, the executable bit,
GIT_DIR, the refs on stdin and the remote: lines a pusher sees were all
untested.
|
|
The header says a git too old for the options leaves the graph as it
was and the hook stays silent, but every run had a git that could
write it.
|
|
Only sh, dash, ksh and bash were tried, so busybox sh ran only where it
is /bin/sh, and mksh, yash, posh and zsh's sh mode never ran. Where sh
is a link to dash, the same shell ran twice. A shell reached by two
names now runs once, and the list is said so a run shows what it
covered.
|
|
README tells a visitor to write a plus in the query form as %2b, and
cgit caches such a page under the raw query, but the hook compared that
query with the url as it stands. A push to foo+bar.git left its pages
under url=foo%2bbar.git/ and r=foo%2Bbar.git cached and stale until
their ttl ran out. Decoding in sh would take more than the hook is
worth, so a query with a % or a + now counts as stale, which costs
another repository's page at most a refill.
|
|
No page asked for with r= was cached, no slot held a head that does not
parse as cgit's, and the hook never met a cache root that was missing,
so ignoring r=, keeping an unreadable slot, or complaining without a
cache all passed.
|
|
|
|
run_action repeated harness.run line for line, and three comments only
labelled the sections below them.
|
|
Both say a change to the code they share belongs in both, but nothing
held them to it, so a fix made to one alone in a path the unit checks
do not reach would have gone unseen.
|
|
The fake HMAC returned 16 bytes, so the checks signed with signatures
half the real length, and a signature cut short passed. tohex's output
was never pinned either, so dropping its zero padding stayed
consistent with itself and passed.
|
|
A cookie_path other than / has to keep Secure but drop the __Host-
name, which a browser takes only for the whole host. Neither was
tried.
|
|
An expired session was only tried against validate_value, never sent
through a visit, and nothing sent a session under the plain cookie
name, which a sibling subdomain can set where it cannot set the
__Host- one.
|
|
The checks that a forged session is not taken for a signed-in visitor,
and that https brings no warning, would also have passed on the page
saying logins are unavailable.
|
|
crypt(3) answers nil for a kind of hash the system does not check, but
the stand-in never did, so a login that raised on it, or let it
through, passed.
|
|
The check was a negated test_cmp, which also passes when either file
is missing, and a changed chain does not prove the new layer was
written. The chain's last line now has to name a graph file that
exists and was not in the chain before the push.
|
|
scan-path finds such a repository by its .git and serves it at the
work tree's path, so the hook has to strip the /.git it runs in. Only
bare repositories were tried, and a hook that kept it passed.
|
|
Nothing ran the hook against a cache filled with remove-suffix=1, so
a hook that kept the .git on the url, and so dropped none of the pages
cgit had cached under the shorter one, passed.
|
|
The hook exists to feed the idle column, but nothing had cgit read an
age file, so a hook writing a date cgit cannot parse, or one at a path
cgit no longer reads, passed.
|
|
The header said a file the pusher cannot write stays as it was, but the
hook replaces it through mv, which needs only the directory, and with
stdin not a terminal mv does so without asking. That is the useful
behaviour, so the header now says so, and a test holds the hook to it.
Only a directory the pusher cannot write keeps the old file, which was
the one case tested.
|
|
A repository with no branches is meant to keep the date cgit already
had, and the hook writes through a temporary file that must not be
left beside the real one. Neither was checked.
|
|
No hook ran under a restrictive umask, so dropping the forced umask 022
passed, and the age file and the graph would then be unreadable to the
web server. Git alone writes the graph as -r-------- under umask 077.
core.sharedRepository was only tried as group, so the case folding and
the numeric modes went unchecked.
|
|
The cache hook's named url, no url and no access cases, the age hook's
missing directory and shared group, and the first commit-graph write
ran under sh alone, though the comment said every shell. The runs that
did loop over the shells ignored what the hook printed, which reaches
the pusher, so a hook that wrote to stderr or broke on a bashism under
dash alone could pass.
|
|
The checks that pages went had nothing proving they were there to begin
with, so they would pass with nothing removed if the scan list stopped
being written or two keys shared a slot. Nor did anything check that
the copy of the hook was pointed at the trash directory, and a renamed
line would have left it wiping the system's cache wherever the test
user can write it.
cached_requests read the lock and the scan list as if they were pages
and hid a failing dd. The test without access could not fail, since
nothing can be removed there and the scan list alone names a.git, so
it now compares the slots with the pristine copy.
|
|
Every account shared one hash, so the binding of a session to its
account's hash could not tell accounts apart, and an account_hash that
handed back the wrong account's hash passed.
|
|
A failed login on a page with no query of its own comes back as
?login=failed, the common case, but only the &login=failed form was
tried. A drop_failure_flag that handled the ampersand alone would have
lost the message and piled flags onto the way back, and passed.
|
|
Every post carried both fields, so the guards for a missing name or
password never ran. An unknown name was checked for the cookie and the
Location alone, so an extra header or body for it passed, and only the
wrong password case had its log line checked for the name and against
the password.
|
|
The cgit-level check accepted any line starting "[cgit] ", the prefix
of cgit's own messages too, as proof that the filter logged a missing
module. The guarded copy also kept the system secret path, so on a
host with luaossl and a readable secret but no luaposix the form would
be signed and the test would fail.
|
|
Only all four libraries missing at once was tried, and the script was
not reloaded after they went, so a require at load would not have
failed there. The protected visit passed on any error, a typo's nil
call included. A login never ran without a library, so a fallback that
skipped the mask, or one that let any password through when crypt was
missing, passed.
|
|
The quadratic trim takes 0.58 seconds for the 20,000 spaces the check
used under LuaJIT on an M-series Mac, against a threshold of half a
second over two calls, so a regression could pass on a slightly faster
core. At 100,000 spaces it takes about fifteen seconds and the linear
one under a millisecond, and each call is now timed on its own.
|
|
The exponent and leading separator cases carried a made-up signature,
which fails the check whatever the parsing does, so loosening the
expiry pattern or dropping its start anchor passed. Both are now built
from properly signed tokens.
|
|
auth-file.lua says group names match whatever their case, but both
fixture files spelt devs alike, so dropping either lowercasing passed.
No repository named two groups and no user sat in two, so reading only
the first group of a list, or only the last line that matched, passed
as well. A repository with no groups at all is a file variant matter,
and for the inline one the check only repeated the empty one.
|
|
The age fixture had one branch whose author and committer dates were
the same, and its only tag was lightweight on that commit. Sorting
oldest first, writing the author date or reading every ref rather than
the branches all passed, and the expected date came from the same
for-each-ref the hook runs. The dates now disagree on every one of
those points and the hook's answer is held to a literal date, under
every shell.
|
|
is_safe_redirect looked at the first two characters alone, so it
accepted https://evil.example/ and javascript:x. Neither could be
signed today only because cgit always signs a url that starts with
virtual-root, and nothing tested that. A target now has to start with
a single slash, which needs virtual-root to be a path for logins to
work, as it is by default.
|
|
The unit checks always took the harness stand-ins and the cgit-level
checks needed a module to be missing, so the real luaossl and luaposix
were never exercised anywhere. A misuse of their interfaces, or a login
through cgit that never worked, passed every run.
Where an interpreter has both libraries and its crypt(3) checks a
SHA-512 hash from openssl passwd, the unit checks run again against
them, adding the secret's mode. Where cgit's own Lua does, a login is
posted through cgit and the cookie it grants opens the repository. Both
skip where crypt checks no SHA-512 hash or the libraries are missing.
|
|
login() in the checks posts username and password under names of its
own, so renaming either field in the form broke every real login while
the suite passed.
|
|
Both shipped filters key their access lists by a repository's url, and
MANUAL says cgit hands that over, but nothing read the argument. Every
auth test served a repository whose url and name were the same, so a
cgit that passed repo.name, under which a url-keyed list matches
nothing and every protected repository goes public, passed.
|
|
Only a missing users file and a missing repos file were tried. A
missing groups file denies today, but a change returning nil there
would have made every protected repository public unnoticed. The repos
file's log line and a users file with no line that parses, which has
to turn a login down without spending crypt, went unchecked too.
|
|
constant_equals was only checked for its answers, on strings that
differ in one byte. Summing the plain differences instead of their
squares passed, which accepts any signature with the same byte sum, and
so did a plain == at the signature or the password check.
|