SSL - TLS 1.0 Disabled
Moderator: SourceGear
-
- Posts: 4
- Joined: Fri Mar 03, 2017 10:00 am
SSL - TLS 1.0 Disabled
Hello
I been running into problems with vault and SSL connections since I turned off TLS 1.0 support. (This was required of me since the server is hosted public web, and TLS 1.0 is no longer considered secure enough). This is known to cause problems in older versions of Dot.Net Framework.
I know I had to adjust the System.Net.ServicePointManager.SecurityProtocol to force it to use TLS 1.2 in my own applications. The last time I checked vault was build using 3.5 version of the framework, which doesn't support TLS 1.2. This is what I think is causing my problems.
What is the chance I can get a build, using Dot.Net 4.62 with TLS 1.2 support for 9.X release including the deploy power toy?
Just a reference.
http://blogs.perficient.com/microsoft/2 ... t-support/
I been running into problems with vault and SSL connections since I turned off TLS 1.0 support. (This was required of me since the server is hosted public web, and TLS 1.0 is no longer considered secure enough). This is known to cause problems in older versions of Dot.Net Framework.
I know I had to adjust the System.Net.ServicePointManager.SecurityProtocol to force it to use TLS 1.2 in my own applications. The last time I checked vault was build using 3.5 version of the framework, which doesn't support TLS 1.2. This is what I think is causing my problems.
What is the chance I can get a build, using Dot.Net 4.62 with TLS 1.2 support for 9.X release including the deploy power toy?
Just a reference.
http://blogs.perficient.com/microsoft/2 ... t-support/
Re: SSL - TLS 1.0 Disabled
We are currently working on a different GUI client for Vault 10 that will work with TLS 1.2 that will be available *after* the Vault 10 release. Vault 10 should be released in the next week or two.
Do you use Vault integrated with Visual Studio or only the Vault GUI client alone? The VS Enhanced Client in VS 2017 on Vault 10 works with TLS 1.2.
Do you use Vault integrated with Visual Studio or only the Vault GUI client alone? The VS Enhanced Client in VS 2017 on Vault 10 works with TLS 1.2.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
-
- Posts: 4
- Joined: Fri Mar 03, 2017 10:00 am
Re: SSL - TLS 1.0 Disabled
I am currently using Visual Studio 2015, with VS Enhanced Client. I have Visual Studio 2017 installed, but haven't switch over too it yet. I was giving it time to have any bug's shaken out of it to keep my down time to a min.
I also use the stand alone client for projects which are not Visual Studio based. Mostly word documents and manuals, which I need to track changes to over time.
I can wait a week or two easy enough, for the new release, if it supports TLS 1.2.
Thanks.
I also use the stand alone client for projects which are not Visual Studio based. Mostly word documents and manuals, which I need to track changes to over time.
I can wait a week or two easy enough, for the new release, if it supports TLS 1.2.
Thanks.
Re: SSL - TLS 1.0 Disabled
The client that can support TLS 1.2 will be after the Vault 10 release. It won't be finished in time for the release.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
-
- Posts: 4
- Joined: Fri Mar 03, 2017 10:00 am
Re: SSL - TLS 1.0 Disabled
Is there a change you need help testing this new GUI?
Re: SSL - TLS 1.0 Disabled
I'll keep your post in mind once we have it ready.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: SSL - TLS 1.0 Disabled
Owen Brady,
There is now an experimental (but supported) build of the Vault 10 GUI Client and Vault 10 Command Line Client which should allow you to enable only TLS 1.2 (disabling both TLS 1.0 / 1.1). Anyone interested in this build should contact SourceGear Technical Support with a link to this thread.
There is now an experimental (but supported) build of the Vault 10 GUI Client and Vault 10 Command Line Client which should allow you to enable only TLS 1.2 (disabling both TLS 1.0 / 1.1). Anyone interested in this build should contact SourceGear Technical Support with a link to this thread.
Jeff Clausius
SourceGear
SourceGear