Running processes, including parameters passed to them. Hardware information, but come on - it's computer support. Attached devices, including USB, but not what's on them with the exception of the formerly mentioned folders. TECHNICALLY, using IP configuration an attacker can gain a better understanding of your internal infrastructure etc etc but honestly if you're running unRAID and not some blackbox OS you're not really enough of a target that this information is likely to be damaging, valuable, or identifying in any way. boot, /boot/config, /boot/config/plugins, /boot/extra, /boot/syslinux, /var/log, /var/log/plugins, /var/log/packages, /tmp If you try to hide extra things there, we can see their names and file properties. Important folders in a few places have diagnostic file listings. ![]() NFS shares can expose the name of the share accidentally. Non-system shares' filenames are masked and internal contents are fairly privacy-safe. Docker logs: Possible these could contain privacy-violating information, depending on your definition of privacy-violating, your containers, how they're configured, etc etc - in general the worst thing here is someone might see a password that a container is repeating plaintext, which is kind of frowned on to begin with so you should be safe. If I understand correctly at this juncture, it's an internal file containing, essentially, your disk assignments, in a format prepared for part of the parity system, to over-simplify it) Whatever super.dat is, it's 4kb and seems to have a structure containing the names your disk controller assigns to your disks, and other data. (Confirmed by trurl below. where you're sending syslogs, if you are Folder names specifically of storage locations for docker/VM configuration data Machine name, network domain name, timezone, machine's IP configuration ![]() Not many people use them, you know if you have it. ![]() Where you keep your encryption keyfile, but not the file or what's in it, if you're using one. (NOTE - I'm scanning my own diagnostic live, YMMV and I might miss something, I'd advise skimming it yourself just so you know for sure.) What we can see that Could Matter(tm) regarding privacy explicitly: * AS OF UNRAID 6.8.3 Here's a breakdown, but it's mostly human-readable and broken into easily named, sorted files - it's not for machine processing, it's for the support staff to parse by hand. Just for future reference in supplying the forum with a diagnostic.zip file are there any recommended edits that should be made before uploading to preserve privacy?įantastic question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |