I tend to agree that it would be desirable for the kuser applications
to be console apps.
--Sam
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
On Tue, Feb 20, 2007 at 11:14:14PM -0500, Rodney M Dyer wrote:
At 10:24 PM 2/20/2007, Rodney M Dyer wrote:
The MIT people simply don't want you to be able to pipe in a password to
kinit via stdin, which is the right security practice (in security
circles), however they are rather flippant
On Tue, 20 Feb 2007, Christopher D. Clausen wrote:
Well, can't you check the exit error codes set by the program?
C:\kinit -kt test
kinit(v5): Cannot resolve network address for KDC in requested realm
while getting initial credentials
C:\echo %ERRORLEVEL%
1
Because that only tells you
On Tue, 20 Feb 2007, Christopher D. Clausen wrote:
I managed to redirect the password prompt:
(Not sure if this is a feature or a bug.)
C:\kinit cclausen 21 1kinit.txt
C:\cat kinit.txt
Password for [EMAIL PROTECTED]:
C:\
This is actually the same as doing this:
C:\kinit cclausen
On Tue, 20 Feb 2007, Rodney M Dyer wrote:
At 11:43 PM 2/19/2007, [EMAIL PROTECTED] wrote:
Is there a way to redirect stderr from kinit/klist to a file?
I think it is simply a bug in the prompter code. I saw this problem a few
years ago and was annoyed, and just worked without the error
[EMAIL PROTECTED] wrote:
Ok.. that's fine, but I'm not talking about re-directing stdin, I'm only
talking about re-directing stderr.
Please file a bug report to [EMAIL PROTECTED]
In principal I have no objection to treating the kuser utilities as
console applications that should never raise a
[EMAIL PROTECTED] wrote:
Is there a way to redirect stderr from kinit/klist to a file?
stdin and stderr cannot be redirected. they are used for
password prompting
Jeffrey Altman
Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
On Tue, 20 Feb 2007, Jeffrey Altman wrote:
[EMAIL PROTECTED] wrote:
Is there a way to redirect stderr from kinit/klist to a file?
stdin and stderr cannot be redirected. they are used for password
prompting
Hmmm but I'm not trying to redirect the password prompt... in fact,
kinit
[EMAIL PROTECTED] wrote:
On Tue, 20 Feb 2007, Jeffrey Altman wrote:
[EMAIL PROTECTED] wrote:
Is there a way to redirect stderr from kinit/klist to a file?
stdin and stderr cannot be redirected. they are used for password
prompting
Hmmm but I'm not trying to redirect the password
[EMAIL PROTECTED] wrote:
On Tue, 20 Feb 2007, Jeffrey Altman wrote:
[EMAIL PROTECTED] wrote:
Is there a way to redirect stderr from kinit/klist to a file?
stdin and stderr cannot be redirected. they are used for password
prompting
Hmmm but I'm not trying to redirect the password
At 10:24 PM 2/20/2007, Rodney M Dyer wrote:
The MIT people simply don't want you to be able to pipe in a password to
kinit via stdin, which is the right security practice (in security
circles), however they are rather flippant about it, because they allow it
under Unix. If they feel like
Is there a way to redirect stderr from kinit/klist to a file?
Running this from a DOS command prompt displays the output right in the
DOS command window (as I would expect):
C:\ klist -c foobar
klist: No credentials cache found (ticket cache API:foobar)
But if I re-direct stderr to a
12 matches
Mail list logo
