KRB5_TRACE does not work on csh
Benjamin Kaduk
kaduk at mit.edu
Tue May 15 12:39:34 EDT 2018
On Tue, May 15, 2018 at 06:30:20PM +0200, Meike Stone wrote:
> Hello,
>
> maybe it is a stupid question and not a kerberos problem, but I can't
> get KRB5_TRACE working in a csh.
>
> On Bash it works as expected:
> export KRB5_TRACE=/dev/stdout
> echo $KRB5_TRACE
> /dev/stdout
>
> kinit meike at TEST.NET
> [22698] 1526401109.124271: Getting initial credentials for meike at TEST.NET
> [22698] 1526401109.124373: Sending request (144 bytes) to TEST.NET
> [22698] 1526401109.124457: Resolving hostname kdc1
> [22698] 1526401109.125178: Sending initial UDP request to dgram 192.168.1.100:88
> [22698] 1526401109.127098: Received answer (168 bytes) from dgram
> 192.168.1.100:88
> [22698] 1526401109.127909: Response was not from master KDC
> [22698] 1526401109.127930: Received error from KDC:
> -1765328359/Additional pre-authentication required
> [22698] 1526401109.127962: Processing preauth types: 16, 15, 19, 2
> [22698] 1526401109.127974: Selected etype info: etype aes256-cts, salt
> "TEST.NETmeike", params ""
> Password for meike at TEST.NET:
>
>
> on /bin/csh (a link to /bin/tcsh):
> setenv KRB5_TRACE /dev/stdout
> echo $KRB5_TRACE
> /dev/stdout
>
> kinit meike at TEST.NET
> Password for meike at TEST.NET:
>
>
> What is the problem here.
A guess, maybe there is special /dev/stdout handling involved. A
test using a file on an actual filesystem might be worth doing.
-Ben
More information about the Kerberos
mailing list