hgweb: fix trust of templates path (BC) Long ago we disabled trust of the templates path with a comment describing the (insecure) behavior before the change. At some later refactor, the code was apparently changed back to match the comment, unaware that the intent of the comment was to describe the behavior to avoid. This change disables the trust and updates the comment to explicitly say not only what the old problem was, but also that it was in fact a problem and the action taken to prevent it. Impact: prior to this change, if you had a UNIX-based hgweb server where users can write hgrc files, those users could potentially read any file readable by the web server. This is marked as a backwards compatibility issue because people may have configured templates without proper trust settings. Issue spotted by Greg Szorc.

     1

test --time

     2

     3

  $ hg --time help -q help 2>&1 | grep time > /dev/null

     4

  $ hg init a

     5

  $ cd a

     6

     7

#if lsprof

     8

     9

test --profile

    10

    11

  $ hg --profile st 2>../out

    12

  $ grep CallCount ../out > /dev/null || cat ../out

    13

    14

  $ hg --profile --config profiling.output=../out st

    15

  $ grep CallCount ../out > /dev/null || cat ../out

    16

    17

  $ hg --profile --config profiling.format=text st 2>../out

    18

  $ grep CallCount ../out > /dev/null || cat ../out

    19

    20

  $ echo "[profiling]" >> $HGRCPATH

    21

  $ echo "format=kcachegrind" >> $HGRCPATH

    22

    23

  $ hg --profile st 2>../out

    24

  $ grep 'events: Ticks' ../out > /dev/null || cat ../out

    25

    26

  $ hg --profile --config profiling.output=../out st

    27

  $ grep 'events: Ticks' ../out > /dev/null || cat ../out

    28

    29

#endif

    30

    31

  $ cd ..