--On Friday, October 05, 2007 9:03 AM +0000 andy.n.parker(a)unilever.com
wrote:
> Full_Name: Andrew N Parker
> Version: 2.3.38
> OS: RHEL 4.2 32 bit
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (194.60.106.5)
OpenLDAP 2.3.38 does not support BDB 4.6. Use a supported BDB release.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
ando(a)sys-net.it wrote:
> Full_Name: Pierangelo Masarati
> Version: HEAD/re24
> OS: irrelevant
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (131.175.154.35)
> Submitted by: ando
>
>
> There was an issue with mirror mode, which caused an endless replication loop
> when repeated, very close add/delete of the same object, like those performed by
> the slapd-addel tester tool, were performed in a multimaster environment using
> refreahAndPersist.
>
> Howard fixed this by letting syncrepl_entry() propagate the replication cookie,
> if available, so that modifications don't get sent back to the SID that
> generated them (please correct me if I got it wrong). The same issue is
> probably affecting cascaded syncrepl, but not delta-syncrepl.
Right, refreshAndPersist in a cascaded syncrepl would also be affected by the
patch, although so far there's no indication that this caused any actual problems.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Pierangelo Masarati
Version: HEAD/re24
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (131.175.154.35)
Submitted by: ando
There was an issue with mirror mode, which caused an endless replication loop
when repeated, very close add/delete of the same object, like those performed by
the slapd-addel tester tool, were performed in a multimaster environment using
refreahAndPersist.
Howard fixed this by letting syncrepl_entry() propagate the replication cookie,
if available, so that modifications don't get sent back to the SID that
generated them (please correct me if I got it wrong). The same issue is
probably affecting cascaded syncrepl, but not delta-syncrepl.
p.
hyc(a)symas.com wrote:
> Except that from ITS#5070 we always use hex for serial numbers now, so this
> would actually be
> {
> serialNumber '03'H,
> issuer rdnSequence:"email=ca(a)example.com,cn=example ca,o=example,st=xx,
> c=us"
> }
works for me... thanks.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
Howard Chu wrote:
> I.e., the sequence should be enclosed in double quotes. So your example should be
>
> {
> serialNumber 3,
> issuer rdnSequence:"email=ca(a)example.com,cn=example ca,o=example,st=xx,
> c=us"
> }
Except that from ITS#5070 we always use hex for serial numbers now, so this
would actually be
{
serialNumber '03'H,
issuer rdnSequence:"email=ca(a)example.com,cn=example ca,o=example,st=xx,
c=us"
}
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
ando(a)sys-net.it wrote:
> hyc(a)symas.com wrote:
>> Yes, it looks like we're using an invalid format for the issuer component.
>> Seems like using the GSER format is a bit harder to parse, since we have no
>> reliable indicator of where the rdnSequence ends. Any thoughts?
>
> In general, I agree. In this specific case, it ends at the end of the
> octetString :)
I take that back. Section 3.20 of RFC3641 says
>>>
3.20. Variant Encodings
The values of some named complex ASN.1 types have special string
encodings. These special encodings are always used instead of the
encoding that would otherwise apply based on the ASN.1 type
definition.
VariantEncoding = RDNSequenceValue /
RelativeDistinguishedNameValue /
ORAddressValue
A value of the RDNSequence type, i.e., a distinguished name, is
encoded according to the <RDNSequenceValue> rule, as a quoted LDAPDN
character string. The character string is first derived according to
the <distinguishedName> rule in Section 3 of RFC 2253 [5], and then
encoded as if it were a UTF8String value, i.e., between double quotes
with any embedded double quotes escaped by being repeated.
<<<
I.e., the sequence should be enclosed in double quotes. So your example should be
{
serialNumber 3,
issuer rdnSequence:"email=ca(a)example.com,cn=example ca,o=example,st=xx,
c=us"
}
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
hyc(a)symas.com wrote:
> Yes, it looks like we're using an invalid format for the issuer component.
> Seems like using the GSER format is a bit harder to parse, since we have no
> reliable indicator of where the rdnSequence ends. Any thoughts?
In general, I agree. In this specific case, it ends at the end of the
octetString :)
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
Yes, it looks like we're using an invalid format for the issuer component.
Seems like using the GSER format is a bit harder to parse, since we have no
reliable indicator of where the rdnSequence ends. Any thoughts?
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Pierangelo Masarati
Version: HEAD/re24/re23
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (81.72.89.40)
Submitted by: ando
I found out that most of the issues I was seeing with syncrepl were a (nasty)
side-effect of the fact that slapo-rwm does not play well with UUID-syntax attrs
in search filters; unfortunately, syncrepl heavily exploits searching with
equality filters on entryUUID... fixed.
PS: sorry for the noise.