unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Tomáš Čech" <sleep_walker@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31141@debbugs.gnu.org
Subject: [bug#31141] [PATCH] gnu: curl: Use mit-krb5 as GSSAPI implementation.
Date: Mon, 23 Apr 2018 16:53:45 +0200	[thread overview]
Message-ID: <20180423145345.xk4qeubkovrat37m@doom> (raw)
In-Reply-To: <87o9ia2i81.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]

Hello,

On Mon, Apr 23, 2018 at 02:57:34PM +0200, Ludovic Courtès wrote:
>Hello,
>
>Tomáš Čech <sleep_walker@gnu.org> skribis:
>
>> * gnu/packages/curl.scm (curl)[inputs]: Replace gss with mit-krb5.
>> [arguments]: Help configure with locating mit-krb5.
>> ---
>>  gnu/packages/curl.scm | 8 ++++++--
>>  1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/gnu/packages/curl.scm b/gnu/packages/curl.scm
>> index ae8b9600d..b5e1f52da 100644
>> --- a/gnu/packages/curl.scm
>> +++ b/gnu/packages/curl.scm
>> @@ -38,6 +38,7 @@
>>    #:use-module (gnu packages groff)
>>    #:use-module (gnu packages gsasl)
>>    #:use-module (gnu packages guile)
>> +  #:use-module (gnu packages kerberos)
>>    #:use-module (gnu packages libidn)
>>    #:use-module (gnu packages openldap)
>>    #:use-module (gnu packages perl)
>> @@ -62,9 +63,9 @@
>>     (outputs '("out"
>>                "doc"))                             ;1.2 MiB of man3 pages
>>     (inputs `(("gnutls" ,gnutls)
>> -             ("gss" ,gss)
>>               ("libidn" ,libidn)
>>               ("libssh2" ,libssh2)
>> +             ("mit-krb5" ,mit-krb5)
>
>Could you explain the rationale?  In general, if there’s a choice and no
>compelling reason to do otherwise, we try to favor the GNU
>implementation (in this case, GNU GSS) by default.

I am using curl against services with Kerberos authentication. Login
against authority server and obtain ticket proving that I am who I
am. I can use that ticket against services.

I'm not able to do the same with GNU GSS implementation. I might be
wrong but it didn't seem to allow me to do the same at least in the
shape we have it.

After this change it works for me as expected.

Best regards,

S_W

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-04-23 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 22:40 [bug#31141] [PATCH] gnu: curl: Use mit-krb5 as GSSAPI implementation Tomáš Čech
     [not found] ` <handler.31141.B.152357282812931.ack@debbugs.gnu.org>
2018-04-21 15:52   ` [bug#31141] Acknowledgement ([PATCH] gnu: curl: Use mit-krb5 as GSSAPI implementation.) Tomáš Čech
2018-04-21 16:10 ` [bug#31141] [PATCH] gnu: curl: Use mit-krb5 as GSSAPI implementation Tomáš Čech
2018-04-23 12:57   ` Ludovic Courtès
2018-04-23 14:53     ` Tomáš Čech [this message]
2018-04-23 15:24       ` Ludovic Courtès
2020-04-09 22:50 ` bug#31141: [PATCH] gnu: curl: Use mit-krb5 as GSSAPI Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180423145345.xk4qeubkovrat37m@doom \
    --to=sleep_walker@gnu.org \
    --cc=31141@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).