That is really great!
Finally, I get the way to get results of xprop -root | grep XKB and
gconftool-2 -R /desktop/peripherals/keyboard/kbd without explicitly
asking user in every bug report...
BTW, is shipping information from gconf considered as a security problem?
Thanks, lads
Sergey
Olav:
Isn't it possible to install .desktop files in the user's $HOME
directory? If someone were to trick a user into installing a
.desktop file with a script that does something malicious, is there
anything to protect the user from the malicious thing happening the
next time the program
On Thu, Nov 30, 2006 at 12:11:57PM -0600, Brian Cameron wrote:
Olav:
Isn't it possible to install .desktop files in the user's $HOME
directory? If someone were to trick a user into installing a
.desktop file with a script that does something malicious, is there
anything to protect
Olav:
Perhaps a decision about how it should work should be made and
documented so people understand how it is intended to work?
How what should work? Bug-Buddy or the bug-buddy info in the .desktop
files?
Information about how data is collected, what rules are used to ensure
the right
Brian Cameron wrote:
Why not just add a GConf preference to bug-buddy so that users can
simply turn off this feature if they don't want it to be on. Perhaps
the first time data is forwarded a pop-up can be displayed asking the
user if they want this feature on or off. This would be most
On Thu, Nov 30, 2006 at 01:15:26PM -0600, Brian Cameron wrote:
Perhaps a decision about how it should work should be made and
documented so people understand how it is intended to work?
How what should work? Bug-Buddy or the bug-buddy info in the .desktop
files?
Information about how data
On Thu, Nov 30, 2006 at 02:29:38PM -0500, Havoc Pennington wrote:
Brian Cameron wrote:
Why not just add a GConf preference to bug-buddy so that users can
simply turn off this feature if they don't want it to be on. Perhaps
the first time data is forwarded a pop-up can be displayed
Olav:
Information about how data is collected, what rules are used to ensure
the right information is collected, how it can be configured, and what
efforts are taken to ensure that the user's privacy is respected should
all be documented, I think.
So info for the paranoia user? Well, it
Hi Brian,
On 11/30/06, Brian Cameron [EMAIL PROTECTED] wrote:
So info for the paranoia user? Well, it is going to a public bugtracker.
This probably should be made clearer so that user can just
cancel/disable the entire bug-buddy.
I think it is good to document how this works so that
James Henstridge wrote:
On 26/07/06, Fernando Herrera [EMAIL PROTECTED] wrote:
On 7/26/06, James Henstridge [EMAIL PROTECTED] wrote:
1. gnome-settings-daemon is modified to set the gtk-modules XSETTING,
based on the existing gconf key. If accessibility is enabled, it sets
it to
Elijah:
Stack traces can already potentially contain private info. The
current method is:
1) Program crashes
2) Bug-buddy is launched, gathers data, and notifies the user what happened
3) Bug-buddy notifies the user that sensitive data may have been
collected and lets them know how to
11 matches
Mail list logo
