Comments you submit will be routed for moderation. If you have an account, please log in first.

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#90 closed enhancement (wontfix)

Debug Output without private Data

Reported by: opiopi Owned by:
Priority: low Milestone:
Component: undefined Version:
Severity: major Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:


I think it's a good idea to introduce a debuglevel which doesn't print private Data (e.g. Mailadresses, Passwords) in Debug reports, because i do not want to spread my private datas if i post a bugreport.

Moved from SF:

Attachments (0)

Change History (8)

comment:1 Changed 6 years ago by damato

  • Component changed from stable build to undefined

comment:2 Changed 6 years ago by damato

  • Cc yamos-svn@… removed

comment:3 Changed 6 years ago by damato

  • Milestone set to YAM 2.7
  • Priority changed from undecided to low
  • Reporter changed from opiopi@… to Opi
  • Severity changed from major to trivial
  • Status changed from new to pending

I understand your reasoning, but I think we already changed something about that some time ago. Thore? any more information on that?

Not a separate debug option, but we did something to not expose that critical information per default. So in case you still see some private data exposed which should not be in the standard debug output please bring up each case here separately and point your finger at it.

comment:4 Changed 6 years ago by Opi

  • Status changed from pending to new

IIRC here was a change which doesn't show a passwort in plain text
but IMHO all E-Mail adresses should also not displayed in such
bugreport because they may be available for public in the www.
So replace all characters after a '@' until the next whitespace
should fulfill this request.

comment:5 Changed 6 years ago by tboeckel

I changed the debug output to change passwords into "XXXX". Other stuff like mail addresses, real names, etc are still printed as they are.

comment:6 Changed 6 years ago by damato

  • Milestone YAM 2.7 deleted
  • Resolution set to wontfix
  • Severity changed from trivial to major
  • Status changed from new to closed

Ok, I also think it would make the debugging a lot more complex if we would have to identify all situations where email adresses are output. The current solution with prevent at least the output of passwords should be enough IMHO. Therefore I am closing this ticket.

comment:7 Changed 6 years ago by damato

  • Reporter changed from Opi to opi

comment:8 Changed 6 years ago by damato

  • Reporter changed from opi to opiopi

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Frank Weber(Reporter)