![]() ![]() Security/Privacy/some degree of anonymity are all the reasons why many of us flocked to Jitsi so anything that even borders on the fringes of discomfort in that area is undesirable.Īgain, if we can have an option to turn this on/off, that would be great. Yes, they may still be able to get them through other means, but we shouldn't be providing it to them easily. The fact is, this information does not need to be made so accessible to users. It's the same reason why people often opt for VPNs at home. You're more knowledgable in this area, so I don't need to elaborate on how this could be a problem. So the server IP is often equivalent to our personal IP. ![]() Quite a few of us run our servers in-house. There could also be the option to just make this feature a choice to implement? Maybe a check like "Show Log Link"?īut so far you haven't provided any proof of problems this may I thought I mentioned how this is a concern in my previous comment. Perhaps they can just be stored on the server somewhere under a directory like "Meeting Logs" instead? That way, the server administrator can quickly access them, if needed, for troubleshooting client issues (even so, I still think the browser console logs would prove to be more useful in that instance). I'm not arguing against their presence, I'm arguing against their easy accessibility by mere meeting participants. These logs could be useful, but strictly on an administrative level. It's not that hard to track a person's address using their IP, for instance. For those who host their servers in the Cloud on a paid service, the risks may be less, but those of us who have our servers in-house run a greater risk. There are intrinsic risks in having an exposed IP. Not to say the information in the log is not useful for troubleshooting purposes. I'm nowhere near being an expert on these things, but the information in the log doesn't quite mimic the information in the browser console. Hmm.mm so I'm not sure about the strength of this use case. The use case is simple: make it easier for users to give us information that can help us fix their problems. At the very least, it should be an administrative feature it's hard to see the use case for making this available to meeting attendants. This log file, while potentially useful to the moderator, serves no useful purpose to the ordinary user and creates an easy trove of information for a potential bad player. Operating System: Ubuntu Server LTS 20.04.Only the Moderator should see and have access to save meeting logs Actual behavior:Ĭlicking "Save Logs" automatically downloads a log of the meeting details in json format to the default download directory of the user. Click on the "Save Logs" link in the user connection details pop-up to download a json file. ![]() While this may be a useful feature for the admin-like 'moderator', it creates unnecessary exposure when made readily available to all users in the meeting. This log contains the server name, server IP address, participant's IP addresses e.t.c. The latest version of Jitsi Meet has a "Save Logs" feature that generates a json file with a bevy of technical information about the meeting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |