From: Steve Dickson <SteveD@redhat.com>
To: Kevin Coffman <kwc@umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] rpc.gssd: Don't supply the KDC with unsupported encryption types
Date: Tue, 25 Nov 2008 09:50:55 -0500 [thread overview]
Message-ID: <492C10CF.7040902@RedHat.com> (raw)
In-Reply-To: <4d569c330811111301r5948b77rd6125ffc0b950d88-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Kevin Coffman wrote:
> The AS-REQ (Authentication Service) is a request for a TGT (aka,
> Ticket-Granting-Ticket). This is a ticket issued by the KDC to a
> principal after verifying her identity (by verifying her password).
> This ticket is good for a period of time, allowing that principal to
> get tickets for other services, such as NFS, without having to use her
> password for every request. (Her password doesn't even go to the KDC
> for the AS-REQ. It is used to generate a key locally, which is used
> to encrypt something locally, which is sent in the AS-REQ.)
>
> This is the exchange your patch is limiting to only DES. That is unnecessary.
>
> The tickets for other services (like NFS) (aka Service Tickets) are
> obtained using a TGS-REQ (Ticket Granting Service). The TGT returned
> in the AS-REP is used to form the TGS request -- to verify it is still
> the same principal. This is where the code in gssd currently limits
> the encryption types that can be negotiated. We only want limit the
> encryption types for the session key in the NFS Service Ticket, not
> for all the service tickets obtained using that TGT. That is also why
> we DO NOT want to have
>
> default_tkt_enctypes = des-cbc-crc # Don't do this!
> default_tgs_enctypes = des-cbc-crc # Don't do this!
>
> in the /etc/krb5.conf file. Those limit all negotiations to only using DES.
>
>
> Also, it shouldn't matter if the KDC is a Linux KDC or a Solaris KDC.
> Modern versions of both KDCs support many encryption types besides
> DES. (As you can see above.)
>
> Now the Solaris NFS client and server can handle more encryption types
> than Linux at the moment. That is why it is important to limit the
> encryption types to only DES when creating the keytab entry for the
> nfs/<hostname>@REALM principal for Linux machines. That gives the KDC
> the information it needs to only issue a Service Ticket with only a
> DES session key to a Solaris NFS client when it is going to talk to a
> Linux NFS server.
>
> Hopefully this clears up a little without raising too many more questions!
It did... thanks!
It turns out there was bug in krb5-libs... Image that! 8-)
steved.
prev parent reply other threads:[~2008-11-25 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 16:40 [PATCH] rpc.gssd: Don't supply the KDC with unsupported encryption types Steve Dickson
[not found] ` <4919B57C.6050104-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-11-11 18:33 ` Kevin Coffman
[not found] ` <4d569c330811111033p70264b87r2463e8cb68b985e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-11 20:05 ` Steve Dickson
[not found] ` <4919E576.6050301-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-11-11 21:01 ` Kevin Coffman
[not found] ` <4d569c330811111301r5948b77rd6125ffc0b950d88-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-25 14:50 ` Steve Dickson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=492C10CF.7040902@RedHat.com \
--to=steved@redhat.com \
--cc=kwc@umich.edu \
--cc=linux-nfs@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.