On Thu, Jul 15, 2010 at 08:14:33AM -0700, Jeremy Chadwick wrote:
> Before I get started, I should note that the system I'm testing on was
> built with the following two features in src.conf and make.conf;
> the lesser is for world, the lesser for world, respectively.
>
> /etc/src.conf:DEBU
On Wed, Jul 14, 2010 at 09:18:21PM +0200, Henrik /KaarPoSoft wrote:
> On Tue, Jul 13, 2010 at 10:10:25PM +0200, Henrik /KaarPoSoft wrote:
> >>I have a problem: ldapsearch results in "Segmentation fault" under
> >>openldap-2.4.23 with cyrus-sasl-2.1.23.
> >>[...]
>
> Jeremy Chadwick wrote:
> >If I
On Wed, Jul 14, 2010 at 09:18:21PM +0200, Henrik /KaarPoSoft wrote:
> On Tue, Jul 13, 2010 at 10:10:25PM +0200, Henrik /KaarPoSoft wrote:
> >>I have a problem: ldapsearch results in "Segmentation fault" under
> >>openldap-2.4.23 with cyrus-sasl-2.1.23.
> >>[...]
>
> Jeremy Chadwick wrote:
> >If I
George Mamalakis wrote:
Unfortunately I have no time this week. I will be able to look at it
and send you a quick howto for openldap/cyrus/heimdal on Saturday. If
somebody else is able to do it sooner, it would be great. Please,
install it on i386 image, since amd64 didn't seem to have any prob
Joerg Pulz wrote:
On Tue, 13 Jul 2010, Henrik /KaarPoSoft wrote:
Dear All,
I have a problem: ldapsearch results in "Segmentation fault" under
openldap-2.4.23 with cyrus-sasl-2.1.23.
[...]
Dear Henrik,
just a guess from my side.
You said, that you installed and configured Kerberos from p
On Tue, Jul 13, 2010 at 10:10:25PM +0200, Henrik /KaarPoSoft wrote:
I have a problem: ldapsearch results in "Segmentation fault" under
openldap-2.4.23 with cyrus-sasl-2.1.23.
[...]
Jeremy Chadwick wrote:
If I was to build a test box from scratch, can you tell me how to set up
all the nece
On Tue, 13 Jul 2010, Henrik /KaarPoSoft wrote:
Dear All,
I have a problem: ldapsearch results in "Segmentation fault" under
openldap-2.4.23 with cyrus-sasl-2.1.23.
A thread for similar issues was started by George Mamalakis back in february:
http://lists.freebsd.org/pipermail/freebsd-stable/
e issue got forgotten. The problem would not persist
in amd64, so I stopped looking it further myself. Whoever wants to
see more information on this issue, search the subject field of this
list for: openldap client GSSAPI authentication segfaults in
fbsd8stable i386
I hope that a remedy to this issu
t; >the same issue as cyrus-sasl - athough it doesn't seem to be
> >available as separate port.
> >
> >-Reko
>
> Hello guys,
>
> I am glad that somebody brought this issue back, since despite my
> last email regarding the same issue on 25/02/2010 saying that there
&g
omething wrong with the function gss_release_buffer(void *a, void *b),
the issue got forgotten. The problem would not persist in amd64, so I
stopped looking it further myself. Whoever wants to see more information
on this issue, search the subject field of this list for: openldap
client GSSAPI
I have a problem: ldapsearch results in "Segmentation fault" under
openldap-2.4.23 with cyrus-sasl-2.1.23
A thread for similar issues was started by George Mamalakis back in
february:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/055017.html
but I find no solution / conclusion f
On Tue, Jul 13, 2010 at 10:10:25PM +0200, Henrik /KaarPoSoft wrote:
> Dear All,
>
> I have a problem: ldapsearch results in "Segmentation fault" under
> openldap-2.4.23 with cyrus-sasl-2.1.23.
>
> A thread for similar issues was started by George Mamalakis back in
> february:
> http://lists.freeb
Dear All,
I have a problem: ldapsearch results in "Segmentation fault" under
openldap-2.4.23 with cyrus-sasl-2.1.23.
A thread for similar issues was started by George Mamalakis back in
february:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/055017.html
but I find no solutio
To sum things up.
By fixing my /etc/hosts to read as it should (this needs some work too,
the behavior with the 'wrong' /etc/hosts is unexpected), ldapwhoami
works fine IF (AND ONLY IF) someone kinits to a user principal;
otherwise it segfaults. My default binding method is GSSAPI, hence the
On 11/02/2010 20:45, George Mamalakis wrote:
4:
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Local error (-2)
additional info: SASL(-1): generic failure: GSSAPI Error:
Miscellaneous failure (see text) (unknown mech-code 2529638919 for
mech unknown)
which is very stran
On 17/02/2010 12:39, George Mamalakis wrote:
On 13/02/2010 00:23, George Mamalakis wrote:
On 12/2/2010 8:48 πμ, jhell wrote:
This is a lot of information to consume.
Lets start with this:
All of the machines in question are of some form of FreeBSD 8.
You enter gdb and very clearly it start
On 13/02/2010 00:23, George Mamalakis wrote:
On 12/2/2010 8:48 πμ, jhell wrote:
This is a lot of information to consume.
Lets start with this:
All of the machines in question are of some form of FreeBSD 8.
You enter gdb and very clearly it starts whining about a segfault &
libc.so.7
Did
On 12/2/2010 8:48 πμ, jhell wrote:
This is a lot of information to consume.
Lets start with this:
All of the machines in question are of some form of FreeBSD 8.
You enter gdb and very clearly it starts whining about a segfault &
libc.so.7
Did you happen to upgrade these clients & server f
On Thu, 11 Feb 2010 13:45, mamalos@ wrote:
Dear all,
I am facing many instabilities in FBSD8 with openldap-client and sasl
authentication (GSSAPI in particular). I have setup an openldap 2.4.1 server
with gssapi support (through cyrus-sasl-2.1.23) on a fbsd8-stable amd64
latest sources, in a
Dear all,
I am facing many instabilities in FBSD8 with openldap-client and sasl
authentication (GSSAPI in particular). I have setup an openldap 2.4.1
server with gssapi support (through cyrus-sasl-2.1.23) on a fbsd8-stable
amd64 latest sources, in a esxi host. In the same host I have setup two
20 matches
Mail list logo
