Hi Steve,
Am 2014-11-16 um 00:23 schrieb Steve Holme:
On Sat, 15 Nov 2014, Michael Osipov wrote: [...]
If you take another close look, you'll see that gss_seal is used
and this is exactly the same as a SASL QOP which I told you about
recently.
Reading the above RFC it did seem like there was
On Sun, Nov 16, 2014 at 12:19:26AM +, Steve Holme wrote:
However, if we were to remove it (as per my patch) is that such a hardship
especially as krb4 has gone - never (probably) to return? At the end of the
day the output you mentioned is purely textual and it saves having an usused
Dear friends,
As some of you are aware krb4 support was dropped from curl and libcurl in
7.33.
However, there have been a few references to this feature left around either
in source code or documentation - some of which I have been cleaning out or
marking as deprecated recently.
There is one
On Sat, Nov 15, 2014 at 03:43:09PM +, Steve Holme wrote:
The curl command line tool supports --krb LEVEL and in its usages sets the
CURLOPT_KRBLEVEL option in libcurl - but only if KRB4 support has been
detected if(curlinfo-features CURL_VERSION_KERBEROS4) in
tool_getparam.c:696.
I
On Sat, 15 Nov 2014, Dan Fandrich wrote:
I have prepared a patch to remove this (see attached), however, from
reading the libcurl code (security.c) and associated comments it seems
more of a generic Kerberos option. Does anyone know if it is used
for Kerberos 5 at all?
I don't know
On Sat, Nov 15, 2014 at 05:57:19PM +, Steve Holme wrote:
On Sat, 15 Nov 2014, Dan Fandrich wrote:
I have prepared a patch to remove this (see attached), however, from
reading the libcurl code (security.c) and associated comments it seems
more of a generic Kerberos option. Does
Am 2014-11-15 um 17:10 schrieb Dan Fandrich:
On Sat, Nov 15, 2014 at 03:43:09PM +, Steve Holme wrote:
The curl command line tool supports --krb LEVEL and in its usages sets the
CURLOPT_KRBLEVEL option in libcurl - but only if KRB4 support has been
detected if(curlinfo-features
Am 2014-11-15 um 16:43 schrieb Steve Holme:
Dear friends,
As some of you are aware krb4 support was dropped from curl and libcurl in
7.33.
However, there have been a few references to this feature left around either
in source code or documentation - some of which I have been cleaning out or
On Sat, 15 Nov 2014, Dan Fandrich wrote:
From a curl command line point of view my patch really doesn't do anything
different as the current code checks for the presence of
CURL_VERSION_KERBEROS4 which won't be there (when = 7.33.0 ).
The difference is curl aborting because of an unknown
On Sat, 15 Nov 2014, Michael Osipov wrote:
I have prepared a patch to remove this (see attached), however, from
reading the libcurl code (security.c) and associated comments it seems
more of a generic Kerberos option. Does anyone know if it is used
for Kerberos 5 at all?
It isn't,
On Sat, Nov 15, 2014 at 10:37:11PM +, Steve Holme wrote:
On Sat, 15 Nov 2014, Dan Fandrich wrote:
From a curl command line point of view my patch really doesn't do anything
different as the current code checks for the presence of
CURL_VERSION_KERBEROS4 which won't be there (when =
On Sat, Nov 15, 2014 at 09:25:32PM +0100, Michael Osipov wrote:
There is no such thing as --krb 5. If you take a look at the man
page, you'll see that you are allowed to pass: The level must be
entered and should be one of 'clear', 'safe', 'confidential', or
'private'.
Ok, it doesn't matter
On Sat, 15 Nov 2014, Dan Fandrich wrote:
I though you were removing support of the option from the curl tool, in which
case it
work abort with curl: option --krb: is unknown.
Ultimately I was trying to determine if this option is used and whether I need
to support it in the SASL Kerberos 5
13 matches
Mail list logo
