On 2019-12-20 at 01:52:04, Keith Thompson wrote: > I've posted this on Stack Overflow > https://stackoverflow.com/q/59381061/827263 > but I haven't gotten any responses yet. > > When I install "Git for Windows" on Windows 10, the installation > wizard offers the choice of using either the OpenSSL library or the > "native Windows Secure Channel library". (Whether that's offered > seems to depend on what's available on the Windows 10 system.) > I believe this is referred to in the git sources as "schannel". > > Is there a way to configure git under Cygwin to use the native > Windows Secure Channel library? An ideal solution would be a > modification to my .gitconfig, but something that lets me build git > (and possibly curl) from source would also be good. See my Stack > Overflow question for more details, including some things that I > tried that didn't work. > > The problem I'm trying to solve: In my work environment, I can > use Cygwin git for local operations, but I have to use Windows git > for anything that talks to a remote (push, pull).I'd prefer to use > Cygwin git exclusively. I'm not 100% certain here, but I believe the answer is no. In order to use SChannel, you'll need to link against MSVCRT or a compatible runtime, but it's not possible to link against both that and Cygwin at the same time (probably because they both provide the same symbols). If your constraint is that you need to interact with the Windows certificate store or such, you could see if there's an OpenSSL or GnuTLS plugin that will do that for you and then build against that library or plugin. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204
Attachment:
signature.asc
Description: PGP signature