upstream/mercurial-mirror Files · tests/test-rename-after-merge.t

sslutil: require TLS 1.1+ when supported...

sslutil: require TLS 1.1+ when supported Currently, Mercurial will use TLS 1.0 or newer when connecting to remote servers, selecting the highest TLS version supported by both peers. On older Pythons, only TLS 1.0 is available. On newer Pythons, TLS 1.1 and 1.2 should be available. Security professionals recommend avoiding TLS 1.0 if possible. PCI DSS 3.1 "strongly encourages" the use of TLS 1.2. Known attacks like BEAST and POODLE exist against TLS 1.0 (although mitigations are available and properly configured servers aren't vulnerable). I asked Eric Rescorla - Mozilla's resident crypto expert - whether Mercurial should drop support for TLS 1.0. His response was "if you can get away with it." Essentially, a number of servers on the Internet don't support TLS 1.1+. This is why web browsers continue to support TLS 1.0 despite desires from security experts. This patch changes Mercurial's default behavior on modern Python versions to require TLS 1.1+, thus avoiding known security issues with TLS 1.0 and making Mercurial more secure by default. Rather than drop TLS 1.0 support wholesale, we still allow TLS 1.0 to be used if configured. This is a compromise solution - ideally we'd disallow TLS 1.0. However, since we're not sure how many Mercurial servers don't support TLS 1.1+ and we're not sure how much user inconvenience this change will bring, I think it is prudent to ship an escape hatch that still allows usage of TLS 1.0. In the default case our users get better security. In the worst case, they are no worse off than before this patch. This patch has no effect when running on Python versions that don't support TLS 1.1+. As the added test shows, connecting to a server that doesn't support TLS 1.1+ will display a warning message with a link to our wiki, where we can guide people to configure their client to allow less secure connections.

Mads Kiilerich - - Load All Authors

File last commit:

r16913:f2719b38 default


                r29560:303e9300

default

Download file

             test-rename-after-merge.t
        
                    121 lines
            
             | 2.2 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-rename-after-merge.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      Issue746: renaming files brought by the second parent of a merge was

      broken.

      Create source repository:

        $ hg init t

        $ cd t

        $ echo a > a

        $ hg ci -Am a

        adding a

        $ cd ..

      Fork source repository:

        $ hg clone t t2

        updating to branch default

        1 files updated, 0 files merged, 0 files removed, 0 files unresolved

        $ cd t2

        $ echo b > b

        $ hg ci -Am b

        adding b

      Update source repository:

        $ cd ../t

        $ echo a >> a

        $ hg ci -m a2

      Merge repositories:

        $ hg pull ../t2

        pulling from ../t2

        searching for changes

        adding changesets

        adding manifests

        adding file changes

        added 1 changesets with 1 changes to 1 files (+1 heads)

        (run 'hg heads' to see heads, 'hg merge' to merge)

        $ hg merge

        1 files updated, 0 files merged, 0 files removed, 0 files unresolved

        (branch merge, don't forget to commit)

        $ hg st

        M b

      Rename b as c:

        $ hg mv b c

        $ hg st

        A c

        R b

      Rename back c as b:

        $ hg mv c b

        $ hg st

        M b

        $ cd ..

      Issue 1476: renaming a first parent file into another first parent

      file while none of them belong to the second parent was broken

        $ hg init repo1476

        $ cd repo1476

        $ echo a > a

        $ hg ci -Am adda

        adding a

        $ echo b1 > b1

        $ echo b2 > b2

        $ hg ci -Am changea

        adding b1

        adding b2

        $ hg up -C 0

        0 files updated, 0 files merged, 2 files removed, 0 files unresolved

        $ echo c1 > c1

        $ echo c2 > c2

        $ hg ci -Am addcandd

        adding c1

        adding c2

        created new head

      Merge heads:

        $ hg merge

        2 files updated, 0 files merged, 0 files removed, 0 files unresolved

        (branch merge, don't forget to commit)

        $ hg mv -Af c1 c2

      Commit issue 1476:

        $ hg ci -m merge

        $ hg log -r tip -C -v | grep copies

        copies:      c2 (c1)

        $ hg rollback

        repository tip rolled back to revision 2 (undo commit)

        working directory now based on revisions 2 and 1

        $ hg up -C .

        2 files updated, 0 files merged, 2 files removed, 0 files unresolved

      Merge heads again:

        $ hg merge

        2 files updated, 0 files merged, 0 files removed, 0 files unresolved

        (branch merge, don't forget to commit)

        $ hg mv -Af b1 b2

      Commit issue 1476 with a rename on the other side:

        $ hg ci -m merge

        $ hg log -r tip -C -v | grep copies

        copies:      b2 (b1)

        $ cd ..

	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

				Issue746: renaming files brought by the second parent of a merge was
				broken.

				Create source repository:

				$ hg init t
				$ cd t
				$ echo a > a
				$ hg ci -Am a
				adding a
				$ cd ..

				Fork source repository:

				$ hg clone t t2
				updating to branch default
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved
				$ cd t2
				$ echo b > b
				$ hg ci -Am b
				adding b

				Update source repository:

				$ cd ../t
				$ echo a >> a
				$ hg ci -m a2

				Merge repositories:

				$ hg pull ../t2
				pulling from ../t2
				searching for changes
				adding changesets
				adding manifests
				adding file changes
				added 1 changesets with 1 changes to 1 files (+1 heads)
				(run 'hg heads' to see heads, 'hg merge' to merge)

				$ hg merge
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ hg st
				M b

				Rename b as c:

				$ hg mv b c
				$ hg st
				A c
				R b

				Rename back c as b:

				$ hg mv c b
				$ hg st
				M b

				$ cd ..

				Issue 1476: renaming a first parent file into another first parent
				file while none of them belong to the second parent was broken

				$ hg init repo1476
				$ cd repo1476
				$ echo a > a
				$ hg ci -Am adda
				adding a
				$ echo b1 > b1
				$ echo b2 > b2
				$ hg ci -Am changea
				adding b1
				adding b2
				$ hg up -C 0
				0 files updated, 0 files merged, 2 files removed, 0 files unresolved
				$ echo c1 > c1
				$ echo c2 > c2
				$ hg ci -Am addcandd
				adding c1
				adding c2
				created new head

				Merge heads:

				$ hg merge
				2 files updated, 0 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ hg mv -Af c1 c2

				Commit issue 1476:

				$ hg ci -m merge

				$ hg log -r tip -C -v \| grep copies
				copies: c2 (c1)

				$ hg rollback
				repository tip rolled back to revision 2 (undo commit)
				working directory now based on revisions 2 and 1

				$ hg up -C .
				2 files updated, 0 files merged, 2 files removed, 0 files unresolved

				Merge heads again:

				$ hg merge
				2 files updated, 0 files merged, 0 files removed, 0 files unresolved
				(branch merge, don't forget to commit)

				$ hg mv -Af b1 b2

				Commit issue 1476 with a rename on the other side:

				$ hg ci -m merge

				$ hg log -r tip -C -v \| grep copies
				copies: b2 (b1)

				$ cd ..