Closed GoogleCodeExporter closed 9 years ago
I forgot to mention that I am able to use the remote MySQL database server as
the backend for the Pyrit instance running on OSX if I remove any SSL
parameters and allow the pyrit database user to connect over an unencrypted
connection (REQUIRE NONE). So, for example, this command results in the
expected eval output:
pyrit -u "mysql://dbuser:dbpassword@dbserverip/pyritdb" eval
Original comment by dcarr...@gmail.com
on 9 May 2011 at 2:47
This is not something Pyrit can do anythng about. Please see the SQLAlchemy
guys about how to use SSL with mysql.
Original comment by lukas.l...@gmail.com
on 12 May 2011 at 6:52
Thanks for the response. I'll check with the SQLAlchemy guys about this issue
connecting to MySQL over SSL. I was a bit confused by the part of the stack
trace error "client library does not have SSL support." I thought it was
indicating that there is a lack of support for SSL in Pyrit. By the way, Pyrit
is a very impressive piece of work! Nice job!
Original comment by dcarr...@gmail.com
on 12 May 2011 at 7:32
I traced this issue down to the version of MySQL that I was running on the
client side. MySQLdb (MySQL-python) and therefore, SQLAlchemy and Pyrit can't
utilize SSL with MySQL when the client version of MySQL is anything higher than
5.5 (confirmed with 5.5.11 and 5.5.12). However, I was able to get it working
with MySQL versions 5.1.41 and 5.1.57. Another thing worth mentioning is that
the remote MySQL server can be 5.5.x (which is where I need all the performance
improvements from 5.5.x anyway) so that's good.
Cheers,
Dave
Original comment by dcarr...@gmail.com
on 14 May 2011 at 11:51
If anyone is interested in getting Pyrit set up to connect to a remote MySQL
instance over SSL, here's a step by step guide:
https://es.oteric.info/articles/how-to-install-pyrit-with-mysql-with-ssl-and-cud
a-support-on-osx
This is specific to a remote client running on OSX, but most of it would
probably also apply to any *nix environment.
Original comment by dcarr...@gmail.com
on 3 Aug 2011 at 3:11
Original issue reported on code.google.com by
dcarr...@gmail.com
on 9 May 2011 at 2:42