Skip to content

schannel: stop calling it "winssl"#3504

Closed
bagder wants to merge 1 commit intomasterfrom
bagder/Schannel-winssl
Closed

schannel: stop calling it "winssl"#3504
bagder wants to merge 1 commit intomasterfrom
bagder/Schannel-winssl

Conversation

@bagder
Copy link
Member

@bagder bagder commented Jan 29, 2019

Stick to "Schannel" everywhere. The configure option --with-winssl is
kept to allow existing builds to work but a new --enable-schannel is
added as an alias.

@bagder bagder added the TLS label Jan 29, 2019
Stick to "Schannel" everywhere. The configure option --with-winssl is
kept to allow existing builds to work but --with-schannel is added as an
alias.
@bagder bagder force-pushed the bagder/Schannel-winssl branch from 5204ba9 to 48f8b7d Compare January 29, 2019 09:28
@danielgustafsson
Copy link
Member

danielgustafsson commented Jan 29, 2019 via email

@bagder
Copy link
Member Author

bagder commented Jan 29, 2019

should we do the same for Apple Secure Transport and move away from darwinssl?

I think so, yes. I think we're the odd ones here using these names and I think users and people in general will understand our terms better if we use the more appropriate and established names.

Darwinssl is slightly more engraved in curl though.

CURLSSLBACKEND_DARWINSSL is exposed in the API so we can just rename that, but we can add an alias. It is also the name used for the backend internally so when setting CURL_SSL_BACKEND that's the name to use. Possibly something else.

@danielgustafsson
Copy link
Member

danielgustafsson commented Jan 29, 2019 via email

@nickzman
Copy link
Member

nickzman commented Jan 30, 2019

I, too, would like to call it Secure Transport. The reason why it was called "DarwinSSL" is because Yang thought "Secure Transport" was too generic a name, but that's what Apple calls it, and no one else uses that name. At the time, I just went with the flow.

@bagder bagder closed this in 180501c Feb 1, 2019
@bagder bagder deleted the bagder/Schannel-winssl branch February 1, 2019 07:21
@lock lock bot locked as resolved and limited conversation to collaborators May 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Development

Successfully merging this pull request may close these issues.

4 participants