Dear libreoffice,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1862331

Title:
  [upstream] mozilla cert8.db and key3.db are denied by apparmor

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  New

Bug description:
  libreoffice accesses firefox's cert8.db and key3.db, i have found this from 
apparmor log messages.
  i googled "libreoffice cert8.db key3.db" and have found out that seems 
libreoffice does this by design. see 
https://bugs.documentfoundation.org/show_bug.cgi?id=119811 , 
https://weekly-geekly.github.io/articles/357692/index.html . do you agree with 
this? then there should be allow rule, i think. if you do not, then should be a 
comment and / or deny rule.

  does libreoffice really need write access to these files? i think it
  can potentially add some bad certificates, and some sites would have
  verified sign then, while user has not added it to exceptions.

  i think if user have not secured his master password, it can be
  considered it is ok if some app can access his passwords.

  i think this pages also can be helpful:
  https://stackoverflow.com/questions/45126738/what-is-cert8-db-and-
  key3-db-file , https://developer.mozilla.org/en-
  US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil , these are
  found by googling "cert8.db key3.db". this also can be helpful:
  https://en.wikipedia.org/wiki/Public_key_certificate .

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1862331/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to