[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Antw: Garbled objectClass
- To: <ssbaksa@gmail.com>
- Subject: Antw: Garbled objectClass
- From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
- Date: Thu, 24 Oct 2019 08:18:19 +0200
- Cc: openldap-technical@openldap.org
- Content-disposition: inline
- In-reply-to: <5DB140BA020000A100034944@gwsmtp.uni-regensburg.de>
- References: <CANk+c=2QFqT8uNdJDTdv_A_1j-r4H5+w3k+j1XdVhX9iZ3SVXA@mail.gmail.com> <5DB140BA020000A100034944@gwsmtp.uni-regensburg.de>
>>> Ulrich Windl schrieb am 24.10.2019 um 08:12 in Nachricht <5DB140BA.E78 :
161 :
60728>:
>>>> Saša-Stjepan Bakša <ssbaksa@gmail.com> schrieb am 23.10.2019 um 16:52
in
> Nachricht
> <CANk+c=2QFqT8uNdJDTdv_A_1j-r4H5+w3k+j1XdVhX9iZ3SVXA@mail.gmail.com>:
> > Is there any good reason that I see one of my custom objectClass garbled
> > like this below. It happens when I am reading content from file. From GUI
> > tool it looks as it should.
> >
> > olcObjectClasses::
ezZ9KCAxLjMuNi4xLjQuMS4zNTI2OS4zLjI0NS4yLjcgTkFNRSAncGNyZ
> >
lBhY2thZ2UnIERFU0MgJ0NvbW1vbiBwYWNrYWdlIGRlc2NyaXB0aW9uIOKAkyBzZXJ2aWNlIHBh
> >
cmFtZXRlcnMgZGVmaW5lZCBieSBNTk8nIFNVUCB0b3AgU1RSVUNUVVJBTCBNVVNUICggcGNyZlB
> >
hY2thZ2VUaXRsZSAkIHBhY2thZ2VMaWZldGltZVR5cGUgKSBNQVkgKCBwYWNrYWdlQWN0aXZhdG
> >
lvbkRhdGUgJCBwYWNrYWdlRXhwaXJ5RGF0ZSAkIHBhY2thZ2VDeWNsZSAkIHRvdGFsTWF4aW11b
> >
VZvbHVtZSAkIHRvdGFsTWF4aW11bVRpbWUgJCBtb25pdG9yaW5nS2V5ICQgdG90YWxNYXhpbXVt
> > QW1vdW50ICQgY3ljbGVNdWx0aXBsaWVyICkgKQ==
> >
> > Others are normal and human readable.
>
> That BASE64 says:
> {6}( 1.3.6.1.4.1.35269.3.245.2.7 NAME 'pcrbase64: invalid input
Sorry, that was due to indent of BASE64. It says:
{6}( 1.3.6.1.4.1.35269.3.245.2.7 NAME 'pcrfPackage' DESC 'Common package
description – service parameters defined by MNO' SUP top STRUCTURAL MUST (
pcrfPackageTitle $ packageLifetimeType ) MAY ( packageActivationDate $
packageExpiryDate $ packageCycle $ totalMaximumVolume $ totalMaximumTime $
monitoringKey $ totalMaximumAmount $ cycleMultiplier ) )
>
>