[17419] in Kerberos_V5_Development
Re: Announcement: Android Kerberos Port with CyaSSL Embedded SSL
daemon@ATHENA.MIT.EDU (Sam Hartman)
Mon Nov 21 15:49:58 2011
From: Sam Hartman <hartmans@mit.edu>
To: Chris Conlon <conlon@yassl.com>
Date: Mon, 21 Nov 2011 15:49:53 -0500
In-Reply-To: <EB169EF1-54B0-4667-9BC5-50568CCF6128@yassl.com> (Chris Conlon's
message of "Tue, 15 Nov 2011 14:10:16 -0700")
Message-ID: <tslty5xgpzi.fsf@mit.edu>
MIME-Version: 1.0
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
I think it's important that if provided the GSS-API comply with the
org.ietf.jgss API. I don't think it matters much whether you port
something that can backend into a native API or you generate your own.
I don't know if swig can generate something that actually complies with
the Java GSS bindings.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
