Hi Yang
On 27 June 2012 18:43, Yang Tse yangs...@gmail.com wrote:
[...]
For the Config_Literal voting:
[Config_Literal=SCHANNEL] option would result in configure option
being named --with-SCHANNEL, and for other build systems WITH_SCHANNEL
or ENABLE_SCHANNEL.
[Config_Literal=WINDOWS_SSL]
Hello SSPI hackers,
Can you please help out and see if you can figure out why NTLM over proxy with
SSPI is broken as claimed here:
http://curl.haxx.se/bug/view.cgi?id=3538625
--
/ daniel.haxx.se
---
List admin:
On Thu, Jun 28, 2012 at 11:29 AM, Michael Wood esiot...@gmail.com wrote:
I feel part 2 of the rules was not completely clear wrt. casing and
did not mention dashes vs. underscores.
True, It certainly was an unintended lack of specification of posted
rules.I actually noticed when trying to
Friends,
I've just got rid of the temporary compile-time SSL-backend check.
Commit message when initially pushed lacked the 'temporay' word, sorry
for that. It was only for debugging purposes and would have required
dummy definitions for other SSL 'backends', not only the Schannel one.
Thanks,
Hi everyone,
2012/6/28 Yang Tse yangs...@gmail.com:
Yes, yes. I'm certainly in favour of that. Although I want explicit
approval on this thread from Marc Hoersken in order to interpret his
proposal in this way, given that his proposal would be affected by
this.
Of course I would like the
On 28 June 2012 14:06, Marc Hoersken i...@marc-hoersken.de wrote:
Hi everyone,
2012/6/28 Yang Tse yangs...@gmail.com:
Yes, yes. I'm certainly in favour of that. Although I want explicit
approval on this thread from Marc Hoersken in order to interpret his
proposal in this way, given that his
2012/6/28 Michael Wood esiot...@gmail.com:
On 28 June 2012 14:06, Marc Hoersken i...@marc-hoersken.de wrote:
[Config_Literal=WINDOWS_SSL]
configure: --with-windows-ssl or --with-winssl (short form,
corresponding to other parameters)
other: WITH_WINDOWS_SSL or ENABLE_WINDOWS_SSL
I'm not sure
Hello everyone,
attached you will find two patches to fix the warnings I reported earlier.
Would be great if someone could do a second test and push afterwards.
Best regards,
Marc
0001-nss-Fixed-size_t-conversion-warnings.patch
Description: Binary data
Due to issue mentioned in thread
http://curl.haxx.se/mail/lib-2012-06/0387.html pointing out posted
rules missing specification of underscore and dash conversions, and in
order to make results fit better in each configuration scheme we have
now the following addendum to point 2 of initial rules:
I've already seen your previous post from 20 hours ago. Please be
patient it will be addressed shortly.
I am patient... I just thought that it would be a good idea to do the
patching myself..
---
List admin:
Am 27.06.2012 18:43, schrieb Yang Tse:
Hi friends,
Up to right now, we only have two messages proposing some string candidates:
http://curl.haxx.se/mail/lib-2012-06/0305.html
http://curl.haxx.se/mail/archive-2012-06/0044.html
When summed up and once duplicates are removed, this makes that for
Daniel Stenberg dan...@haxx.se wrote:
Can you please help out and see if you can figure out why NTLM over proxy
with SSPI is broken as claimed here:
http://curl.haxx.se/bug/view.cgi?id=3538625
I currently have no way of testing this. I hope others will help here.
--
-=[Yang]=-
Hi Yang,
your commit f1474db3600172804d6f79d30e1127c6c7efa066 enables
-Wstrict-aliasing=3 also for clang, but it seems that clang doesnt
understand this warning (at least not clang 2.8 and 3.0):
clang: warning: unknown warning option '-Wstrict-aliasing=3'; did you
mean '-Wstring-plus-int'?
On Thu, Jun 28, 2012 at 4:11 PM, Marc Hoersken i...@marc-hoersken.de wrote:
I am patient... I just thought that it would be a good idea to do the
patching myself..
Fine, thanks.
0001-nss-Fixed-size_t-conversion-warnings.patch merged and pushed.
Afterwards I had to include warnless.h in nss.c
I've got one more thing to propose before the freeze:
As I mentioned earlier, on Mac OS X, if an app attempts an SSL connection and
the connection fails due to trust issues, apps typically put up a window
showing the failed certificate and ask if the user wants to connect anyway. But
to get
Hi Gün,
Guenter li...@gknw.net wrote:
your commit f1474db3600172804d6f79d30e1127c6c7efa066 enables
-Wstrict-aliasing=3 also for clang, but it seems that clang doesnt
understand this warning (at least not clang 2.8 and 3.0):
It seems I got fooled by existing comment in line 859 of
How would I find out if CURLOPT_TCP_KEEPALIVE is supported on my
platform (Windows)?
So, there would be no solution if I am using a libcurl version prior to
7.25? I am trying to avoid
the pain of doing an upgrade. Another bit of advice I got was to
periodically send a NOOP
instruction to
I can confirm this issue in 7.25.0 and later using the curl command line tool
and the trial version of MS ISA server 2006 ( available here:
http://www.microsoft.com/en-us/download/details.aspx?id=15244 ).
Unfortunately, I'm a bit busy for the next couple weeks (damn work getting in
the way
I am trying to build libcurl version 7.26 for Windows with OpenSSL support.
I was able to build it successfully without OpenSSL. When I add
WITH_SSL=dll
I get an error about missing rsa.h. I have downloaded the current
(1.0.1c) OpenSSL
source code and put in in the deps directory as
On Thu, Jun 28, 2012 at 09:33:44AM -0700, Jeff McKay wrote:
How would I find out if CURLOPT_TCP_KEEPALIVE is supported on my
platform (Windows)?
If you enable logging, you should see a message Failed to set
SO_KEEPALIVE on fd X if setting keepalive failed on a recent
libcurl.
So, there would
On Thu, 28 Jun 2012, Dan Fandrich wrote:
periodically send a NOOP instruction to the ftp server on the control
channel, but I don't think I have this capability if libcurl is handling
the ftp transfer, correct?
Correct. Adding NOOP support on the ftp control channel has been suggested
in
On Wed, 27 Jun 2012, Fabian Keil wrote:
I like the behaviour tested in 287 useful and would miss not being able to
send custom HTTP headers in CONNECT requests with curl.
I wouldn't mind if I had to use a separate option for this, though. In fact
I would consider this an improvement, as it
Hi friends,
[STEP 1] of this process has resulted in the following non redundant
candidate lists.
Three candidates for the [STEP 2] Version_Literal voting:
[Version_Literal=SSL-Windows-native]
[Version_Literal=Schannel]
[Version_Literal=WinSSL]
Three candidates for the [STEP 2] Config_Literal
My four votes...
[Version_Literal=Schannel]
[Version_Literal=WinSSL]
[Config_Literal=schannel]
[Config_Literal=winssl]
--
-=[Yang]=-
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:
My four votes:
[Version_Literal=Schannel]
[Version_Literal=WinSSL]
[Config_Literal=schannel]
[Config_Literal=winssl]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
25 matches
Mail list logo