Bugs reports should include syslog warnings or not?

[Jeremy Bicha]

On Sat, Mar 17, 2018 at 7:51 PM, Robie Basak <robie.basak at ubuntu.com> wrote:
> On Sat, Mar 17, 2018 at 06:09:25PM +0100, Sebastien Bacher wrote:
>> The report pointed out that private info have been included in a report
>> through JournalError.txt, and the solution applied was to change apport
>> to include errors level messages only and not warning.
>
> IMHO, not logging warning level messages is too blunt an instrument to
> fix this bug. And it doesn't really fix it either - the next time it
> might be that private data is leaked via an error rather than a warning.
>
> IMHO, private information should never be leaked to logs by default, by
> being obfuscated at source. An exception might be if a developer
> explicitly and specifically turns on such an option having had the
> opportunity to understand the consequences and take the necessary care.

One particular class of private info I've seen in the systemd journal
is file names of files that tracker fails to index.

File names can be very sensitive. And yet, it seems to me like it's
appropriate for tracker to log the file name as a warning.

Maybe apport should exclude tracker warnings by default for bugs that
aren't related to tracker?

Thanks,
Jeremy Bicha