Like in topic. When supplying 4096 byte certificate to *cert, everything is fine. When supplying 8192 byte certificate, it fails with aforementioned error.
Like in topic. When supplying 4096 byte certificate to *cert, everything is fine. When supplying 8192 byte certificate, it fails with aforementioned error.
##
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/13688550-error-14094417-ssl-routines-ssl3_read_bytes-sslv3-alert-illegal-parameter-when-using-certfp-certificate-of-length-8192?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:74372125 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Like in topic. When supplying 4096 byte certificate to *cert, everything is fine. When supplying 8192 byte certificate, it fails with aforementioned error.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
And the 8192 byte certificate works with the IRC server directly (without ZNC between it and the client)?