Bug 9147 - 3_b2: ekiga-4.0.1 security fix and crash fixes released.
Summary: 3_b2: ekiga-4.0.1 security fix and crash fixes released.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 13:17 CET by Bit Twister
Modified: 2013-03-16 03:03 CET (History)
4 users (show)

See Also:
Source RPM: ekiga
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2013-02-21 13:17:13 CET 
ekiga-4.0.1 security fix and crash fixes released. See
http://ftp.gnome.org/pub/gnome/sources/ekiga/4.0/ekiga-4.0.1.news


Ekiga is available at:
http://ftp.gnome.org/pub/gnome/sources/ekiga/4.0/
and the required libraries can be found at:
http://ftp.gnome.org/pub/gnome/sources/opal/3.10/
http://ftp.gnome.org/pub/gnome/sources/ptlib/2.10/
Comment 1 Manuel Hiebel 2013-02-21 13:41:12 CET 
(I don't see sec fix)

CC: (none) => fundawang, olav, sander.lepik
Source RPM: (none) => ekiga

Comment 2 Bit Twister 2013-02-21 14:10:55 CET 
(In reply to Manuel Hiebel from comment #1)
> (I don't see sec fix)

I'll admit 5th Fix is pretty terse.

- Fix crash in XML parsing in case of malicious code

Only reason I noticed it was it was pointed out in their email ekiga-list feed.

I was/am more interested in the numerous crash fixes since I have had several crashes trying to place calls and whatnot with 4.0.0.
Comment 3 Nicolas Lécureuil 2013-03-14 10:46:17 CET 
please test new ekiga 4.0.1 in cauldron

CC: (none) => nicolas.lecureuil

Comment 4 Bit Twister 2013-03-16 03:03:38 CET 
(In reply to Nicolas Lécureuil from comment #3)
> please test new ekiga 4.0.1 in cauldron

After forced update of all the kde packages and ekiga, it no longer crashes when placing a diamondcard.us echo test.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.