GNOME Bugzilla – Bug 721198
ekiga-4.0.0 saves account settings in plain text, producing corrupt xml
Last modified: 2020-06-06 16:30:22 UTC
I'm using ekiga-4.0.0-r1 on Gentoo Linux. When I create a new SIP account, all the options are written unescaped as plain into ~/.config/ekiga.conf. So if the account name is “1&1” e.g., the passwort contains the character “&” or other xml-constructs, ekiga.conf will not be valid xml anymore. Then, when starting ekiga the next time, the config file can not be read: ** (process:28027): WARNING **: couldn't read the user configuration in /home/username/.config/ekiga.conf In effect all settings are lost and the configuration assistant is invoced. Apart from loosing the config, this is also a security issue. In particular the password SHOULD NOT be written as plaintext into the config file. The downstream bug can be found at: https://bugs.gentoo.org/show_bug.cgi?id=448698
Why aren't you using a GConf build on Linux ?
Because the gconf USE-flag is disabled by default. Enabling it is a suitable workaround.
Ok Anyway, the upcoming release has replaced GConf by GSettings, which is part of Glib => no dependancy. Moreover, the account is now saved as an XML description. However, the SIP Password is still stored as plain text for now, unfortunately...
Ekiga is not under active development anymore: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273 Ekiga saw its last release 7 years ago. The last code commits were 4 years ago. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.