Yes, it does logs a warning on using socklen_t :
"argument of type "socklen_t *" is incompatible with parameter of type "int
*".
On Mon, Apr 28, 2014 at 7:44 AM, Simo Sorce wrote:
> On Sun, 2014-04-27 at 11:47 -0400, Greg Hudson wrote:
> > On 04/26/2014 02:59 PM, Vipul Mehta wrote:
> > > As e
Yes, the TGT is passed directly by the host.
Please read the section "Messages in the Forwarding Process" here :
http://technet.microsoft.com/en-us/library/4a1daa3e-b45c-44ea-a0b6-fe8910f92f28
It explains the steps clearly with the diagram.
On Sat, Apr 26, 2014 at 3:34 AM, Ben H wrote:
> That
Is your requirement to have the same certificate valid for two Kerberos realms
that are "equivalent" (An AD and a MIT/Heimdahl Kerberos realm)?
I worked with this a while ago (2010) issuing certificates from an
AD-integrated AD-CS certificate server:
Active Directory and MIT Kerberos use
Hi All,
I have Windows AD (2008) infrastructure. I created corresponding krb5.conf,
built the Krb source code, and now able to get TGT for that user on my
Linux machine using kinit.
My requirement is to setup PKINIT authentication on client-side (Linux)
with AD.
I have two choices:
1. Generate th
Greg Hudson writes:
> I'm not immediately sure how to write the autoconf test, though. My
> hope is that passing socklen_t * as the final getsockopt argument
> generates a warning on HPUX (perhaps you can verify this), and we can
> use that to distinguish. But AC_COMPILE_IFELSE doesn't appear t
