Securing logs before posting

[cowszero 0]

I've read the topic How to Report a Problem in which it describes posting logs for support issues. Logs are to be uploaded, zipped only if necessary, or accessible by link which does not require a login. Makes sense from a usability stand port: put as few barriers in place as possible so that the logs can be quickly and easily examined.

 

But even a cursory reading of the log files shows a good deal of private information (public IP addresses and server names, open port numbers, library contents, etc.). I know we are supposed to be one big happy family but the truth is we are mostly strangers and sharing this level of detail public is risky behaviour.

 

How do most people handle (or just feel about) this? I am not trying to be difficult, especially as I am about to ask for help from the community. I just want to be sensitive to the risks involved with sharing log files.

 

 

Edited February 22, 2017 by cowszero

[Latchmor 584]

All I've done in the past is take a copy of the log, open it in Notepad2, find and replace all instances of user/IP etc.

 

Couldn't really do that for library items though.

 

Sent from my OnePlus 3T

[Jdiesel 1431]

I find it is a pain to replace IP address, links, and plain text passwords in my M3U urls so I usually just PM to the Luke or EBR. 

[blade005 185]

I choose to scrub mine of any IP and Name information and use Paste2.org to create an easily accessible link for the Devs to review.

 

Drop the log contents into Notepad, do a REPLACE ALL for any IP or Name information and then drop that in Paste2.org and create a link for Devs.

Edited February 23, 2017 by blade005

[Rumbaar 13]

Yeah, I was worried about this myself when I noticed it had my DDNS address in my logs.  So I've deleted them from the forums.  I'll have to be more mindful in the future.

 

But if could, an support export function within EMBY that did the automatic scrubbing of logs prior to extraction would be ideal.

[Abobader 3464]

Good day,

 

Well it easy to create a sub-forum or a forum if Luke and Ebr see it a good idea, that only whom submit a thread can see it together with the admin/dev team.

 

After that he simply can post that thread link.

 

My best

[QuasiZ 4]

Probably somewhat easy with SED and some regular expressions. Finding out which strings exist and may contain details you don't want to reveal is the hard part. Making it user-friendly slightly less so.

 

Right now using SED (GnuWin32) I think I've got all my logs clean as can be (userdata path, network info, media folders, media files, external service lookups and select external service error messages), but that's without debug being on and who knows what other messages could be there. Most could probably be found in the source files (just figure out wherever it writes to a log file), others depend on external services' responses. E.g. "Info App: TVDb Provider - X did not match Y"