1. Have a look at the mysql logs on the server. It may give you a reason
for the failure.
2. Run wireshark to have a look at the communications. It may give a
clue as to what is failing.
On Wed, 2012-01-25 at 18:16 +0200, Felix Liberman wrote:
> Hi Shmuel,
>
>
> The reason is simple - it's IT requirement for any application that
> transfers authentication info.
> In my case I'm sending DB user+password combination over TCP that
> (theoretically) could be intercepted and sniffed.
>
> Anyway, I'm stuck and need some fresh idea how to debug this
> failure...
>
>
> Will someone educate me why you should connect your DB using
> SSL?
> (assuming that you are on the same network, and not
> communicating across
> the internet, of course)
> Shmuel.
> On Tue, Jan 24, 2012 at 11:27 PM, Felix Liberman
> <felix.liberman at gmail.com>wrote:
> > Hi All,
> >
> > I'm trying to re-configure my Perl application that
> communicates with
> > MySQL server via DBI layer.
> > Previous version worked perfectly without SSL, but now (for
> production
> > mode) higher security measures required, so I switched to
> SSL.
> ...
> > The DBD::mysql (rev 4.018) module was compiled with SSL
> enabled option,
> > but client application fails:
> >
> > {{{
> > DBI
> >
>
> connect('database=sc_prj_cm;host={somehost};port=3306;mysql_ssl=1;mysql_ssl_ca_file=/{somepath}/ssl_certs/cacert.pem','{someuser}',...)
> > failed: SSL connection error at {my source code}
> > }}}
>
>
> --
> ~Felix_
>
>
> _______________________________________________
> Perl mailing list
> [email protected]
> http://mail.perl.org.il/mailman/listinfo/perl
_______________________________________________
Perl mailing list
[email protected]
http://mail.perl.org.il/mailman/listinfo/perl
