You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussing with Matthias about a potential issue in QGIS Server where an expression can be used to disclose information about the server environment we came into the situation where we cannot publicly discuss about the issue because we don't have a patch or a mitigation procedure yet.
This made me think that we should have a standard procedure about how we address these cases, I don't have a proposal but I think that maybe we could have a reserved way to communicate with a restricted group of developers (security team) and perhaps even a dedicated budget for this kind of issue.
I'm thinking at a budget because it may happen that the patch (like in this case) is not trivial.
I remember we discussed something related to security disclosure in the past, maybe I just forgot about it and we do already have an established procedure, I apologize if that's the case.
The text was updated successfully, but these errors were encountered:
Discussing with Matthias about a potential issue in QGIS Server where an expression can be used to disclose information about the server environment we came into the situation where we cannot publicly discuss about the issue because we don't have a patch or a mitigation procedure yet.
This made me think that we should have a standard procedure about how we address these cases, I don't have a proposal but I think that maybe we could have a reserved way to communicate with a restricted group of developers (security team) and perhaps even a dedicated budget for this kind of issue.
I'm thinking at a budget because it may happen that the patch (like in this case) is not trivial.
I remember we discussed something related to security disclosure in the past, maybe I just forgot about it and we do already have an established procedure, I apologize if that's the case.
The text was updated successfully, but these errors were encountered: