Devart Forums

csdev

Hi, I'm currently trying to use MySqlConnection (in MyDirect .NET 3.50.13) to create a secure connection to a MySQL 5.1 server. I'm currently able to do the same thing with no problems using either the MySQL client or their C++ library, but when using MyDirect, I receive an exception citing an 'Invalid PEM header.'

The contents of the stack trace are as follows:

Code: Select all

   at CoreLab.Security.a.a(Byte[] A_0, String& A_1, Byte[]& A_2)
   at CoreLab.Security.a.a(Byte[] A_0)
   at CoreLab.Security.a.b(String A_0)
   at CoreLab.Security.j.f(String A_0)
   at CoreLab.MySql.j.a(String A_0, String A_1)
   at CoreLab.MySql.b.a(String A_0, String A_1, String A_2, String A_3, Int32 A_4, String A_5, Int32 A_6, SshOptions A_7, SslOptions A_8)
   at CoreLab.MySql.MySqlInternalConnection.Connect(String userId, String password, String host, String database, Int32 port, Int32 connectionTimeout, MySqlProtocol protocol, Boolean compress)
   at CoreLab.MySql.MySqlInternalConnection..ctor(ac connectionOptions)
   at CoreLab.MySql.a7.a(DbConnectionOptions A_0, Object A_1, DbConnectionBase A_2)
   at CoreLab.Common.DbConnectionFactory.a(DbConnectionPool A_0, DbConnectionOptions A_1)
   at CoreLab.Common.DbConnectionPool.a()
   at CoreLab.Common.DbConnectionPool.GetObject()
   at CoreLab.Common.DbConnectionFactory.a(DbConnectionBase A_0)
   at CoreLab.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)
   at CoreLab.MySql.MySqlConnection.Open()
   at
ConnectToRemoteDatabase() <-- My function

I used OpenSSL to generate the files (server and clients share the same CA, but not certificates or common names). Does anyone know why MyDirect wouldn't like certain PEM-encoded certificates and keys?

csdev

Hi, I'm having the exact same problem, and since I don't think it should require 'days' to solve, how about posting the resolution here so that others may benefit from the knowledge, rather than handling it offline?

Devart Forums

Search found 2 matches

Invalid PEM Header?