Some comments on this approach. It appears that you are trying
to correct a fundalmental problem in the underlying Kerberos
gss implementation.
On the server/acceptor side, if the gss_acquire_cred is called
with a GSS_C_NO_NAME, (or the gss_init_sec_context is not passwd
a crede_handle) then any
Douglas E Engert [EMAIL PROTECTED] writes:
Some comments on this approach. It appears that you are trying to
correct a fundalmental problem in the underlying Kerberos gss
implementation.
Well, actually, I'm doing GSSAPI cargo cult programming, but your way of
phrasing that sounds so much
Is MIT implementation only accepting non-minimal-length integers or it is
also generating non-minimal-length integers?
If it is generating non-minimal-length integers then that should be
corrected.
Salil As per the ASN encoding specifications, all integers must
Salil be encoded in
Hola..
I'm defining some documentation of this two terms (principal name and
realm). And I'm wondering if there is any special characters allowed to
define a principal name and realm name ?
I know that the valid characters are case sensitive and include all
alpha-numeric characters (a-z,
On Jun 27, 2006, at 18:01, Julio Cesar Parra/Mexico/IBM wrote:
Hola..
I'm defining some documentation of this two terms (principal name and
realm). And I'm wondering if there is any special characters
allowed to
define a principal name and realm name ?
Oh, what a fun question, one we've
To: kerberos@mit.edu
Subject: Is there a list of characters allowed to define a principal name and
realm?
From: Julio Cesar Parra/Mexico/IBM [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Date: Tue, 27 Jun 2006 17:01:13 -0500
Hola..
I'm defining some documentation of this two
On Tue, 27 Jun 2006 18:38:47 -0400, Ken Raeburn wrote:
For portability, I think the right answer is if you use anything outside
of US-ASCII minus control characters, you're likely to hurt yourself or
your users, and RFC 4120's specifications and recommendations are based
on that. We intend
On Jun 27, 2006, at 19:29, Jeremy Allison wrote:
On Tue, 27 Jun 2006 18:38:47 -0400, Ken Raeburn wrote:
For portability, I think the right answer is if you use anything
outside
of US-ASCII minus control characters, you're likely to hurt
yourself or
your users, and RFC 4120's