all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: rms@gnu.org
Cc: acm@muc.de, 13141@debbugs.gnu.org, drew.adams@oracle.com,
	emacs-devel@gnu.org
Subject: Re: please review bug #13141
Date: Mon, 21 Jan 2013 11:39:46 +0900	[thread overview]
Message-ID: <87ehhf5kel.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1TwzpU-0007Of-Pd@fencepost.gnu.org>

Richard Stallman writes:
 >     I've had at least half a dozen cases
 >     where users deleted automatically added information which I then
 >     requested -- to no avail, since the reporters never responded.
 > 
 > To go out of their way to delete it makes me wonder why.  Maybe it was
 > a valid reason.  Could it be that there was something private in that
 > information which they specifically did not want to send?

Some of it, yes, such as the keystroke log.  The list of shadowed
libraries would only very rarely be considered sensitive.  (For
example, if the user had modified a corporate internal library and was
shadowing it in her load-path.)

The cases of deletion I'm referring to were done with a chainsaw
rather than a scalpel.  I've always assumed the motive was a misguided
attempt to either localize the information to what they user thought
was a bug or to save bandwidth, but you could be right: they were
worried about the possibility of sensitive information leaking, and
chose to deal with the issue brutally.

 > Because of this consideration it would not be right to hide that
 > information.  We should not try to trick our users into sending us
 > something they did not want to send.

Agreed.  I withdraw the suggestion of appending the information after
the user hits "send".  Of course attaching it via MIME etc would be
not be the default (my phrasing is at fault here, I was writing from
the point of view of appeasing Drew and Fuqiao).




  parent reply	other threads:[~2013-01-21  2:39 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 23:10 please review bug #13141 Drew Adams
2013-01-19 23:20 ` bug#13141: " Alan Mackenzie
2013-01-19 23:20 ` Alan Mackenzie
2013-01-19 23:59   ` Drew Adams
2013-01-20  0:12     ` Xue Fuqiao
2013-01-20  0:12     ` bug#13141: " Xue Fuqiao
2013-01-20  7:16     ` Stephen J. Turnbull
2013-01-20 10:33       ` bug#13141: " Xue Fuqiao
2013-01-20 10:33       ` Xue Fuqiao
2013-01-20 17:08       ` Eli Zaretskii
2013-01-20 17:08       ` bug#13141: " Eli Zaretskii
2013-01-20 18:41       ` Richard Stallman
2013-01-20 21:21         ` Drew Adams
2013-01-21  1:03         ` bug#13141: " Dmitry Gutov
2013-01-21  1:03         ` Dmitry Gutov
2013-01-21  3:02           ` Stephen J. Turnbull
2013-01-21  3:26           ` Stephen J. Turnbull
2013-01-21  2:39         ` Stephen J. Turnbull [this message]
2013-01-21  2:39         ` Stephen J. Turnbull
2013-01-20  7:16     ` Stephen J. Turnbull
2013-01-20 10:50     ` Alan Mackenzie
2013-01-20 12:02       ` Xue Fuqiao
2013-01-20 20:27         ` Glenn Morris
2013-01-21  2:52           ` Stephen J. Turnbull
2013-01-20 12:02       ` bug#13141: " Xue Fuqiao
2013-01-20 17:40       ` Drew Adams
2013-01-20 17:40       ` Drew Adams
2013-01-21  4:24         ` bug#13141: " Drew Adams
2013-01-21  4:24         ` Drew Adams
2013-01-20 10:50     ` bug#13141: " Alan Mackenzie
2013-01-19 23:59   ` Drew Adams
2013-01-19 23:21 ` Drew Adams
2013-01-19 23:21 ` bug#13141: " Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2013-01-21  7:18 Andrey Paramonov
2013-01-21 15:05 ` Drew Adams
2013-01-21 15:26   ` Harald Hanche-Olsen
2013-01-21 17:29     ` Eli Zaretskii
2013-01-21 22:20     ` Drew Adams
2013-01-22  4:15       ` Xue Fuqiao
2013-01-22  6:40         ` Drew Adams
2013-01-22  7:51           ` Xue Fuqiao
2013-01-22 15:10             ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ehhf5kel.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=13141@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.