|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Mail-followup-to: rt@krbdev.mit.edu mail-copies-to: never From: "Greg Hudson via RT" <rt-comment@krbdev.MIT.EDU> In-Reply-To: <rt-2659@krbdev.mit.edu> Message-ID: <rt-2659-32982.13.0241224032571@krbdev.mit.edu> To: "'AdminCc of krbdev.mit.edu Ticket #2659'":;"'AdminCc of krbdev.mit.edu Ticket #2659'":;@MIT.EDU Date: Thu, 1 Jul 2010 14:55:09 -0400 (EDT) Reply-To: rt-comment@krbdev.MIT.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: krb5-bugs-bounces@mit.edu As of r24147, it is possible for callers to use libgssrpc with IPv6 sockets provided that they: * Create and connect/bind their own sockets. * Only use TCP. * Do not query the addresses of client or server objects. That's enough to get kadmin working, as noted in #6746. There's no fundamental reason why UDP could not also be supported, but allowing the portmapper to be used might be difficult. As I understand it, our libgssrpc is based on Sun's (now Oracle's) ONC RPC. That API was updated to work with non-IPv4 transports and is now called TIRPC. TIRPC has been incorporated into libc on the *BSD platforms and has also been ported to Linux (though not incorporated into glibc). Our current understanding is that TIRPC code has been made available under two licenses: the SISSL and (via OpenSolaris) the CDDL. Neither is believed to be GPL-compatible. We are not aware of any implementations of TIRPC which are not derived from Sun/Oracle's code. We have made a request for the relevant parts of OpenSolaris to be relicensed under a BSD-like license so we might adapt it for the krb5 tree. _______________________________________________ krb5-bugs mailing list krb5-bugs@mit.edu https://mailman.mit.edu/mailman/listinfo/krb5-bugs
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |