openldap-bugs

openldap-bugs@openldap.org

1 participants
20966 discussions

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client
by siddjain＠live.com 24 Apr '19

24 Apr '19

--_000_MWHPR08MB24001BB2C0F56927A628AF69B53C0MWHPR08MB2400namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable we have documented complete steps to repro the bug here<https://github.com/= siddjain/openldap-bug> with container logs. ________________________________ From: Howard Chu <hyc(a)symas.com> Sent: Monday, April 22, 2019 10:15 AM To: siddjain(a)live.com; openldap-its(a)OpenLDAP.org Subject: Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate bef= ore sending it to client siddjain(a)live.com wrote: > Full_Name: SIDDHARTH JAIN > Version: 2.4.45 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (173.226.196.10) > > > In some cases, OpenLDAP will modify the TLS certificate given to it befor= e > sending it over to the client resulting in a certificate signature error.= An > example of certificate it modifies is given below: OpenLDAP never touches the certificates you configure. If you're getting a = corrupted certificate then there's either a bug in your storage/filesystem or in your= SSL/TLS library. -- -- Howard Chu CTO, Symas Corp. https://eur04.safelinks.protection.outlook.com= /?url=3Dhttp%3A%2F%2Fwww.symas.com&data=3D02%7C01%7C%7Cb0dec02e090a48ff= 954b08d6c7462da0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6369155015543= 63548&sdata=3D7ca82woC2PGsf9x0qYDT1izZ5MSqJbxA4T9m8kq5y2Y%3D&reserv= ed=3D0 Director, Highland Sun https://eur04.safelinks.protection.outlook.com= /?url=3Dhttp%3A%2F%2Fhighlandsun.com%2Fhyc%2F&data=3D02%7C01%7C%7Cb0dec= 02e090a48ff954b08d6c7462da0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63= 6915501554363548&sdata=3DFr3v%2FI3WSXtWqXOFDY%2F9Z4%2FqS%2F%2FvC4YMJQDR= GNjx8Lo%3D&reserved=3D0 Chief Architect, OpenLDAP https://eur04.safelinks.protection.outlook.com= /?url=3Dhttp%3A%2F%2Fwww.openldap.org%2Fproject%2F&data=3D02%7C01%7C%7C= b0dec02e090a48ff954b08d6c7462da0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0= %7C636915501554373561&sdata=3DJ%2B926RRaeQIx6%2BIvx70BnHqZ0zj4SO5ilR6VP= vdiTsk%3D&reserved=3D0 --_000_MWHPR08MB24001BB2C0F56927A628AF69B53C0MWHPR08MB2400namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;= color: rgb(0, 0, 0);"> <span style=3D"color: rgb(36, 41, 46); font-family: -apple-system, system-u= i, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Em= oji", "Segoe UI Emoji", "Segoe UI Symbol"; font-si= ze: 14px; background-color: rgb(255, 255, 255); display: inline !important"= >we have documented complete steps to repro the bug<span> </span></span><= a href=3D"https://github.com/siddjain/openldap-bug" style=3D"box-sizing: bo= rder-box; background-color: rgb(255, 255, 255); color: rgb(3, 102, 214); fo= nt-family: -apple-system, system-ui, "Segoe UI", Helvetica, Arial= , sans-serif, "Apple Color Emoji", "Segoe UI Emoji", &q= uot;Segoe UI Symbol"; font-size: 14px">here</a><span style=3D"color: r= gb(36, 41, 46); font-family: -apple-system, system-ui, "Segoe UI"= , Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe = UI Emoji", "Segoe UI Symbol"; font-size: 14px; background-co= lor: rgb(255, 255, 255); display: inline !important"><span> </span>wit= h container logs.</span><br> </div> <div> <div id=3D"appendonsend"></div> <div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col= or:rgb(0,0,0)"> <br> </div> <hr tabindex=3D"-1" style=3D"display:inline-block; width:98%"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co= lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Howard Chu <hyc@sy= mas.com><br> <b>Sent:</b> Monday, April 22, 2019 10:15 AM<br> <b>To:</b> siddjain(a)live.com; openldap-its(a)OpenLDAP.org<br> <b>Subject:</b> Re: (ITS#9014) OpenLDAP modifies user provided TLS certific= ate before sending it to client</font> <div> </div> </div> <div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt"= > <div class=3D"PlainText">siddjain(a)live.com wrote:<br> > Full_Name: SIDDHARTH JAIN<br> > Version: 2.4.45<br> > OS: Linux<br> > URL: <a href=3D"ftp://ftp.openldap.org/incoming/">ftp://ftp.openldap.o= rg/incoming/</a><br> > Submission from: (NULL) (173.226.196.10)<br> > <br> > <br> > In some cases, OpenLDAP will modify the TLS certificate given to it be= fore<br> > sending it over to the client resulting in a certificate signature err= or. An<br> > example of certificate it modifies is given below:<br> <br> OpenLDAP never touches the certificates you configure. If you're getting a = corrupted<br> certificate then there's either a bug in your storage/filesystem or in your= SSL/TLS library.<br> <br> -- <br>   -- Howard Chu<br>   CTO, Symas Corp.        &nbs= p;  <a href=3D"https://eur04.safelinks.protection.outlook.com/?url=3Dh= ttp%3A%2F%2Fwww.symas.com&amp;data=3D02%7C01%7C%7Cb0dec02e090a48ff954b0= 8d6c7462da0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636915501554363548= &amp;sdata=3D7ca82woC2PGsf9x0qYDT1izZ5MSqJbxA4T9m8kq5y2Y%3D&amp;res= erved=3D0"> https://eur04.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fwww.syma= s.com&amp;data=3D02%7C01%7C%7Cb0dec02e090a48ff954b08d6c7462da0%7C84df9e= 7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636915501554363548&amp;sdata=3D7ca= 82woC2PGsf9x0qYDT1izZ5MSqJbxA4T9m8kq5y2Y%3D&amp;reserved=3D0</a><br>   Director, Highland Sun     <a href=3D"https://eu= r04.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fhighlandsun.com%2F= hyc%2F&amp;data=3D02%7C01%7C%7Cb0dec02e090a48ff954b08d6c7462da0%7C84df9= e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636915501554363548&amp;sdata=3DFr= 3v%2FI3WSXtWqXOFDY%2F9Z4%2FqS%2F%2FvC4YMJQDRGNjx8Lo%3D&amp;reserved=3D0= "> https://eur04.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fhighland= sun.com%2Fhyc%2F&amp;data=3D02%7C01%7C%7Cb0dec02e090a48ff954b08d6c7462d= a0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636915501554363548&amp;= sdata=3DFr3v%2FI3WSXtWqXOFDY%2F9Z4%2FqS%2F%2FvC4YMJQDRGNjx8Lo%3D&amp;re= served=3D0</a><br>   Chief Architect, OpenLDAP  <a href=3D"https://eur04.safelinks.p= rotection.outlook.com/?url=3Dhttp%3A%2F%2Fwww.openldap.org%2Fproject%2F&amp= ;amp;data=3D02%7C01%7C%7Cb0dec02e090a48ff954b08d6c7462da0%7C84df9e7fe9f640a= fb435aaaaaaaaaaaa%7C1%7C0%7C636915501554373561&amp;sdata=3DJ%2B926RRaeQ= Ix6%2BIvx70BnHqZ0zj4SO5ilR6VPvdiTsk%3D&amp;reserved=3D0"> https://eur04.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fwww.open= ldap.org%2Fproject%2F&amp;data=3D02%7C01%7C%7Cb0dec02e090a48ff954b08d6c= 7462da0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636915501554373561&amp= ;amp;sdata=3DJ%2B926RRaeQIx6%2BIvx70BnHqZ0zj4SO5ilR6VPvdiTsk%3D&amp;res= erved=3D0</a><br> </div> </span></font></div> </div> </body> </html> --_000_MWHPR08MB24001BB2C0F56927A628AF69B53C0MWHPR08MB2400namp_--

1 0

Re: (ITS#9015) Replication goes haywire querying promoted master
by ondra＠mistotebe.net 24 Apr '19

24 Apr '19

On Tue, Apr 23, 2019 at 11:28:40PM +0000, quanah(a)symas.com wrote: > --On Tuesday, April 23, 2019 8:56 PM +0200 Ond=C5=99ej Kuzn=C3=ADk=20 > <ondra(a)mistotebe.net> wrote: >> Going by what I think I remember of the consumer code did: >> - on set up, it finds out there's no cookie to go by so it goes into >> refresh on the main DB >> - main DB responds with success but no/empty cookie >> - consumer starts over but again finds itself with no cookie, so it goes >> to step one >> >> But the consumer is actually up to date at that point as the search >> suggested, so it should just go ahead and do the refreshAndPersist on >> accesslog as it planned to originally. And as operations hit the main >> DB, they will replicate accordingly, even if that were to happen after >> the original search and before this one[0]. > > The consumer did not replicate the database as a part of the initial > search, so I don't think it qualifies as "up to date". I.e., it's primary > DB remains empty. Ah, that wasn't mentioned, my assumption was that the source DB was actually empty. This is coming from ITS#8281 fix in cd8ff37629012c1676ef79de164a159da9b2ae89. There are two scenarios that need different treatment: 1. We start with no servers and no data and want to set up MMR from there 2. We start with a live server and want to move over to MMR The bootstrap scenario is the one I outlined in my response above, the consumers should be able to deal with it correctly if they do what I say. However the provider should make it possible for the client to know that's what's happening, so it should only send an empty cookie-less response in the case DB is empty. The conversion to MMR should be dealt with differently. AFAIK, the correct order of set up is: - prepare original master: - serverID == 0 - add syncprov - change serverID accordingly - connect other servers: - set serverIDs - add olcSyncrepl everywhere (including original master) - wait for things to settle, you're done I agree it is necessary we make sure not following the above still results either with a helpful error or that it also Just Works(tm). Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#9016) cn=config should fail on EMIT if target directory not empty
by michael＠stroeder.com 24 Apr '19

24 Apr '19

This is a cryptographically signed message in MIME format. --------------ms030705030102060301060203 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 4/24/19 1:32 PM, ondra(a)openldap.org wrote: > Since it's not feasible to clean up properly, it should just return an = error > instead? Yes. In general I prefer fail-early-fail-hard with clear error messages. Ciao, Michael. --------------ms030705030102060301060203 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC CyEwggUzMIIEG6ADAgECAhBcyYchBfxJZNzvHl+r2LoiMA0GCSqGSIb3DQEBCwUAMIGXMQsw CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJTQSBD bGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xODEyMTYwMDAw MDBaFw0xOTEyMTYyMzU5NTlaMCUxIzAhBgkqhkiG9w0BCQEWFG1pY2hhZWxAc3Ryb2VkZXIu Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvdaCPHlSjB9Wb51jh60x+6OO lOP14FSXRNDYWcuaCwey30JdrJxw9VMiBEJo7Q7fHWcpna9l9oVKuvjO3VepiyTlQoinvwSG gQrBburWskKupOJPwv0QH8nWpc9KnP7LnOqfepwHNrqhweijxeGg95TQeDfOVbQmGwqnaCtp CBuCu3gyxe/wVkKnr6uqwHFUoGSNIrLAdLFcnFbpKGoYvZvahkdLNglCRLpeSVu9/O0MqkGt gGp6nPcTHwbZYSoGqFJQjPeTlczubTKo9DWYhZ0vMB2fjdadSqZxUgqqdElLRWSqRD1jCm3U xShVkPJDQg3tkQq6Yw4C1Z9+L9KxJQIDAQABo4IB6jCCAeYwHwYDVR0jBBgwFoAUgq9sjPjF /pZhfOgfPStxSF7Ei8AwHQYDVR0OBBYEFLn0/ESCAOEV6clL6lYXzOwKIKlyMA4GA1UdDwEB /wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMF AjARBglghkgBhvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggr BgEFBQcCARYdaHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwWgYDVR0fBFMwUTBPoE2g S4ZJaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RPUlNBQ2xpZW50QXV0aGVudGljYXRp b25hbmRTZWN1cmVFbWFpbENBLmNybDCBiwYIKwYBBQUHAQEEfzB9MFUGCCsGAQUFBzAChklo dHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9SU0FDbGllbnRBdXRoZW50aWNhdGlvbmFu ZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5j b20wHwYDVR0RBBgwFoEUbWljaGFlbEBzdHJvZWRlci5jb20wDQYJKoZIhvcNAQELBQADggEB ALFD55CXI+vy81ngFjheHu+TjKJuxrYfw71qz54pmYwR4UYBTSLNvESJXwOfSi7UxBh97xjB bjy5rDByXl1IWAFXcnoHPKJNZL8wOa0MNz4o3X0of7JHZHYlyXJRnZV90+KtZQdn5ZP2hBmg SHxcjdgCMU9p6VoOlJLhpEKN1TmbHq/elcwZKknnGN+54Vn2RhVP0x3998yyhIkiHNAqQImT cqY5QkpGxyocLz54NXudIZSvXyvQI4d7FYl4JKn6gw4PRXht0/xzB/GGGKGWSrgdPCUJ4Rif cGpO43inEBxWlW19cjYSXjqZetq2ZIJnrADxTttTJoUQsGuoT5ZMf2UwggXmMIIDzqADAgEC AhBqm+E4O/8ra58B1dm4p1JWMA0GCSqGSIb3DQEBDAUAMIGFMQswCQYDVQQGEwJHQjEbMBkG A1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFD T01PRE8gQ0EgTGltaXRlZDErMCkGA1UEAxMiQ09NT0RPIFJTQSBDZXJ0aWZpY2F0aW9uIEF1 dGhvcml0eTAeFw0xMzAxMTAwMDAwMDBaFw0yODAxMDkyMzU5NTlaMIGXMQswCQYDVQQGEwJH QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYD VQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJTQSBDbGllbnQgQXV0 aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEP ADCCAQoCggEBAL6znlesKHZ1QBbHOAOY08YYdiFQ8yV5C0y1oNF9Olg+nKcxLqf2NHbZhGra 0D00SOTq9bus3/mxgUsg/Wh/eXQ0pnp8tZ8XZWAnlyKMpjL+qUByRjXCA6RQyDMqVaVUkbIr 5SU0RDX/kSsKwer3H1pT/HUrBN0X8sKtPTdGX8XAWt/VdMLBrZBlgvnkCos+KQWWCo63OTTq Rvaq8aWccm+KOMjTcE6s2mj6RkalweyDI7X+7U5lNo6jzC8RTXtVV4/Vwdax720YpMPJQaDa ElmOupyTf1Qib+cpukNJnQmwygjD8m046DQkLnpXNCAGjuJy1F5NATksUsbfJAr7FLUCAwEA AaOCATwwggE4MB8GA1UdIwQYMBaAFLuvfgI9+qbxPISOre44mOzZMjLUMB0GA1UdDgQWBBSC r2yM+MX+lmF86B89K3FIXsSLwDAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIB ADARBgNVHSAECjAIMAYGBFUdIAAwTAYDVR0fBEUwQzBBoD+gPYY7aHR0cDovL2NybC5jb21v ZG9jYS5jb20vQ09NT0RPUlNBQ2VydGlmaWNhdGlvbkF1dGhvcml0eS5jcmwwcQYIKwYBBQUH AQEEZTBjMDsGCCsGAQUFBzAChi9odHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9SU0FB ZGRUcnVzdENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMA0G CSqGSIb3DQEBDAUAA4ICAQB4XLKBKDRPPO5fVs6fl1bsj6JrF/bz9kkIBtTYLzXN30D+03Hj 6OxCDBEaIeNmsBhrJmuubvyE7HtoSmR809AgcYboW+rcTNZ/8u/Hv+GTrNI/AhqX2/kiQNxm gUPt/eJPs92Qclj0HnVyy9TnSvGkSDU7I5Px+TbO+88G4zipA2psZaWeEykgzClZlPz1FjTC kk77ZXp5cQYYexE6zeeN4/0OqqoAloFrjAF4o50YJafX8mnahjp3I2Y2mkjhk0xQfhNqbzlL WPoT3m7j7U26u7zg6swjOq8hITYc3/np5tM5aVyu6t99p17bTbY7+1RTWBviN9YJzK8HxzOb XYWBf/L+VGOYNsQDTxAk0Hbvb1j6KjUhg7fO294F29QIhhmiNOr84JHoy+fNLpfvYc/Q9EtF OI5ISYgOxLk3nD/whbUe9rmEQXLp8MB933Ij474gwwCPUpwv9mj2PMnXoc7mbrS22XUSeTwx CTP9bcmUdp4jmIoWfhQm7X9w/Zgddg+JZ/YnIHOwsGsaTUgj7fIvxqith7DoJC91WJ8Lce3C VJqb1XWeKIJ84F7YLXZN0oa7TktYgDdmQVxYkZo1c5noaDKH9Oq9cbm/vOYRUM1cWcef20Wk yk5S/GFyyPJwG0fR1nRas3DqAf4cXxMiEKcff7PNa4M3RGTqH0pWR8p6EjGCBDUwggQxAgEB MIGsMIGXMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYD VQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09N T0RPIFJTQSBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQXMmH IQX8SWTc7x5fq9i6IjANBglghkgBZQMEAgEFAKCCAlkwGAYJKoZIhvcNAQkDMQsGCSqGSIb3 DQEHATAcBgkqhkiG9w0BCQUxDxcNMTkwNDI0MTIwMzU1WjAvBgkqhkiG9w0BCQQxIgQgn56E SGO4wXtKJNZ055HSw53D3LbVbJTHd7PGKrb0KSkwbAYJKoZIhvcNAQkPMV8wXTALBglghkgB ZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG 9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBvQYJKwYBBAGCNxAEMYGvMIGsMIGX MQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdT YWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJT QSBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQXMmHIQX8SWTc 7x5fq9i6IjCBvwYLKoZIhvcNAQkQAgsxga+ggawwgZcxCzAJBgNVBAYTAkdCMRswGQYDVQQI ExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9E TyBDQSBMaW1pdGVkMT0wOwYDVQQDEzRDT01PRE8gUlNBIENsaWVudCBBdXRoZW50aWNhdGlv biBhbmQgU2VjdXJlIEVtYWlsIENBAhBcyYchBfxJZNzvHl+r2LoiMA0GCSqGSIb3DQEBAQUA BIIBAJD4gv8eWV6VCHuVWTALdiWdt2YNBvDN7tyVNwURCnW+mlB9gPxBR1uJMp2L49dEdESO 0Dg/A61z0sO35S0wJYCLU8L7RuNahsjkZg8/CSaAPpnbG2xs3jaLNzhaPb1WULR9qbNyJ8dp xwdMSp19gMNUpgTLmHYmsTeAvtujjp4eZwh9VufCbcFstJOMWYO2fyBpJilG4RIouM2bPCLo ii4tAzSDONIeF7W1W1G73xLkw1lmSS4N1zBg1dFJgMTp9bcrGkBqzJajrpeWN2nUGuZBl+xi ucV4w8hezAnVVE8UFofDxn8i1JPsMoCjr1tBcSQg4NQzA5p3nnrOb5ERpDcAAAAAAAA= --------------ms030705030102060301060203--

1 0

(ITS#9016) cn=config should fail on EMIT if target directory not empty
by ondra＠openldap.org 24 Apr '19

24 Apr '19

Full_Name: Ondrej Kuznik Version: re24/master OS: URL: Submission from: (NULL) (82.10.24.68) Running slapd/slaptest to convert a slapd.conf to cn=config will happily reuse the target directory. However if there was some existing configuration present already, slaptest reports a successful conversion, even though the resulting directory most likely won't represent the slapd.conf used - existing .ldif files won't be replaced or removed. Depending on the differences between slapd.conf and slapd.d in place, the result might not even be a useable cn=config anymore. Since it's not feasible to clean up properly, it should just return an error instead?

1 0

Re: (ITS#9015) Replication goes haywire querying promoted master
by quanah＠symas.com 23 Apr '19

23 Apr '19

--On Tuesday, April 23, 2019 8:56 PM +0200 Ond=C5=99ej Kuzn=C3=ADk=20 <ondra(a)mistotebe.net> wrote: > Going by what I think I remember of the consumer code did: > - on set up, it finds out there's no cookie to go by so it goes into > refresh on the main DB > - main DB responds with success but no/empty cookie > - consumer starts over but again finds itself with no cookie, so it goes > to step one > > But the consumer is actually up to date at that point as the search > suggested, so it should just go ahead and do the refreshAndPersist on > accesslog as it planned to originally. And as operations hit the main > DB, they will replicate accordingly, even if that were to happen after > the original search and before this one[0]. The consumer did not replicate the database as a part of the initial=20 search, so I don't think it qualifies as "up to date". I.e., it's primary=20 DB remains empty. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#9015) Replication goes haywire querying promoted master
by ondra＠mistotebe.net 23 Apr '19

23 Apr '19

On Tue, Apr 23, 2019 at 04:48:28PM +0000, quanah(a)openldap.org wrote: > In testing a particular use case/setup scenario, I found that it's possible to > cause a replica to slam a provider with unending requests. In this specific > case, I was setting up delta-syncrepl MMR, but I believe the issue applies to > standard syncrepl, and is not MMR specific. The scenario looks like this: > > Initially we have a stand alone server, which no overlays in place. The > configuration is done via cn=config, which allows for us to update the > configuration without a server restart. > > [...] > > I believe the problem is that the root entry for the database contains no > contextCSN. This is likely due to the fact that: > > [...] > > However, I think the overall behavior is undesirable. If there is no contextCSN > present, it should not lead to replication clients executing a potential DoS on > the provider. It also generated ~60GB of logs at loglevel stats in 1 day. Ok, I think this is consumer's fault and limited to refreshAndPersist deltasync (with or without MMR). Going by what I think I remember of the consumer code did: - on set up, it finds out there's no cookie to go by so it goes into refresh on the main DB - main DB responds with success but no/empty cookie - consumer starts over but again finds itself with no cookie, so it goes to step one But the consumer is actually up to date at that point as the search suggested, so it should just go ahead and do the refreshAndPersist on accesslog as it planned to originally. And as operations hit the main DB, they will replicate accordingly, even if that were to happen after the original search and before this one[0]. So in that case the behaviour would be as follows: - on set up, it finds out there's no cookie to go by so it goes into refresh on the main DB - main DB responds with success but no/empty cookie - consumer starts over, remembering that its cookie (albeit empty) is valid, so sends a refreshAndPersist search on accesslog DB - that yields no traffic, but will give it the right data once anything replication-worthy happens, job done - unless the connection is actually severed (restarts, ...) before anything needs replicating, we start from step one but no overhead was incurred, we're still fine [0]. Unless so much time has elapsed between the two searches (that happen on the same connection BTW) that some accesslog ops have already been expired. Expiration is usually configured in days, not seconds and an admin that doesn't notice a consumer going AWOL for that amount of time probably deserves that. -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#9015) Replication goes haywire querying promoted master
by quanah＠symas.com 23 Apr '19

23 Apr '19

--On Tuesday, April 23, 2019 7:07 PM +0100 Howard Chu <hyc(a)symas.com> wrote: > The consumer should not be reconnecting more frequently than its retry > config. Since the consumer never disconnects, there is no reconnect. It connects a single time, and issues the same operation endlessly. Thus why when you look at the log file snippet I pasted, you see an OPERATION count in the MILLIONS. conn=1003 op=361869515 I.e., OPERATION 361,869,515 for connection 1003. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#9015) Replication goes haywire querying promoted master
by hyc＠symas.com 23 Apr '19

23 Apr '19

quanah(a)openldap.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.47 > OS: N/A > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (47.208.144.40) > > > In testing a particular use case/setup scenario, I found that it's possible to > cause a replica to slam a provider with unending requests. In this specific > case, I was setting up delta-syncrepl MMR, but I believe the issue applies to > standard syncrepl, and is not MMR specific. The scenario looks like this: > > Initially we have a stand alone server, which no overlays in place. The > configuration is done via cn=config, which allows for us to update the > configuration without a server restart. > > The configuration is modified to load the syncprov and accesslog overlays, > create a new accesslog database, and to send all change data to the accesslog > db. > > After that is done, a secondary server is brought online with the same > configuration other than the serverID being different and the syncrepl statement > adjusted. > > When the secondary server is started, it pummels the initial provider with > queries like: > > Apr 23 06:39:06 anvil4 slapd[28967]: conn=1003 op=361868131 SRCH > base="dc=example,dc=com" scope=2 deref=0 filter="(objectClass=*)" > Apr 23 06:39:06 anvil4 slapd[28967]: conn=1003 op=361868131 SRCH attr=* + > Apr 23 06:39:06 anvil4 slapd[28967]: conn=1003 op=361868131 SEARCH RESULT > tag=101 err=0 nentries=0 text= > > (Averaging around 2000 queries/second on my server per syncrepl client). > > I believe the problem is that the root entry for the database contains no > contextCSN. This is likely due to the fact that: > > a) There was never a syncprov overlay present until I loaded this one in > b) The serverID was set prior to the syncprov overlay being loaded (So it went > from "0" to "1", with no changes ever recorded for "1"). > > Now there is a trivial ways to handle this, by making a change on the provider > prior to starting up the other servers. > > However, I think the overall behavior is undesirable. If there is no contextCSN > present, it should not lead to replication clients executing a potential DoS on > the provider. It also generated ~60GB of logs at loglevel stats in 1 day. The consumer should not be reconnecting more frequently than its retry config. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#9015) Replication goes haywire querying promoted master
by quanah＠openldap.org 23 Apr '19

23 Apr '19

Full_Name: Quanah Gibson-Mount Version: 2.4.47 OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.144.40) In testing a particular use case/setup scenario, I found that it's possible to cause a replica to slam a provider with unending requests. In this specific case, I was setting up delta-syncrepl MMR, but I believe the issue applies to standard syncrepl, and is not MMR specific. The scenario looks like this: Initially we have a stand alone server, which no overlays in place. The configuration is done via cn=config, which allows for us to update the configuration without a server restart. The configuration is modified to load the syncprov and accesslog overlays, create a new accesslog database, and to send all change data to the accesslog db. After that is done, a secondary server is brought online with the same configuration other than the serverID being different and the syncrepl statement adjusted. When the secondary server is started, it pummels the initial provider with queries like: Apr 23 06:39:06 anvil4 slapd[28967]: conn=1003 op=361868131 SRCH base="dc=example,dc=com" scope=2 deref=0 filter="(objectClass=*)" Apr 23 06:39:06 anvil4 slapd[28967]: conn=1003 op=361868131 SRCH attr=* + Apr 23 06:39:06 anvil4 slapd[28967]: conn=1003 op=361868131 SEARCH RESULT tag=101 err=0 nentries=0 text= (Averaging around 2000 queries/second on my server per syncrepl client). I believe the problem is that the root entry for the database contains no contextCSN. This is likely due to the fact that: a) There was never a syncprov overlay present until I loaded this one in b) The serverID was set prior to the syncprov overlay being loaded (So it went from "0" to "1", with no changes ever recorded for "1"). Now there is a trivial ways to handle this, by making a change on the provider prior to starting up the other servers. However, I think the overall behavior is undesirable. If there is no contextCSN present, it should not lead to replication clients executing a potential DoS on the provider. It also generated ~60GB of logs at loglevel stats in 1 day.

1 0

Re: (ITS#9014) OpenLDAP modifies user provided TLS certificate before sending it to client
by hyc＠symas.com 22 Apr '19

22 Apr '19

siddjain(a)live.com wrote: > Full_Name: SIDDHARTH JAIN > Version: 2.4.45 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (173.226.196.10) > > > In some cases, OpenLDAP will modify the TLS certificate given to it before > sending it over to the client resulting in a certificate signature error. An > example of certificate it modifies is given below: OpenLDAP never touches the certificates you configure. If you're getting a corrupted certificate then there's either a bug in your storage/filesystem or in your SSL/TLS library. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs