If the operating system supports TLS 1.2, then does it matter what version of .NET the apps are running in?
We have a 2016 webserver with only TLS 1.2 enabled (used IISCrypto tool to verify that). This webserver has 2 web apps both built in .NET 3.5 - one website and one wcf service.
I've done nothing but disable all other protocols so that only TLS 1.2 is available. I've also done the same in my browser settings. I then accessed both URLs in a browser and to my surprise there were no issues.
I then used Fiddler and Wireshark to confirm that the protocol used is TLS 1.2, so it appears that in this setup, with a 2016 webserver running .NET 3.5 apps that TLS 1.2 is supported - without me changing any of the .NET code.
I'm not unhappy with this result, but I am a little confused and hoped someone might clear this up for me, because my research indicated that the TLS protocol had to be supported in the application, either by adding code to earlier versions or upgrading to a version where TLS 1.2 is supported (like 4.6.1). Other options were to change registry settings - but I'm honestly not clear on whether the registry changes were in conjunction with the code changes/upgrades or not.
In my case, it seems that since the OS supports the protocol, then the app version does not matter. Has anybody else had this experience or am I missing something?
Thanks in advance!
codenewbie
operating-systems web tls wcf
add a comment |
We have a 2016 webserver with only TLS 1.2 enabled (used IISCrypto tool to verify that). This webserver has 2 web apps both built in .NET 3.5 - one website and one wcf service.
I've done nothing but disable all other protocols so that only TLS 1.2 is available. I've also done the same in my browser settings. I then accessed both URLs in a browser and to my surprise there were no issues.
I then used Fiddler and Wireshark to confirm that the protocol used is TLS 1.2, so it appears that in this setup, with a 2016 webserver running .NET 3.5 apps that TLS 1.2 is supported - without me changing any of the .NET code.
I'm not unhappy with this result, but I am a little confused and hoped someone might clear this up for me, because my research indicated that the TLS protocol had to be supported in the application, either by adding code to earlier versions or upgrading to a version where TLS 1.2 is supported (like 4.6.1). Other options were to change registry settings - but I'm honestly not clear on whether the registry changes were in conjunction with the code changes/upgrades or not.
In my case, it seems that since the OS supports the protocol, then the app version does not matter. Has anybody else had this experience or am I missing something?
Thanks in advance!
codenewbie
operating-systems web tls wcf
add a comment |
We have a 2016 webserver with only TLS 1.2 enabled (used IISCrypto tool to verify that). This webserver has 2 web apps both built in .NET 3.5 - one website and one wcf service.
I've done nothing but disable all other protocols so that only TLS 1.2 is available. I've also done the same in my browser settings. I then accessed both URLs in a browser and to my surprise there were no issues.
I then used Fiddler and Wireshark to confirm that the protocol used is TLS 1.2, so it appears that in this setup, with a 2016 webserver running .NET 3.5 apps that TLS 1.2 is supported - without me changing any of the .NET code.
I'm not unhappy with this result, but I am a little confused and hoped someone might clear this up for me, because my research indicated that the TLS protocol had to be supported in the application, either by adding code to earlier versions or upgrading to a version where TLS 1.2 is supported (like 4.6.1). Other options were to change registry settings - but I'm honestly not clear on whether the registry changes were in conjunction with the code changes/upgrades or not.
In my case, it seems that since the OS supports the protocol, then the app version does not matter. Has anybody else had this experience or am I missing something?
Thanks in advance!
codenewbie
operating-systems web tls wcf
We have a 2016 webserver with only TLS 1.2 enabled (used IISCrypto tool to verify that). This webserver has 2 web apps both built in .NET 3.5 - one website and one wcf service.
I've done nothing but disable all other protocols so that only TLS 1.2 is available. I've also done the same in my browser settings. I then accessed both URLs in a browser and to my surprise there were no issues.
I then used Fiddler and Wireshark to confirm that the protocol used is TLS 1.2, so it appears that in this setup, with a 2016 webserver running .NET 3.5 apps that TLS 1.2 is supported - without me changing any of the .NET code.
I'm not unhappy with this result, but I am a little confused and hoped someone might clear this up for me, because my research indicated that the TLS protocol had to be supported in the application, either by adding code to earlier versions or upgrading to a version where TLS 1.2 is supported (like 4.6.1). Other options were to change registry settings - but I'm honestly not clear on whether the registry changes were in conjunction with the code changes/upgrades or not.
In my case, it seems that since the OS supports the protocol, then the app version does not matter. Has anybody else had this experience or am I missing something?
Thanks in advance!
codenewbie
operating-systems web tls wcf
operating-systems web tls wcf
edited Jan 23 at 15:12
codenewbie
asked Jan 23 at 14:04
codenewbiecodenewbie
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397478%2fif-the-operating-system-supports-tls-1-2-then-does-it-matter-what-version-of-n%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397478%2fif-the-operating-system-supports-tls-1-2-then-does-it-matter-what-version-of-n%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown