> I think we all agreed that the best API approach was to move just the
> gss_name_t around between the processes, but I was told that there's no
> support yet for importing composite names (due to a missing OID for the
> GSS_C_NT_EXPORT_NAME_COMPOSITE name type?)
Yes, you can export them now (gss_export_name_composite()) but you can't import them, because IANA has not assigned an OID for GSS_C_NT_EXPORT_NAME_COMPOSITE, and I didn't want to implement a non-standard OID in MIT or Heimdal.
> So my question is: how does this get fixed? Does somebody just have to
> write an I-D to propose this for standardization?
https://datatracker.ietf.org/doc/draft-ietf-kitten-gssapi-naming-exts/
7.6
The OID for GSS_C_NT_COMPOSITE_EXPORT is <TBD>.
Sam understands more about the IETF process than I. I believe it's possible to get an OID before the draft becomes an RFC. But we'd still have to wait for MIT/Heimdal to ship conforming implementations.
-- Luke
|