[36017] in Kerberos
Re: TCP support for MIT Kerberos in HP-UX IA64
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Apr 7 11:08:05 2014
Message-ID: <5342BF43.4070506@mit.edu>
Date: Mon, 07 Apr 2014 11:07:47 -0400
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Vipul Mehta <vipulmehta.1989@gmail.com>, kerberos@mit.edu
In-Reply-To: <CAMeQEL9whEjrSbwSrFu-fFw6EMDOMk5xuO3rVvbhmJmRevBOcw@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On 04/07/2014 04:44 AM, Vipul Mehta wrote:
> I've narrowed down the problem.
>
> get_so_error() in sendto_kdc.c is returning error code 22 i.e. invalid
> argument on getsockopt() call.
>
> e = getsockopt(fd, SOL_SOCKET, SO_ERROR, &sockerr, &sockerrlen);
I did some searching and found:
http://lists.ibiblio.org/pipermail/freetds/2009q1/024226.html
http://www.postgresql.org/message-id/20101216174803.20b2b6db@pc09.procura.nl
It looks like HP-UX has an eight-byte socklen_t and a four-byte int, and
has two different versions of getsockopt(), one which expects a pointer
to int in the last parameter and one which expects a pointer to
socklen_t. Since we don't do anything in our build system to choose
"X/Open sockets," we probably get the first one.
If you change sockerrlen from socklen_t to int, does it start working?
I'm not sure if we can make a reasonable change to accomodate this if
so, but it would be good to know. There seems to have been some
confusion among various standards bodies over what type the optlen
parameter should point to.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
