veyepar: Quit logging! (or, data minimization in Debian)

Author(s):	Daniel Gillmor
Location	Room 327/8
Date	aug Tue 26	Days Raw Files
Start	13:30	First Raw Start	13:24
Duration	00:45:00	Offset	0:05:04
End	14:15	Last Raw End	14:16
Chapters	00:00
Total cuts_time	45 min.

https://summit.debconf.org/debconf14/meeting/70/quit-logging-or-data-minimization-in-debian/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

assets release.pdf Quit_logging_or_data_minimization_in_Debian.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Computer users leave traces of data on local and remote machines that record their activity.  These records can cause problems for people who do not want their activities tracked, and they facilitate both mass and targeted surveillance.  Service operators are put in an uncomfortable position because of the existence of this data: they have a responsibility to protect their users, but they may also be at risk of compelled data disclosure against their users' interests.

One way to avoid this problem is to reduce or eliminate the quantity of data generated and stored by any system by default in its regular operations.  If you don't have the data, it can't be used against you or against your users.

Debian is in a good position to shape norms around this -- we can configure default logging levels; we can tune what specifically gets logged, and we can determine how long logs are kept by default.

This is a discussion about how to achieve the goal of data minimization within Debian, while considering the tradeoffs and consequences of this sort of change.

We should cover at least:

* what kind of statement (if any) about default levels of logging for debian packages might belong in Debian Policy
 * points of convenient control for minimizing logging on standard debian systems
 * different system logging architectures and how they can support data minimization
 * how to provide both data minimization and useful debugging information at a system level

Comment:

production notes