This is a cryptographically signed message in MIME format.
--------------ms000401080109060103090807
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
hyc(a)symas.com wrote:
> gabriel(a)gritsch-soft.com wrote:
>> would it be possible to support Apples "Common Crypto Services" instea=
d of
>> OpenSSL
> [..]
> But in general, it sounds like a bad idea. In light of Apple's now-infa=
mous=20
> "goto fail" bug=20
> http://www.zdnet.com/apples-goto-fail-tells-us-nothing-good-about-cuper=
tinos-software-delivery-process-7000027449/=20
> it would be poor practice to migrate away from a security package that =
is now=20
> receiving broad and in-depth scrutiny, to one that only has Apple's ass=
urances=20
> behind it. Also given Apple's success rate with security in general=20
> http://online.wsj.com/articles/apple-celebrity-accounts-compromised-by-=
very-targeted-attack-1409683803=20
> it seems like a poor choice.
Yes, I agree with these concerns - especially for OpenLDAP server deploym=
ents.
But there are some advantages using the OS platform's mainstream crypto l=
ib
for libldap to get access to the OS's own keyring (e.g. when using client=
certs).
E.g. I'd avoid libnss for OpenLDAP servers but PKCS#11 in libnss gives so=
me
better access to smartcards.
On the downside it's a pain to deal with all the LDAP_OPT_X_TLS_* options=
having no or different meaning/features for various crypto libs...
Ciao, Michael.
--------------ms000401080109060103090807
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFfzCC
BXswggNjoAMCAQICAwxOfTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu
ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMjEw
MDIyMDE3MDlaFw0xNDEwMDIyMDE3MDlaMD8xGDAWBgNVBAMUD01pY2hhZWwgU3Ry9mRlcjEj
MCEGCSqGSIb3DQEJARYUbWljaGFlbEBzdHJvZWRlci5jb20wggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQDo2SKth5GhtaDrCyfGtyUG+/hAAa/J52L0NFN4SSRvTtdGf9HfWwwd
NCtgae0TVGWk2lKDbXA9d5vmyIiRhuwxd90H6FLErhRBeB9G67qtw87E8WUoXt2DwPQEUTWV
hqHpPadlmgFw3+i3TGQQTe3O3W9MMMd4GJNhObem2VGRuCD37OXnzBksTcq0FPJgcWAhe3d/
0ItOkNWBqgq8Mf3p7WFBhaQ0a27BC/mKtH8fI3kPcS305imPRja69Msq3EwUZBc9ToVp6FRQ
NYKjfOBybDUzVkmRZl3H8xutQP2w8Zxb8m5f7Q1BfLLrIFScfYvIDgOERxTCd4lab8+/09XH
AgMBAAGjggFEMIIBQDAMBgNVHRMBAf8EAjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91
ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0Fj
ZXJ0Lm9yZzAOBgNVHQ8BAf8EBAMCA6gwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMC
BgorBgEEAYI3CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIG
CCsGAQUFBzABhhZodHRwOi8vb2NzcC5jYWNlcnQub3JnMDEGA1UdHwQqMCgwJqAkoCKGIGh0
dHA6Ly9jcmwuY2FjZXJ0Lm9yZy9yZXZva2UuY3JsMB8GA1UdEQQYMBaBFG1pY2hhZWxAc3Ry
b2VkZXIuY29tMA0GCSqGSIb3DQEBBQUAA4ICAQC9ouXq3p/bDWMM4tBKgD3tl4HY5H0eECl8
q9/nqk0UL6YeWkrCiQdrDtNPW7DcGqNYtzdgtzmyTr1GhiAX+igrOjdk/ge5NRcQOpONK/4b
zrmpQEcIUyxSSDKLWh211/kcFfxxLEiJ5teF4GL8Fc1qbrLP4+DCvJXWfYaaR5NLjZMqm2VP
yKTv3qpXWnGohiRkGTwS/11QM2XCfIGdRsQT9a8mO4m2fn2tGPp2TEIoCLrDDrbGVeDWaOWB
OIeTrp4wa3Q4OI6yCptJhEqKvjhV96IBRYgM76nTBqsqnDzwxExAyhhWiUS5DunRHOr/+NyF
pUpD4883RBLO0g9kUEGOhtZNF1u+8zEL0YgMGvifAom9JEklLOXZuqj0MThypKs/3d/OyOQb
4gURnu6oZwcKZ7LskytWnlRKUxF6o0A8grtmyKkqe14TS7cQbg0NTaIYXPkHR+dfFmb3uEqn
BBjvpJXFcEtWI2lQXC/ET+au991pK797ExBOmpQwjIn3SjiW80vw/UoL6DMvqY/6JhVhyNTP
MJ2W5AX5kc27DIbVtVGZs8J4AYhuNALJUq9N9Ka7rPRj3RcYDrfehDLOkM5iMnarpmtuOpLK
d1SvZhqj/0N/JWGIDpPSTkTFOPP6ZN9I9Rqyf+9NGqb2sjo4DkIiZcHxt735/GJLwus5KLBl
2DGCA6EwggOdAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93
d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8G
CSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMMTn0wCQYFKw4DAhoFAKCCAfUwGAYJ
KoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQwOTE5MTgwNTU3WjAj
BgkqhkiG9w0BCQQxFgQU1Bu1xvzhKvbO2C4/UC5TemE/oDIwbAYJKoZIhvcNAQkPMV8wXTAL
BglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAN
BggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBkQYJKwYBBAGCNxAEMYGD
MIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9y
ZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYS
c3VwcG9ydEBjYWNlcnQub3JnAgMMTn0wgZMGCyqGSIb3DQEJEAILMYGDoIGAMHkxEDAOBgNV
BAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZ
Q0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNl
cnQub3JnAgMMTn0wDQYJKoZIhvcNAQEBBQAEggEAJqysehHr7PX9CRn5k5b3vvjWRFBlZ267
gs5JFW7IRGga/8Qmd3OXCNpuAQIy1z3P92wxnT4jmRTtfym6t+dzicSqf7w6nORV76Y25I5d
uz3t4Imzhe422I2DekCHSEKsYjI6D81+jz/zdBJxzDyFPnoxamcBeIzAqpZisMQmc59aNLTO
JrzgCfsgzIJ5QkeLYIlyuCT2SgAtjdOakKSoVR36E++gfdMO9AjgJBHCuZsydYuMhiW40sDG
68+BthA3S5XqAf1S3xy3dPuVs08MhEnqPRcszILG2W/33LHcaxb1HuOpYfR44oxQfP01j9Wj
v19+j+fkiLDwpEWhIfZFJgAAAAAAAA==
--------------ms000401080109060103090807--
gabriel(a)gritsch-soft.com wrote:
> Full_Name: Gabriel Gritsch
> Version: 2.4.39
> OS: Mac OS X 10.9.5
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (46.234.244.166)
>
>
> Hi all,
>
> would it be possible to support Apples "Common Crypto Services" instead of
> OpenSSL because the OpenSSL-functions are marked as deprecated since OS X 10.7
> and produce a lot of warnings.
If someone submits a patch for this we will of course review and consider it.
But in general, it sounds like a bad idea. In light of Apple's now-infamous
"goto fail" bug
http://www.zdnet.com/apples-goto-fail-tells-us-nothing-good-about-cupertino…
it would be poor practice to migrate away from a security package that is now
receiving broad and in-depth scrutiny, to one that only has Apple's assurances
behind it. Also given Apple's success rate with security in general
http://online.wsj.com/articles/apple-celebrity-accounts-compromised-by-very…
it seems like a poor choice.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Gabriel Gritsch
Version: 2.4.39
OS: Mac OS X 10.9.5
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (46.234.244.166)
Hi all,
would it be possible to support Apples "Common Crypto Services" instead of
OpenSSL because the OpenSSL-functions are marked as deprecated since OS X 10.7
and produce a lot of warnings.
best regards
Gabriel
--001a1135fa9258513c0503605842
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I forgot to attach the error message. Here is it:
$ ./mtest7
map size is 10MB
new map size is 20MB
mtest7.c:69: mdb_put(txn, dbi, &key, &data, 0): MDB_BAD_TXN: Transaction
cannot recover - it must be aborted
Abortado (imagem do n=C3=BAcleo gravada)
2014-09-18 21:29 GMT-03:00 <openldap-its(a)openldap.org>:
>
> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
>
> Thanks for your report to the OpenLDAP Issue Tracking System. Your
> report has been assigned the tracking number ITS#7943.
>
> One of our support engineers will look at your report in due course.
> Note that this may take some time because our support engineers
> are volunteers. They only work on OpenLDAP when they have spare
> time.
>
> If you need to provide additional information in regards to your
> issue report, you may do so by replying to this message. Note that
> any mail sent to openldap-its(a)openldap.org with (ITS#7943)
> in the subject will automatically be attached to the issue report.
>
> mailto:openldap-its@openldap.org?subject=3D(ITS#7943)
>
> You may follow the progress of this report by loading the following
> URL in a web browser:
> http://www.OpenLDAP.org/its/index.cgi?findid=3D7943
>
> Please remember to retain your issue tracking number (ITS#7943)
> on any further messages you send to us regarding this report. If
> you don't then you'll just waste our time and yours because we
> won't be able to properly track the report.
>
> Please note that the Issue Tracking System is not intended to
> be used to seek help in the proper use of OpenLDAP Software.
> Such requests will be closed.
>
> OpenLDAP Software is user supported.
> http://www.OpenLDAP.org/support/
>
> --------------
> Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.
>
>
--=20
Carlo Pires
--001a1135fa9258513c0503605842
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I forgot to attach the error message. Here is it:<br>=
</div><br>$ ./mtest7<br><div>map size is 10MB<br>new map size is 20MB<br>mt=
est7.c:69: mdb_put(txn, dbi, &key, &data, 0): MDB_BAD_TXN: Transact=
ion cannot recover - it must be aborted<br>Abortado (imagem do n=C3=BAcleo =
gravada)<br><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">2014-09-18 21:29 GMT-03:00 <span dir=3D"ltr"><<a href=3D"mai=
lto:openldap-its@openldap.org" target=3D"_blank">openldap-its(a)openldap.org<=
/a>></span>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
*** THIS IS AN AUTOMATICALLY GENERATED REPLY ***<br>
<br>
Thanks for your report to the OpenLDAP Issue Tracking System.=C2=A0 Your<br=
>
report has been assigned the tracking number ITS#7943.<br>
<br>
One of our support engineers will look at your report in due course.<br>
Note that this may take some time because our support engineers<br>
are volunteers.=C2=A0 They only work on OpenLDAP when they have spare<br>
time.<br>
<br>
If you need to provide additional information in regards to your<br>
issue report, you may do so by replying to this message.=C2=A0 Note that<br=
>
any mail sent to <a href=3D"mailto:openldap-its@openldap.org">openldap-its@=
openldap.org</a> with (ITS#7943)<br>
in the subject will automatically be attached to the issue report.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 mailto:<a href=3D"mailto:openldap-its@openldap.=
org">openldap-its(a)openldap.org</a>?subject=3D(ITS#7943)<br>
<br>
You may follow the progress of this report by loading the following<br>
URL in a web browser:<br>
=C2=A0 =C2=A0 <a href=3D"http://www.OpenLDAP.org/its/index.cgi?findid=3D794=
3" target=3D"_blank">http://www.OpenLDAP.org/its/index.cgi?findid=3D7943</a=
><br>
<br>
Please remember to retain your issue tracking number (ITS#7943)<br>
on any further messages you send to us regarding this report.=C2=A0 If<br>
you don't then you'll just waste our time and yours because we<br>
won't be able to properly track the report.<br>
<br>
Please note that the Issue Tracking System is not intended to<br>
be used to seek help in the proper use of OpenLDAP Software.<br>
Such requests will be closed.<br>
<br>
OpenLDAP Software is user supported.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.OpenLDAP.org/support/" ta=
rget=3D"_blank">http://www.OpenLDAP.org/support/</a><br>
<br>
--------------<br>
Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><span style=3D"border-c=
ollapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-s=
ize:13px">=C2=A0 Carlo Pires<br></span>
</div>
--001a1135fa9258513c0503605842--
Full_Name: Howard Chu
Version: 2.4
OS:
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (8.25.222.90)
Submitted by: hyc
A number of controls allocate additional structures in their parsing, stored in
the op->o_controls[] array. Nothing cleans these up at the end of the
operation.
Usually these don't leak because they're allocated on the thread slab, but if
the incoming request is large enough it can force them into regular malloc.
Fix coming shortly.
Hi,
Following up from
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761407#23>:
This limitation seems to still exist (tried RE24 and master).
Until it can be fixed, please document it clearly in slapd-config.5 (and maybe
the admin guide too), as well as any related attrs if they also require a
restart (olcAuthzPolicy?). It's surprising behaviour, since almost every other
attribute does support online configuration. Proposed patch follows.
thanks,
Ryan
diff --git a/doc/man/man5/slapd-config.5 b/doc/man/man5/slapd-config.5
index c5bf06f..7c39369 100644
--- a/doc/man/man5/slapd-config.5
+++ b/doc/man/man5/slapd-config.5
@@ -409,6 +409,10 @@ values can be specified to allow for multiple matching
and replacement patterns. The matching patterns are checked in the order they
appear in the attribute, stopping at the first successful match.
+Note that changes to
+.B olcAuthzRegexp
+take effect the next time the server is started, not immediately upon
+changing the configuration.
.\".B Caution:
.\"Because the plus sign + is a character recognized by the regular expression engine,
.\"and it will appear in names that include a REALM, be careful to escape the
--On Wednesday, September 17, 2014 3:08 AM +0100 Howard Chu <hyc(a)symas.com>
wrote:
> quanah(a)openldap.org wrote:
>> Full_Name: Quanah Gibson-Mount
>> Version: 2.4.39
>> OS: Linux 3.11
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (75.111.58.125)
>>
>>
>> Found this at a customer site. They loaded an LDIF file that had the
>> child of an entry, but not the entry itself. slapadd then created a
>> glue entry to account for this, however there some significant problems
>> with this process
>>
>> a) The glue entry is not syntactically correct. There is no RDN value.
>>
>> b) It is impossible to use a filter with ldapsearch to find the entry.
>> It appears the objectClass index is utterly broken.
>
> Works as designed. Closing this ITS.
Even with -M, it appears impossible to find a specific glued entry, which
is problematic when attempting to find if it indeed exists or not outside
of a slapcat, or trying to parse (in this case) the 306 broken glued
entries that exist in the DB. It would be useful to be able (with -M) to
actually search for and find the specific entry so that the account
management client can then proceed accordingly. Right now, a search for
the specific entry results in error code 32, so then the account management
software attempts to create it, which results in error code 68. The
software then has no way to find the entry and decide if it needs
modification or deletion.
OTOH, it is entirely the clients fault for providing bad input, so I'm not
sure how hard we should chase it. :P
--Quanah
--
Quanah Gibson-Mount
Server Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration