Mr. Deslauriers, thank you for explaining. Just so I'm clear: Chromium security fixes are NOT backported like you described as being done for VLC. Instead, you simply update the version (hence, why it can cause other problems/bugs). Don't you think it was a problem to leave security vulnerabilities in place (e.g., compromised CA certificates were blacklisted in the update to 133) just so passwords won't be forgotten (assuming the user even uses the feature)? I understand the inconvenience, but it seems to me some kind of notice/advisory should have been issued to Chromium Universe users if you decided to wait to implement security updates just to retain what amounts to a convenient usability feature. Compromised CA certificates can literally have life and death consequences for people living in dictatorial countries.
Thank you so much for your time. I really appreciate your help and answering my questions :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/760685 Title: Lucid Lynx is not getting VLC security updates -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
