I'm sorry, there is an updated version of the patch:
ftp://ftp.openldap.org/incoming/jvcelak-20121031-update-moznss-load-certs-f…
The attached file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Jan Vcelak am authorized by Red Hat, my employer, to release this work under the following terms.
Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.
Rich Megginson wrote:
> On 10/03/2012 10:18 AM, Howard Chu wrote:
>> Thanks for your comments, Rich.
>>> Maybe we could use nss_compat_ossl to do the mapping of cipher names
>>> from openssl to moznss?
>>
>> That makes sense to me, although if as you say it hasn't been actively
>> maintained, that sounds like another problem. But certainly if other
>> apps are using it, then aren't they going to want new cipher suite
>> support too?
>>
> Yes, and imho nss_compat_ossl is the place to do this.
>
> But, would it be possible to update the cipher suite list in tls_m.c
> first, to bring it up to date, then work on updating the compat library?
I discussed this with Kurt; the Project's policy on issues like this in the
past has been not to commit any backward-compatibility fixes of this sort
until the real fix has already been released. I.e., we should wait until
nss_compat_ossl has been updated.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
On 10/27/2012 12:53 PM, Michael Ströder wrote:
> jsynacek(a)redhat.com wrote:
>> This patch updates the slapo-constraint testsuit. It adds additional tests for
>> any constraints using 'uri'. Furthermore, it improves testing of the 'restrict'
>> parameter.
>
> In my RE24 working tree:
>
> git apply --stat jsynacek-20121025-constraint-tests-update.patch
>
> Then I expected
> ./run -b hdb test064 to fail (without the patch in ITS#7418) but it returned
> "Test succeeded".
>
> Ciao, Michael.
>
I'm sorry, one hunk didn't apply correctly.
New URL:
ftp://ftp.openldap.org/incoming/jsynacek-20121029-constraint-tests-update.p…
All the tests should fail without the patch in ITS#7418.
Cheers,
--
Jan Synacek
Software Engineer, BaseOS team Brno, Red Hat
Full_Name: ben blewett
Version: 2.4.31
OS: ubuntu 12.10
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (216.176.19.106)
documentation in the admin guide and the man pages for setup of slapo-pcache
when using slapd-config [cn=config] seems to be a bit sparse. just wanted to
put this on the list if it's not already.
Upgrade? This ITS will be closed.
> No such option in OpenLDAP 2.4.23 as delivered with RHEL 6.
>
> man ldapsearch shows the only general option documented
> is nettimeout
>
> ??
>
> On 10/28/2012 3:45 PM, Pierangelo Masarati wrote:
>> Use ldapsearch -o ldif-wrap=no instead.
>>
>> p.
>>
>>> Full_Name:
>>> Version:
>>> OS:
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (96.228.233.77)
>>>
>>>
>>> RFC 2849 states:
>>>
>>> 2) Any non-empty line, including comment lines, in an LDIF file
>>> MAY be folded by inserting a line separator (SEP) and a
>>> SPACE.
>>> Folding MUST NOT occur before the first character of the
>>> line.
>>> In other words, folding a line into two lines, the first of
>>> which is empty, is not permitted. Any line that begins with
>>> a
>>> single space MUST be treated as a continuation of the
>>> previous
>>> (non-empty) line. When joining folded lines, exactly one
>>> space
>>> character at the beginning of each continued line must be
>>> discarded. Implementations SHOULD NOT fold lines in the
>>> middle
>>> of a multi-byte UTF-8 character.
>>>
>>> OpenLDAP (ldapsearch at least) has taken implemented that folding
>>> behavior for LDIF output.
>>>
>>> This causes trouble for anyone trying to use 'ldapsearch | grep
>>> <something>'
>>> for one simple example.
>>>
>>> Would you accept a patch to allow an option which disables line
>>> folding?
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>
--
Pierangelo Masarati
Associate Professor
Dipartimento di Ingegneria Aerospaziale
Politecnico di Milano
No such option in OpenLDAP 2.4.23 as delivered with RHEL 6.
man ldapsearch shows the only general option documented
is nettimeout
??
On 10/28/2012 3:45 PM, Pierangelo Masarati wrote:
> Use ldapsearch -o ldif-wrap=no instead.
>
> p.
>
>> Full_Name:
>> Version:
>> OS:
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (96.228.233.77)
>>
>>
>> RFC 2849 states:
>>
>> 2) Any non-empty line, including comment lines, in an LDIF file
>> MAY be folded by inserting a line separator (SEP) and a SPACE.
>> Folding MUST NOT occur before the first character of the line.
>> In other words, folding a line into two lines, the first of
>> which is empty, is not permitted. Any line that begins with a
>> single space MUST be treated as a continuation of the previous
>> (non-empty) line. When joining folded lines, exactly one space
>> character at the beginning of each continued line must be
>> discarded. Implementations SHOULD NOT fold lines in the middle
>> of a multi-byte UTF-8 character.
>>
>> OpenLDAP (ldapsearch at least) has taken implemented that folding
>> behavior for LDIF output.
>>
>> This causes trouble for anyone trying to use 'ldapsearch | grep
>> <something>'
>> for one simple example.
>>
>> Would you accept a patch to allow an option which disables line folding?
>>
>>
>>
>>
>
>
Use ldapsearch -o ldif-wrap=no instead.
p.
> Full_Name:
> Version:
> OS:
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (96.228.233.77)
>
>
> RFC 2849 states:
>
> 2) Any non-empty line, including comment lines, in an LDIF file
> MAY be folded by inserting a line separator (SEP) and a SPACE.
> Folding MUST NOT occur before the first character of the line.
> In other words, folding a line into two lines, the first of
> which is empty, is not permitted. Any line that begins with a
> single space MUST be treated as a continuation of the previous
> (non-empty) line. When joining folded lines, exactly one space
> character at the beginning of each continued line must be
> discarded. Implementations SHOULD NOT fold lines in the middle
> of a multi-byte UTF-8 character.
>
> OpenLDAP (ldapsearch at least) has taken implemented that folding
> behavior for LDIF output.
>
> This causes trouble for anyone trying to use 'ldapsearch | grep
> <something>'
> for one simple example.
>
> Would you accept a patch to allow an option which disables line folding?
>
>
>
>
--
Pierangelo Masarati
Associate Professor
Dipartimento di Ingegneria Aerospaziale
Politecnico di Milano
Full_Name:
Version:
OS:
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (96.228.233.77)
RFC 2849 states:
2) Any non-empty line, including comment lines, in an LDIF file
MAY be folded by inserting a line separator (SEP) and a SPACE.
Folding MUST NOT occur before the first character of the line.
In other words, folding a line into two lines, the first of
which is empty, is not permitted. Any line that begins with a
single space MUST be treated as a continuation of the previous
(non-empty) line. When joining folded lines, exactly one space
character at the beginning of each continued line must be
discarded. Implementations SHOULD NOT fold lines in the middle
of a multi-byte UTF-8 character.
OpenLDAP (ldapsearch at least) has taken implemented that folding
behavior for LDIF output.
This causes trouble for anyone trying to use 'ldapsearch | grep <something>'
for one simple example.
Would you accept a patch to allow an option which disables line folding?