Re: olcTLSCACertificateFile and olcTLSCertificateFile displayed as encrypted?

[Jean-Francois Malouin <Jean-Francois.Malouin@bic.mni.mcgill.ca>]

* Quanah Gibson-Mount <quanah@symas.com> [20180927 19:42]:
> --On Wednesday, September 26, 2018 5:11 PM -0400 Jean-Francois
> Malouin <Jean-Francois.Malouin@bic.mni.mcgill.ca> wrote:
> 
> >Hi,
> >
> >Not a very important question, just a little puzzled by this...
> >Is there a reason why the olcTLSCACertificateFile and
> >olcTLSCertificateFile paths show up as encrypted in this cn=config search?
> 
> Those are not encrypted, they're encoded.
> 
> If you decode them, you can see why... You have extra space
> characters at the beginning of the values:
> 
> mime-decode IC9ldGMvbGRhcC9zc2wvQ09NT0RPX0NBX2J1bmRsZS5jcnQ=
> ' /etc/ldap/ssl/COMODO_CA_bundle.crt'
> 
> mime-decode ICAgL2V0Yy9sZGFwL3NzbC9TVEFSX2JpY19tbmlfbWNnaWxsX2NhLmNydA==
> '   /etc/ldap/ssl/STAR_bic_mni_mcgill_ca.crt'

Ah, I see.
I have removed the leading white spaces and indeed they now display un-encoded.
Thank you for the info!

jf

> 
> 
> --Quanah
> 
> 
> 
> --
> 
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>