Skip Menu |
 

History Show all quoted text — Show full headers
# Mon Sep 25 21:06:57 2006 <petesea@bigfoot.com> - Ticket created
From: petesea@bigfoot.com
Date: Mon, 25 Sep 2006 18:06:23 -0700 (Pacific Daylight Time)
Subject: Kfw: kinit doesn't accept windows path to keytab file
To: kfw-bugs@mit.edu
Download (untitled) / with headers
text/plain 507B
The kinit included with KfW doesn't seem to like a Windows path to a
keytab file. eg:

kinit -kt d:\my\path\to\keytab.file

It seems to be OK with a Windows path as long as it includes UNIX forward
(/) slashes, but it doesn't like a drive letter.

So... while this appears to work:

kinit -kt /my/path/to/keytab.file

this won't

kinit -kt d:/my/path/to/keytab.file

It would preferable if it accepted either forward (/) or backward (\)
slashes... but it really needs to accept a drive letter.
# Mon Sep 25 21:57:50 2006 jaltman (Jeffrey Altman) - Status changed from 'new' to 'resolved'
# Mon Sep 25 21:57:51 2006 jaltman (Jeffrey Altman) - Given to jaltman (Jeffrey Altman)
# Mon Sep 25 21:57:51 2006 jaltman (Jeffrey Altman) - Correspondence added
Download (untitled) / with headers
text/plain 317B
On all platforms the format for a keytab or a ccache is <TYPE>:<name>.

The proper format would be

FILE:d:\path\file

However, there is some magic glue that is supposed to work to
auto-detect a drive letter and guess from that it is a FILE: type. The
fix for this was pulled up to the release branch tonight.