[issue1138] grml should not send any data w/o _asking the user first_

[Ulrich Dangel]

Ulrich Dangel <mru at grml.org> added the comment:

* Daniel Mitzlaff wrote [23.01.12 19:03]:
> The actual grml release 2011.12/Knecht Rootrecht sends some data @boot to its
> servers here. Well, it's fine. Mostly. But in some countries this can violate
> several Laws, and more on, it's not fine to give the user a software that phones
> to home immediately - and whitout notice! - after boot.

We tried to get feedback and information from the users. We introduced
grml-feedback which basically was never used. Therefore we decided (be
aware that the decision was _not_ unanimous) to gather data. The current
data is:
 * remote/local boot
 * screen resolution
 * flag if your cpu supports 64bit
 * anonymized boot parameters

Do you see any issue with this data? We currently don't track the users
as the data is currently only send at startup (grml-autoconfig to be
precise) and don't log if/what options you choose otherwise (for example
grml-quickconfig) and does not use any machine specific id like
/var/lib/dbus/machine-id

The logic is also simple it just tries to send the data at startup. This
means if you don't have any network connection while booting the data
won't be send.

> Please give the user a clear hint about this on the download dialogue and/or -
> more important - change the behavior of this feature from a cryptic opt-out
> variant via "nostats" cheatcode to a transparent opt-in feature, eventually via
> the quickconfig menu.

grml-quickconfig is the wrong place as it is an optional component and
can be skipped (and we still want stats from user which choose to
disable grml-quickconfig). It would also not really work for blind users
as they would have to explictly select the bootoption without the
possibility to read the text. Stopping during the bootprocess and asking
questions is also not an option as grml is used for unattended
deployments.

OTOH bootopions are the default way to change and modify the behaviour
of grml. This is nothing cryptic and it is the standard way to alter
Grmls behaviour.

Please suggest an working alternative. Adding it to grml-quickconfig is
IMHO not a viable option. Asking the user once before starting the shell
may be an option but is rather intrusive.

cheers,
Ulrich

----------
messages: 4285, 4286
nosy: hackbyte
priority: urgent
status: chatting
title: grml should not send any data w/o _asking the user first_

_____________________________________
GRML issue tracker <bts at bts.grml.org>
<http://bts.grml.org/grml/issue1138>
_____________________________________