##// END OF EJS Templates
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.

File last commit:

r20045:b3684fd2 default
r29560:303e9300 default
Show More
test-filecache.py.out
60 lines | 1.1 KiB | text/plain | TextLexer
/ tests / test-filecache.py.out
Idan Kamara
scmutil: introduce filecache...
r14928 basic:
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * neither file exists
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * neither file still exists
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * empty file x created
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * file x changed size
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * nothing changed with either file
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * file x changed inode
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * empty file y created
creating
* file y changed size
creating
* file y changed inode
creating
* both files changed inode
creating
Idan Kamara
scmutil: introduce filecache...
r14928
fakeuncacheable:
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * neither file exists
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * neither file still exists
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * empty file x created
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * file x changed size
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * nothing changed with either file
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * file x changed inode
Idan Kamara
scmutil: introduce filecache...
r14928 creating
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * empty file y created
creating
* file y changed size
creating
* file y changed inode
creating
* both files changed inode
creating
Idan Kamara
destroyed: keep the filecache in sync with __dict__ (issue3335) (issue3693) (issue3743)...
r18313 repository tip rolled back to revision -1 (undo commit)
working directory now based on revision -1
repository tip rolled back to revision -1 (undo commit)
working directory now based on revision -1
Idan Kamara
filecache: create an entry in _filecache when __set__ is called for a missing one...
r18316
setbeforeget:
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * neither file exists
Siddharth Agarwal
test-filecache.py: make setbeforeget test clearer...
r20040 string set externally
Siddharth Agarwal
test-filecache.py: add markers to the output for each event...
r20041 * file x created
Idan Kamara
filecache: create an entry in _filecache when __set__ is called for a missing one...
r18316 creating
Siddharth Agarwal
test-filecache.py: make setbeforeget test clearer...
r20040 string from function
Siddharth Agarwal
scmutil.filecache: support watching over multiple files
r20045 * string set externally again
string 2 set externally
* file y created
creating
string from function