upstream/mercurial-mirror Files · tests/helpers-testrepo.sh

sslutil: print a warning when using TLS 1.0 on legacy Python...

sslutil: print a warning when using TLS 1.0 on legacy Python Mercurial now requires TLS 1.1+ when TLS 1.1+ is supported by the client. Since we made the decision to require TLS 1.1+ when running with modern Python versions, it makes sense to do something for legacy Python versions that only support TLS 1.0. Feature parity would be to prevent TLS 1.0 connections out of the box and require a config option to enable them. However, this is extremely user hostile since Mercurial wouldn't talk to https:// by default in these installations! I can easily see how someone would do something foolish like use "--insecure" instead - and that would be worse than allowing TLS 1.0! This patch takes the compromise position of printing a warning when performing TLS 1.0 connections when running on old Python versions. While this warning is no more annoying than the CA certificate / fingerprint warnings in Mercurial 3.8, we provide a config option to disable the warning because to many people upgrading Python to make the warning go away is not an available recourse (unlike pinning fingerprints is for the CA warning). The warning appears as optional output in a lot of tests.

timeless - - Load All Authors

File last commit:

r29219:3c9066ed default


                r29561:1a782fab

default

Download file

             helpers-testrepo.sh
        
                    19 lines
            
             | 678 B
            
                | application/x-sh
            
             |
                BashLexer
            
             / tests / helpers-testrepo.sh
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      # The test-repo is a live hg repository which may have evolution

      # markers created, e.g. when a ~/.hgrc enabled evolution.

      #

      # Tests are run using a custom HGRCPATH, which do not

      # enable evolution markers by default.

      #

      # If test-repo includes evolution markers, and we do not

      # enable evolution markers, hg will occasionally complain

      # when it notices them, which disrupts tests resulting in

      # sporadic failures.

      #

      # Since we aren't performing any write operations on the

      # test-repo, there's no harm in telling hg that we support

      # evolution markers, which is what the following lines

      # for the hgrc file do:

      cat >> $HGRCPATH << EOF

      [experimental]

      evolution=createmarkers

      EOF

	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

				# The test-repo is a live hg repository which may have evolution
				# markers created, e.g. when a ~/.hgrc enabled evolution.
				#
				# Tests are run using a custom HGRCPATH, which do not
				# enable evolution markers by default.
				#
				# If test-repo includes evolution markers, and we do not
				# enable evolution markers, hg will occasionally complain
				# when it notices them, which disrupts tests resulting in
				# sporadic failures.
				#
				# Since we aren't performing any write operations on the
				# test-repo, there's no harm in telling hg that we support
				# evolution markers, which is what the following lines
				# for the hgrc file do:
				cat >> $HGRCPATH << EOF
				[experimental]
				evolution=createmarkers
				EOF