krb5-libs/1022: accept_sec_context() specifies principal to rd_req()
Nicolas.Williams at ubsw.com
Mon Apr 8 16:12:01 EDT 2002
Why not use the default credential, GSS_C_NO_CREDENTIAL and then inquire
the context for the acceptor name?
The mechanism should support such behaviour.
Alternatively, is there a way to acquire a default acceptor credential
and then add all the available acceptor credentials to the first one?
On Mon, Apr 08, 2002 at 12:03:28PM -0700, Donn Cave wrote:
> It turns out that we were able to solve our particular problem at our
> site more easily in ftpd itself, by resolving the DNS name more accurately
> as I suggested in the very next bug, krb5-appl/1023. If that could be done,
> then I'd have no stake in this issue. In any case it isn't as important
> as the GSS_C_NO_CHANNEL_BINDING support that Jeffrey Altman submitted some
> time back for this file.
> In principle, though, I don't see this as throwing away information.
> The information in question is "who did I authenticate as", and that
> is available in the context via gss_inquire_context(). (I think,
> haven't verified that.) The problem is that currently, krb5_rd_req()
> goes on to turn this information into policy, at a level that's not
> accessible to the application. Like telnetd (which I believe checks
> principal name minus instance), ftpd could enforce its own policy in
> this matter, but it has to get past gss_accept_sec_context() first.
> Donn Cave, University Computing Services, University of Washington
> donn at u.washington.edu
> krbdev mailing list krbdev at mit.edu
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
More information about the krbdev