You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Atlassian Sourcetree Community.
I saw this link stating that bitbucket will turn off tls 1.0 and 1.1, and only use tls 1.2 starting december-1. https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01
So I upgraded sourcetree to the latest windows version, 3.0.8, and did a wireshark/tcpdump network capture. Most items are good tls 1.2, but when doing a Pull I do see some bad tls 1.0 entries. I'm on windows 10 pro ver 1703. Doing git from sourcetree Open->Terminal looks good ( GIT_CURL_VERBOSE=1 git ls-remote https://bitbucket.org/
uses 1.2). I'm using the built-in git of sourcetree.
So i'm concerned that something will break on that date. Can someone else confirm or deny what I saw, that some part of sourcetree is still using old tls 1.0 ?
Thanks. -Mike
Can you check what version of Git/Git Credential Manager you are using? see https://githubengineering.com/crypto-removal-notice/ for more information.
Sourcetree relies on the OS and should be just using TLS 1.2
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.