Is domain joining necessary to support KCD for a reverse proxy

[Amit Thukral]

Hi,
We have a linux based product which is a reverse proxy web firewall for web
applications (hosted on servers behind the product).
Normal kerberos works fine for us which is for the clients trying to access
the applications located on webservers.
We want to enhance it for KCD, am little confused that whether domain
joining for this product is really required or not for KCD ?

Thanks! I
Amit

On Jun 18, 2015 9:46 PM, <krbdev-request at mit.edu> wrote:

> Send krbdev mailing list submissions to
>         krbdev at mit.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mailman.mit.edu/mailman/listinfo/krbdev
> or, via email, send a message with subject or body 'help' to
>         krbdev-request at mit.edu
>
> You can reach the person managing the list at
>         krbdev-owner at mit.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of krbdev digest..."
>
>
> Today's Topics:
>
>    1. memleak in gss_add_cred_with_password in krb 1.12.1 and
>       1.13.1 (Sorin Manolache)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Jun 2015 18:13:40 +0200
> From: Sorin Manolache <sorinm at gmail.com>
> Subject: memleak in gss_add_cred_with_password in krb 1.12.1 and
>         1.13.1
> To: krbdev at mit.edu
> Message-ID: <5582EE34.6070005 at gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hello,
>
> I think I've found a memory leak in gss_add_cred_with_password, in krb5
> 1.12.1 and 1.13.1.
>
> The gss_OID_set target_mechs in gss_add_cred_with_password
> (lib/gssapi/mechglue/g_acquire_cred_with_pw.c) is not released if the
> function returns GSS_S_COMPLETE.
>
> Sorin
>
>
> ------------------------------
>
> _______________________________________________
> krbdev mailing list
> krbdev at mit.edu
> https://mailman.mit.edu/mailman/listinfo/krbdev
>
>
> End of krbdev Digest, Vol 150, Issue 8
> **************************************
>