https://bugs.freedesktop.org/show_bug.cgi?id=51819
--- Comment #55 from Markus Mohrhard <[email protected]> --- (In reply to comment #53) > Great to hear, that Matúš is working on it "officially"! (really did not get > it until now) > > If I can help in anything (testing, etc.) just let me know! (except > compiling for which sadly my current machine is way too old - maybe after > getting a newer one somehow...) > > BTW I find your strategy really great (and practical) to try to get the > users involved into the community and the developing process through the > issues important for them. > > Just a small remark: security issues may not be the ideal candidates for > this purpose, maybe they need a bit more special handling (quicker response, > more focus from experienced developers, etc.) Just to clarify something here. Let us not call this issue a security issue. It is maybe a privacy issue if you want to give this bug a special name. Accusing us of not caring or not caring enough about security issues is not winning much friends. As Michael already mentioned earlier it has been analyzed by the security team in the past and been classified as normal bug or if you want to call it like that, "privacy" issue. I hope that it makes a bit clearer why this bug has not seen the attention that you would have preferred. There will always be bugs where users and developers have different expectations but it would be nice to not accuse us of not caring enough. > > But I personally really enjoyed browsing the code through the web interface > and trying to spot the problem, and surely will try to do this for other > issues too, so the strategy definitely functions :-) > > Thanks for working on this issue! (and sorry for the "shrillness") Thanks a lot for working on a fix. As you hopefully see it is much more productive to look at an issue yourself than trying to force other people to fix your bugs. As you might have seen if you participate in fixing a bug we'll assist you bug just asking other people to fix it does not work. Your patch looks correct if it works. If it still does not work you would need to debug it a bit and see where we either expect a SID_PASSWORD or somehow still clear the SID_ENCRYPTIONDATA. If you are intersted in these kind of tasks you can try to remove the remaining SID_PASSWORD which might hide a few more similar problems. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
