upstream/mercurial-mirror Files · tests/test-dirstate.t

dispatch: protect against malicious 'hg serve --stdio' invocations (sec)...

dispatch: protect against malicious 'hg serve --stdio' invocations (sec) Some shared-ssh installations assume that 'hg serve --stdio' is a safe command to run for minimally trusted users. Unfortunately, the messy implementation of argument parsing here meant that trying to access a repo named '--debugger' would give the user a pdb prompt, thereby sidestepping any hoped-for sandboxing. Serving repositories over HTTP(S) is unaffected. We're not currently hardening any subcommands other than 'serve'. If your service exposes other commands to users with arbitrary repository names, it is imperative that you defend against repository names of '--debugger' and anything starting with '--config'. The read-only mode of hg-ssh stopped working because it provided its hook configuration to "hg serve --stdio" via --config parameter. This is banned for security reasons now. This patch switches it to directly call ui.setconfig(). If your custom hosting infrastructure relies on passing --config to "hg serve --stdio", you'll need to find a different way to get that configuration into Mercurial, either by using ui.setconfig() as hg-ssh does in this patch, or by placing an hgrc file someplace where Mercurial will read it. mitrandir@fb.com provided some extra fixes for the dispatch code and for hg-ssh in places that I overlooked.

Pierre-Yves David - - Load All Authors

File last commit:

r26587:56b2bcea default


                r32050:77eaf953

4.1.3 stable

Download file

             test-dirstate.t
        
                    88 lines
            
             | 1.8 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-dirstate.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      ------ Test dirstate._dirs refcounting

        $ hg init t

        $ cd t

        $ mkdir -p a/b/c/d

        $ touch a/b/c/d/x

        $ touch a/b/c/d/y

        $ touch a/b/c/d/z

        $ hg ci -Am m

        adding a/b/c/d/x

        adding a/b/c/d/y

        adding a/b/c/d/z

        $ hg mv a z

        moving a/b/c/d/x to z/b/c/d/x (glob)

        moving a/b/c/d/y to z/b/c/d/y (glob)

        moving a/b/c/d/z to z/b/c/d/z (glob)

      Test name collisions

        $ rm z/b/c/d/x

        $ mkdir z/b/c/d/x

        $ touch z/b/c/d/x/y

        $ hg add z/b/c/d/x/y

        abort: file 'z/b/c/d/x' in dirstate clashes with 'z/b/c/d/x/y'

        [255]

        $ rm -rf z/b/c/d

        $ touch z/b/c/d

        $ hg add z/b/c/d

        abort: directory 'z/b/c/d' already in dirstate

        [255]

        $ cd ..

      Issue1790: dirstate entry locked into unset if file mtime is set into

      the future

      Prepare test repo:

        $ hg init u

        $ cd u

        $ echo a > a

        $ hg add

        adding a

        $ hg ci -m1

      Set mtime of a into the future:

        $ touch -t 202101011200 a

      Status must not set a's entry to unset (issue1790):

        $ hg status

        $ hg debugstate

        n 644          2 2021-01-01 12:00:00 a

      Test modulo storage/comparison of absurd dates:

      #if no-aix

        $ touch -t 195001011200 a

        $ hg st

        $ hg debugstate

        n 644          2 2018-01-19 15:14:08 a

      #endif

      Verify that exceptions during a dirstate change leave the dirstate

      coherent (issue4353)

        $ cat > ../dirstateexception.py <<EOF

        > from mercurial import merge, extensions, error

        > 

        > def wraprecordupdates(orig, repo, actions, branchmerge):

        >     raise error.Abort("simulated error while recording dirstateupdates")

        > 

        > def reposetup(ui, repo):

        >     extensions.wrapfunction(merge, 'recordupdates', wraprecordupdates)

        > EOF

        $ hg rm a

        $ hg commit -m 'rm a'

        $ echo "[extensions]" >> .hg/hgrc

        $ echo "dirstateex=../dirstateexception.py" >> .hg/hgrc

        $ hg up 0

        abort: simulated error while recording dirstateupdates

        [255]

        $ hg log -r . -T '{rev}\n'

        1

        $ hg status

        ? a

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				------ Test dirstate._dirs refcounting

				$ hg init t
				$ cd t
				$ mkdir -p a/b/c/d
				$ touch a/b/c/d/x
				$ touch a/b/c/d/y
				$ touch a/b/c/d/z
				$ hg ci -Am m
				adding a/b/c/d/x
				adding a/b/c/d/y
				adding a/b/c/d/z
				$ hg mv a z
				moving a/b/c/d/x to z/b/c/d/x (glob)
				moving a/b/c/d/y to z/b/c/d/y (glob)
				moving a/b/c/d/z to z/b/c/d/z (glob)

				Test name collisions

				$ rm z/b/c/d/x
				$ mkdir z/b/c/d/x
				$ touch z/b/c/d/x/y
				$ hg add z/b/c/d/x/y
				abort: file 'z/b/c/d/x' in dirstate clashes with 'z/b/c/d/x/y'
				[255]
				$ rm -rf z/b/c/d
				$ touch z/b/c/d
				$ hg add z/b/c/d
				abort: directory 'z/b/c/d' already in dirstate
				[255]

				$ cd ..

				Issue1790: dirstate entry locked into unset if file mtime is set into
				the future

				Prepare test repo:

				$ hg init u
				$ cd u
				$ echo a > a
				$ hg add
				adding a
				$ hg ci -m1

				Set mtime of a into the future:

				$ touch -t 202101011200 a

				Status must not set a's entry to unset (issue1790):

				$ hg status
				$ hg debugstate
				n 644 2 2021-01-01 12:00:00 a

				Test modulo storage/comparison of absurd dates:

				#if no-aix
				$ touch -t 195001011200 a
				$ hg st
				$ hg debugstate
				n 644 2 2018-01-19 15:14:08 a
				#endif

				Verify that exceptions during a dirstate change leave the dirstate
				coherent (issue4353)

				$ cat > ../dirstateexception.py <<EOF
				> from mercurial import merge, extensions, error
				>
				> def wraprecordupdates(orig, repo, actions, branchmerge):
				> raise error.Abort("simulated error while recording dirstateupdates")
				>
				> def reposetup(ui, repo):
				> extensions.wrapfunction(merge, 'recordupdates', wraprecordupdates)
				> EOF

				$ hg rm a
				$ hg commit -m 'rm a'
				$ echo "[extensions]" >> .hg/hgrc
				$ echo "dirstateex=../dirstateexception.py" >> .hg/hgrc
				$ hg up 0
				abort: simulated error while recording dirstateupdates
				[255]
				$ hg log -r . -T '{rev}\n'
				1
				$ hg status
				? a