[36469] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Canonicalisation in kfw-4.0?

daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Mon Sep 15 09:58:19 2014

Date: Mon, 15 Sep 2014 09:58:00 -0400 (EDT)
From: Benjamin Kaduk <kaduk@mit.edu>
To: Rick van Rein <rick@openfortress.nl>
In-Reply-To: <E7838E23-DB1A-44E6-B0FF-D3F9B8B650A6@openfortress.nl>
Message-ID: <alpine.GSO.1.10.1409150956300.21571@multics.mit.edu>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="-559023410-699573626-1410789480=:21571"
Cc: "<kerberos@mit.edu>" <kerberos@mit.edu>
Errors-To: kerberos-bounces@mit.edu

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-699573626-1410789480=:21571
Content-Type: TEXT/PLAIN; charset=windows-1252
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Sun, 14 Sep 2014, Rick van Rein wrote:

> Hello Benjamin,
>
> >> Am I correct that the kfw-4.0 GUI does not support a Canonicalisation
> >> option for the principal name?
> >
> > I'm not sure I understand the question correctly.  Are you asking about
> > RFC 6806 name canonicalization, as used for (e.g.) enterprise principal
> > names?
>
> Yes, that=92s what I meant.  It is not present in the kfw4 GUI, is it?

There is no support for enterprise principal names in the KfW 4.0 GUI,
correct.  kinit.exe /E should work as on Unix, though.

Can you say something about your usage scenario for enterprise principal
names?  If it is sufficiently generic, we might consider adding GUI
functionality in a future release.

-Ben
---559023410-699573626-1410789480=:21571
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

---559023410-699573626-1410789480=:21571--

home help back first fref pref prev next nref lref last post