https://bugzilla.novell.com/show_bug.cgi?id=486267 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |lnussel@novell.com |ovo.novell.com | --- Comment #1 from Marcus Meissner 2009-03-18 15:23:19 MST --- we released stricter dbus checking and stricter networkmanager profiles. it should however all still work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net --- Comment #3 from Ludwig Nussel 2009-03-19 02:10:44 MST --- Did you really install all available updates? Did you reboot after installing the updates? If you can answer both question with yes please attach /var/log/messages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User Larry.Finger@lwfinger.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c5 --- Comment #5 from Larry Finger 2009-03-19 10:06:43 MST --- Created an attachment (id=280689) --> (https://bugzilla.novell.com/attachment.cgi?id=280689) Output of /var/log/NetworkManager after rebooting -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c7 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net --- Comment #7 from Ludwig Nussel 2009-03-19 14:16:45 MST --- what's the output of rpm -q --changelog NetworkManager-kde|head ? Should be * Mi Feb 25 2009 hschaa@suse.de - Add fix_dbus_conf.patch (bnc#479563, CVE-2009-0578) .. Make sure you install NetworkManager-kde from the correct repo. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c9 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net --- Comment #9 from Ludwig Nussel 2009-03-20 03:11:42 MST --- You are really sure that you installed *all* available updates, including dbus etc? If so I have no idea what's wrong then. Could you please tar up /etc/dbus-1 and attach here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User dmueller@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c11 Dirk Mueller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmueller@novell.com, | |hschaa@novell.com --- Comment #11 from Dirk Mueller 2009-03-20 05:08:42 MST --- I've submitted a new done/11.1/NetworkManager-kde that appears to work for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c13 --- Comment #13 from Ludwig Nussel 2009-03-20 06:59:49 MST --- the config also opens the security hole again so this one cannot be used. AFAICT the knetworkmanager.conf from 11.1 looks good and it works just fine here if I use it with nm-applet instead of nm-applet.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User Larry.Finger@lwfinger.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c15 Larry Finger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Larry.Finger@lwfinger.net | --- Comment #15 from Larry Finger 2009-03-20 07:35:08 MST --- Created an attachment (id=280922) --> (https://bugzilla.novell.com/attachment.cgi?id=280922) tarball of /etc/dbus-1 All patches listed as "Needed" by YaST => Online Update have been installed. Just in case I got a bad download, I refreshed every installed package that was listed in searches for "NetworkManager", "dbus" and "PolicyKit" in YaST => Software Management. This did not help. I probably didn't mention this earlier, but I'm running a 2.6.29-rc8 kernel. After finishing this post, I'll reboot into the standard kernel to see if that changes anything. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c17 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thoenig@novell.com --- Comment #17 from Ludwig Nussel 2009-03-20 07:52:22 MST --- the config looks goot AFAICT. TBH I'm out of ideas :( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c21 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Larry.Finger@lwfinger.net --- Comment #21 from Helmut Schaa 2009-03-20 09:52:12 MST --- Yep, your patch would allow all users to read the connection secrets. The following dbus-send command reads the secrets from the first connection object KNM provides. Could you please check (with and without your patch) if the command allows root to read the secrets and denies the same to a normal user? dbus-send --system --print-reply --dest=org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/Connection/0 org.freedesktop.NetworkManagerSettings.Connection.Secrets.GetSecrets -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User Larry.Finger@lwfinger.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c23 --- Comment #23 from Larry Finger 2009-03-20 14:16:26 MST --- I am not the only one with the problem. See the thread entitled "WPA not working anymore with ath5k / NetworkManager (NC10)" in the openSUSE Wireless Subforum. I was not able to find a patch that satisfied the security requirements. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User Larry.Finger@lwfinger.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c26 --- Comment #26 from Larry Finger 2009-03-21 14:30:36 MST --- Do the two systems have the same architecture? I see the problem with x86_64. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User georgmueller@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c28 --- Comment #28 from Georg Müller 2009-03-21 15:41:15 MST --- hm, if I understand dbus and "at_console" correctly, the test of comment #21 might be useless, because of the order policies are being applied. As stated in the dbus-daemon man page, the last applied rule matches, and user= rules are applied before at_console=true rules. So, this means if I am root and at_console, the deny rule of "at_console" would overwrite a possible allow rule for user root. It would be nice to see the state of at_console in the reject message. Is there any way to see all rules dbus applies? I tried DBUS_DEBUG=1, but this did not help. In the reject messages, the "XX matched rules", but I want to see them in detail (including "at_console" state). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c30 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |georgmueller@gmx.net --- Comment #30 from Ludwig Nussel 2009-03-22 13:12:52 MST --- (In reply to comment #25)

Hm, I have done the upgrade, my girlfriend has done it, her laptop worked, mine did not (both using kde 3.5 with knetworkmanager).

I ran a "diff -r /etc/dbus-1/" and found no differences instead of some missing/new files from different packages (kerneloops, gnome clock, ...).

I am not sure how this can be possible...

Interesting. Do the systems use different filesystems? What's the output of ls -1U /etc/dbus-1/system.d/ on both system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|georgmueller@gmx.net | AssignedTo|lnussel@novell.com |hschaa@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User felix@derklecks.de added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c34 Felix Möller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felix@derklecks.de --- Comment #34 from Felix Möller 2009-03-23 09:19:12 MST --- I am experiencing the same bug. i | NetworkManager | package | 0.7.0.r4359-15.1.1 | i586 | updates i | NetworkManager-glib | package | 0.7.0.r4359-15.1.1 | i586 | updates i | NetworkManager-gnome | package | 0.7.0.r1053-11.1.1 | i586 | updates i | NetworkManager-gnome | patch | 563 | noarch | updates i | NetworkManager-vpnc | package | 0.7.0.r4274-1.23 | i586 | oss111 i | NetworkManager-vpnc-gnome | package | 0.7.0.r4274-1.23 | i586 | oss111 i | dbus-1 | package | 1.2.10-5.3.1 | i586 | updates i | dbus-1 | patch | 488 | noarch | updates the patch from comment #20 allows me to use my wlan again. My system is 32bit. I am using KDE4 and nm-applet. It has to be noted that I have downgraded from factory some weeks ago... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c36 --- Comment #36 from Tambet Ingo 2009-03-23 09:25:41 MST --- Just coping the file over doesn't do anything. Rebooting is the simplest way to make sure the new configuration is actually used. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c38 --- Comment #38 from Helmut Schaa 2009-03-23 10:12:45 MST --- Could everyone please check if a directory called root is located in /var/run/dbus/at_console? Removing that directory (followed by dbus, NM and KNM restart) should result in a working system again. Ludwig, if one was/is logged in as root dbus will treat root as at_console and will in turn deny access to the Connection.Secrets interface. Not sure how to handle that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User georgmueller@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c40 --- Comment #40 from Georg Müller 2009-03-23 10:19:47 MST --- As an addition: If someone (for what reason ever) tries to run a network manager client logged in as root, he will fail with the current set of rules. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User georgmueller@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c42 --- Comment #42 from Georg Müller 2009-03-23 10:34:01 MST --- (In reply to comment #41)

(In reply to comment #39)

...

Solution: Do not use deny rule in at_console, only in context=default and an allow rule for root. That is what I have done with my dbus changes. No more problems :)

This might open the security hole again.

Why? Rules are applied in the following order (from dbus-daemon man page): - all context="default" policies are applied - all group="connection's user's group" policies are applied in undefined order - all user="connection's auth user" policies are applied in undefined order - all at_console="true" policies are applied - all at_console="false" policies are applied - all context="mandatory" policies are applied So, if there is a deny rule in context="default" and no other rule that is matching (you are not root and do not get the allow), then nothing else happens. To minimize the security risk. a much more transparent configuration is very helpful. That means, checking one file instead of 2, 3 or 4 files helps here (since you see on one look what you allow/deny instead of cross-checking with other files). Couldn't we get rid of the client config files at all and define it in a generic way for all nm clients? For the NetoworkManagerUserSettings, I have done it with the nm-user-settings.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c44 --- Comment #44 from Helmut Schaa 2009-03-23 12:55:04 MST --- When /var/run/dbus/at_console/root is present I'm additionally not able to trigger suspend with kpowersave due to dbus preventing the method call. Hence, I'd say this issue affects more apps than just KNM and changing the configuration files just works around the real cause. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User georgmueller@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c46 --- Comment #46 from Georg Müller 2009-03-23 15:53:59 MST --- I see no connection to the kpowersave problem, because there is no special configuration file for kpowersave (or can you please point me to that). As an additional note:

From a logical point of view, at_console=true should only extend priviliges and not restrict them. So, deny rules in at_console=true sections do not make sense to me. They should be done at the lowest level (context=default).

Regarding nm at root login - could it be possible that NM uses NetworkManagerSystemSettings instead of NetworkManagerUserSettings if you log in as root? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c48 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |mvidner@novell.com Info Provider|lnussel@novell.com | AssignedTo|hschaa@novell.com |tambet@novell.com --- Comment #48 from Ludwig Nussel 2009-03-24 08:10:03 MST --- Do'h! Now this finally all makes sense. I wonder why I didn't see this before. Of course Georg is right. NetworkManager which runs as root sends a request over the bus. Now if root for whatever reason is at_console the policy for at_console overrides the policy for user root. at_console is now allowed to read secrets -> ouch. That's not a knetworkmanager specific problem. There are two possible solutions to this problem AFAICS: a) remove the deny rules for secrets and implement access control in the applets b) instead of the send_destination rule that allows all interfaces plus the deny rule for secrets use allow rules for individual interfaces only. This way the deny rule could be at context=default or omitted. In any case we need to update knetworkmanager, nm-applet and cnetworkmanager. so this is probably a good opportunity only ship one applet config only (bug 476502). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c50 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #280928|0 |1 is obsolete| | Attachment #280944|0 |1 is obsolete| | Attachment #281182|0 |1 is obsolete| | Attachment #281225|0 |1 is obsolete| | --- Comment #50 from Ludwig Nussel 2009-03-24 09:48:19 MST --- Created an attachment (id=281578) --> (https://bugzilla.novell.com/attachment.cgi?id=281578) proposed config for method b) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User Larry.Finger@lwfinger.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c52 --- Comment #52 from Larry Finger 2009-03-24 13:10:17 MST --- Created an attachment (id=281669) --> (https://bugzilla.novell.com/attachment.cgi?id=281669) Patch for knetworkmanager.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User georgmueller@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c54 --- Comment #54 from Georg Müller 2009-03-24 16:21:43 MST --- The patch of comment #50 is only for nm-applet. Any NM client does not work if there is _any_ rule which denies access for at_console. That is why you had to rip it off knetworkmanager.conf and why bug 476502 exists. These two bugs should be closed in the same step to avoid further confusion or a new issue like that in the future. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c56 --- Comment #56 from Ludwig Nussel 2009-03-25 03:11:56 MST --- Ok. I'm fine with either solution as long as we can somehow get it quickly as people out there are yelling at us already :-) So is there a chance to have the code changes applied and packages submitted to all distros within this week? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c58 --- Comment #58 from Helmut Schaa 2009-03-25 03:29:17 MST --- But KNM3 and KNM4 need the same checks too. However, I agree that removing the at_console policy is a bad idea. (In reply to comment #55)

it's probably harder to maintain to list all allowed interfaces, just to disallow one.

I'd argue that it is more secure to just open single interfaces instead of opening all interfaces and deny only a specific one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User wstephenson@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c60 --- Comment #60 from Will Stephenson 2009-03-25 04:55:45 MST --- I'm sorry to be late to this party. I'd prefer not to do user checking in applet code - it will be harder to fix or workaround the next time dbus access policies change or across different distros. Is there no way that the user can GetSecrets on their own dbus interface within the limits imposed by dbus' security policy interpretation order with the config proposed in #50? Is there a need to Get your own Secrets? Currently both applets and their editor processes are using desktop-specific storage to communicate settings, not GetSettings/Secrets and UpdateConnection - in any case, without a NetworkManagerSettings.AddConnection method, we cannot manage connections purely over dbus. Apart from GetSecrets is there any other reason #50 is not acceptable? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User georgmueller@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c62 --- Comment #62 from Georg Müller 2009-03-26 07:55:20 MST --- I don't see Helmut saying it does not work. There was one point that the patch of comment #50 was not enough, because there were other config files causing the problem (knetworkmanager.conf, comment #53). Regarding comment 55 and comment #60: I don't see a need to get your own secrets, consider NetowrkManagerUserSettings as an interface for NetworkManager (the daemon) only. So a deny by default and allow as root is a good solution here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=486267 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=486267#c64 --- Comment #64 from Tambet Ingo 2009-03-31 03:47:51 MDT --- Some updates... This is not a problem for the majority of distributions because of two reasons: First, root logins are disabled on Ubuntu/RH/... and second, there's a specific check in the script that creates the /var/run/dbus/at_console/$username (it's a different path on other distros, but used for the same thing) to never create it for root. Upstream NM wasn't very interested in these changes, mainly to have one common conf file for distros that still use the old (insecure) DBus and things work just fine now. It looks like the new configuration file Ludwig wrote will get accepted, so let's go with this. Ludwig, could you add a 'rm -rf /var/run/dbus/at_console/*' to one of the startup scripts (either CK or dbus I guess) to make sure there's no stale directories there? The problem with these is that whoever is logged in during a system freeze or hard reset, these users would always be considered as at_console="true" by DBus. Technically, that would solve this bug as well, so do we want to proceed with NM applet .conf file changes as well? Do we want to move the new configuration to NetworkManager package now for released distros? In that case we need to sync the updates of NetworkManager and all the applets to all distros... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.