Newbie question about security of Asterisk/elastix

marezi

Joined
Apr 19, 2009
Messages
10
Likes
0
Points
0
#1
Hello!

I am reading a lot of bugs being discovered and then fixed.
The last for example:
http://securitytracker.com/alerts/2009/Apr/1021970.html

When a fix/patch is released is there a simple way to aply it to elastix? How?

Is there a way to be informed or to make it more secure - autoupdate?

Thanks!
 

blackgecko

Joined
Apr 13, 2009
Messages
29
Likes
0
Points
0
#2
yum update
yum upgrade
 

marezi

Joined
Apr 19, 2009
Messages
10
Likes
0
Points
0
#3
blackgecko said:
yum update
yum upgrade
So this command also implements patches for asterisk?

Do I need to add repository for asterisk and elastix or is this already done in elastix ISO ?

Thanks.
 

blackgecko

Joined
Apr 13, 2009
Messages
29
Likes
0
Points
0
#4
it is already been done
 

rafael

Joined
May 14, 2007
Messages
1,454
Likes
1
Points
0
#5
That would upgrade your system to the latest version of Elastix. Elastix take care of upgrading asterisk packages.
 

marezi

Joined
Apr 19, 2009
Messages
10
Likes
0
Points
0
#6
rafael said:
That would upgrade your system to the latest version of Elastix. Elastix take care of upgrading asterisk packages.
Is there some kind of protection if upgrade is major - a lot of changes that could make problems on curent set up?
 

tarnok

Joined
Apr 20, 2009
Messages
16
Likes
0
Points
0
#7
I was wondering about marezi's question too. Lets say someone hasn't done a yum update/upgrade in 8+ months. Would there be any dangers / broken configurations occurring that is well known?

Which parts of the file system should be backed up to be safe?
 

jammerz

Joined
Sep 7, 2009
Messages
75
Likes
0
Points
0
#8
I've actually broken some of my elastix and pbxinflash boxes when doing yum updates on production systems and it was a fairly heavy burden to redo servers til I started utilizing vmware's esxi virtual machines and snapshots.

I would always suggest doing some tests on a separate development or virtual machine and first back it up or in VMware's case snapshot before you update, then see what is the outcome of yum update and if it works you can do the same on your production system, this way you can always revert back to last good snapshot...I did it on a production system without first testing on my dev system the other day (I know better) nevertheless, it saved my A.. when I reverted back to my snapshot and decided I'd better do some tests back on Dev box.

jf
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,886
Members
17,563
Latest member
dineshr
Top