0

I am trying to install ossec on a centos 6.4 machine but only repo which have .rpm file are from atomicrepo but then installing it require to upgrade my mysql I am reluctant to do it so I have used mock to rebuild and manage to yum install later from the build folder. My concern is that any security issue with regards to this issue or any other known issue and also how much extra space will this take?

2
Contributors
5
Replies
17
Views
4 Years
Discussion Span
Last Post by newbie14
0

No its for a production use. The problem is that I am tring to install ossec which is an intrusion detection system. For centos the only repo which have it is atomicorp and that requires few other upgrade like on the mysql. But I want to avoid all that and that is why I prefer to rebuild via mock and yum install it. I have tested on another machine it works. So I am worried in future will it be a problem ?

0

Well, you could build from source and install the updated version of MySQL to /usr/local instead of /usr. When you run the new mysqld daemon you can tell it to use a different port from the default. Then you could point ossec to that version of MySQL via the new port (maybe) instead of the default one.

Edited by rubberman

0

FWIW, I have found that newer versions of MySQL are pretty well backward compatible with older clients. If you want to install the newer version as the default, then make an external backup of your data and system drive so if it does FU, you can restore to a functioning system. Do that anyway... :-)

0

Dear Rubberman, All my centos machine are minimal installated so there is one with no mysql installed in it to minimise hacking risks. Thus in this case I am not sure as mock worked well. So I would like to know what is the disadvantage of using mock actually?

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.