RE: Successfully build after 2 week struggle but...!

Hi Himanshu, “I successfully build windows x86 static libcurl library after struggling for two week. I'm new to building libraries but at the end it build. I build all dependencies statically like…” When you create a static library, you don’t have to worry about satisfying link dependencies

RE: schannel: next InitializeSecurityContext failed: Unknown error

This error message is actually pretty helpful: Trying https://www.hollywood-mal.de/ OK! Trying https://www.hollywood-mal.com/ FAIL: 35 schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - Die Sperrfunktion

RE: bug in schannel connection shutdown?

Marc, I took a look at this issue, but was unable to reproduce it myself. Even with a testcase provided by Mark, I still was not running into invalid memory access errors. Anyway, I created a patch that should avoid such issues by reference counting the credential handle and only allowing

RE: bug in schannel connection shutdown?

Frank, I'm using libcurl 7.27.0 with schannel on windows with MSVC2008, with https. ... If I then call curl_multi_cleanup() (when shutting down the entire program), I get accesses to free()d memory in schannel connection cleanup. I don't get such issues on linux with gnutls. The attached

RE: schannel_connect_step3 failures

Yang, Marc, et. All, I am worried that the flags change in your use cases. And I really don't like the idea of ignoring or just warning about non-matching flags. ISC_RET_CONFIDENTIALITY, ISC_RET_REPLAY_DETECT and ISC_RET_SEQUENCE_DETECT are pretty important to make sure that the SSL

RE: Unicode and NTLM

I doubt the change I made to be able to use the wide versions of functions (when UNICODE is defined) actually fixed anything besides compiling on systems that don't have an ANSI method available. (It'd be cool if it did though!). UTF-8 (which is passed around using char *) is still Unicode,

RE: further schannel improvements

improvements Hi there, 2012/6/20 Yang Tse yangs...@gmail.com: On Tue, Jun 19, 2012 at 5:22 AM, Yang Tse yangs...@gmail.com wrote: Relative to seven patch files posted Fri, Jun 15, 2012 at 2:24 AM by Mark Salisbury Mark... Patches 0002-* and 0004-* not yet integrated. All other five somewhat

2 fixes for schannel handshake

Hello, I have a couple more fixes for schannel SSL (see attached). 1. Process extra data buffer before returning from schannel_connect_step2. Without this change I've seen WinCE hang when schannel_connect_step2 returns and calls Curl_socket_ready. 2. If the encrypted handshake does not

RE: schannel and cacert verification

That's correct. Desktop windows has multiple cert stores - there is a machine store and a user store. The user store is what you see when you open up the Certificates view from IE. By default I think all code uses this store too. Mark -Original Message- From:

RE: after 7.26.0

Hi Marc, I'd like to test your native windows SSL work and try integrating some of what I've done on top of your work. What state is your work in currently? I recall one of the concerns was around write buffering. Does it make sense for you to send me a patch I can use to base work off? Did

RE: SSL/TLS support using Windows SSPI Schannel API

, Salisbury, Mark wrote: Thanks a lot for your contribution Mark. Let's combine these into something great! Yep, I am also for combining the solutions into something great! - write buffering implemented (though this is very easy to do).  it continues in a loop until all bytes are written

RE: SSL/TLS support using Windows SSPI Schannel API

[mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Marc Hoersken Sent: Monday, April 23, 2012 2:18 PM To: libcurl development Subject: Re: SSL/TLS support using Windows SSPI Schannel API 2012/4/23 Salisbury, Mark mark.salisb...@hp.com: Thinking about this a little bit more, I wonder if the SSL

RE: SSL/TLS support using Windows SSPI Schannel API

] On Behalf Of Daniel Stenberg Sent: Monday, April 23, 2012 2:49 PM To: libcurl development Subject: RE: SSL/TLS support using Windows SSPI Schannel API On Mon, 23 Apr 2012, Salisbury, Mark wrote: If you are asked to send 100 bytes, which is translated into 125 encrypted bytes, but only 30 bytes

RE: IP address support for no proxy feature

Subject: Re: IP address support for no proxy feature On Wed, Nov 11, 2009 at 10:12:13PM +, Salisbury, Mark wrote: With this change, it is possible to specify a no proxy list like 192.168.*, which would prevent the proxy from being used to access any host that begins with 192.168., for instance

RE: IP address support for no proxy feature

, November 11, 2009 9:18 PM To: libcurl development Subject: Re: IP address support for no proxy feature 2009/11/12, Salisbury, Mark wrote: Here's how I'd propose updating it: .IP CURLOPT_NOPROXY Pass a pointer to a zero terminated string. This should be a comma-separated list of hosts which do

IP address support for no proxy feature

Hello, I would like to submit a patch to allow IP addresses to be included in the list of no proxy hosts. Currently the no proxy logic allows for domain names to be specified. For instance, specifying hp.com will prevent the proxy from being used for accessing all hosts that end in hp.com.

RE: IP address support for no proxy feature

...@cool.haxx.se] On Behalf Of Yang Tse Sent: Wednesday, November 11, 2009 3:45 PM To: libcurl development Subject: Re: IP address support for no proxy feature 2009/11/11, Salisbury, Mark wrote: I would like to submit a patch to allow IP addresses to be included in the list of no proxy hosts