Problem with ReindexSMIMECertificates (after Upgrade to 6.4)

[tms]

Hi all,

after Upgrade to znuny 6.4. certificates were not visible in znuny S/MIME Management. This is solved by running ReindexSMIMECertificates (done also every night automatically). But this ran on an error for one certificate:

Code: Select all

 Message: Data too long for column 'subject' at row 1, SQL: '

This was due to a certificate with an (indeed) long subject:
Subject: C=TR, L=Gebze - Kocaeli, O=T\xC3\xBCrkiye Bilimsel ve Teknolojik Ara\xC5\x9Ft\xC4\xB1rma Kurumu - T\xC3\x9CB\xC4\xB0TAK, OU=Ulusal Elektronik ve Kriptoloji Ara\xC5\x9Ft\xC4\xB1rma Enstit\xC3\xBCs\xC3\xBC - UEKAE, OU=Kamu Sertifikasyon Merkezi, CN=T\xC3\x9CB\xC4\xB0TAK UEKAE K\xC3\xB6k Sertifika Hizmet Sa\xC4\x9Flay\xC4\xB1c\xC4\xB1s\xC4\xB1 - S\xC3\xBCr\xC3\xBCm 3

So my question: even if this subject looks a little strange, maybe nevertheless the database column for the subject might be too short in the znuny database?

And a second request: ReindexSMIMECertificates stopped completely after detecting this error. In my opinion it should just skip the affected certificate and continue with the other ones. Otherwise no certificates are handled at all if there is an error with the first one, even if the others would be ok.

For now I just deleted the affected certificate from my system, so everything runs fine for us, all other certificates are handled correctly.
But maybe the issue should be taken into account in the znuny development?

Best regards,
Stefanie

[root]

Hi,

Are there more details besides the column name? The table name would be interesting and the database type.

- Roy

[tms]

Sorry, yes, of course:
Message: Data too long for column 'subject' at row 1, SQL: '
INSERT INTO smime_keys (key_hash, key_type, file_name, email_address, expiration_date, fingerprint, subject, create_time, create_by)
VALUES
(?, ?, ?, ?, ?, ?, ?, ?, ?)'
We are using MariaDB.

[root]

Hi Stefanie,

Thank you, I'll check into this and we will probably adjust the size of this column. If required you can do this manually.

- Roy

[root]

Hi,

A change to fix this is alreay in QA and part of one of the next releases.

- Roy