[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #11 from Sune Vuorela --- Git commit 3518099a08f0b129e6be8c8216ecb5fc0bf38273 by Sune Vuorela. Committed on 20/02/2024 at 13:57. Pushed by sune into branch 'release/24.02'. Better user strings for signature settings M +9-4generators/poppler/pdfsettingswidget.cpp https://invent.kde.org/graphics/okular/-/commit/3518099a08f0b129e6be8c8216ecb5fc0bf38273 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #10 from Albert Astals Cid --- Git commit 8a6d86ab1961b51ffc9f86ef2ebcbe86a8d4ae3c by Albert Astals Cid, on behalf of Sune Vuorela. Committed on 19/02/2024 at 21:39. Pushed by aacid into branch 'master'. Better user strings for signature settings M +9-4generators/poppler/pdfsettingswidget.cpp https://invent.kde.org/graphics/okular/-/commit/8a6d86ab1961b51ffc9f86ef2ebcbe86a8d4ae3c -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/928 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #8 from Albert Astals Cid --- NSS is the better name We use the current user Firefox NSS database by default if it exists, but users can select any folder containing an NSS database. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #7 from Sune Vuorela --- (In reply to Ingo Klöcker from comment #5) > I think a good name for the NSS backend depends on how it behaves on > different OSes, i.e. if it uses the Windows/macOS certificate store on > Windows/macOS then "Firefox Certificate store" is probably not a good name. > And I guess most people don't know that Mozilla Firefox was once called > Netscape. Afaik, it still uses the firefox cert store on all platforms. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #6 from Philippe ROUBACH --- (In reply to Ingo Klöcker from comment #2) > Maybe we should change the name of the backend to "GnuPG (S/MIME)" (or > "GPGSM", but many won't understand this) to make this more obvious. "GPG" is > actually very wrong because gpg is the name of the OpenPGP tool of the GnuPG > suite. A good GUI is a teacher GUI. Why not using a text not on the button but beside the option when we select the option. This text would explain what certificate is expected. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #5 from Ingo Klöcker --- I think a good name for the NSS backend depends on how it behaves on different OSes, i.e. if it uses the Windows/macOS certificate store on Windows/macOS then "Firefox Certificate store" is probably not a good name. And I guess most people don't know that Mozilla Firefox was once called Netscape. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #4 from Sune Vuorela --- (In reply to Albert Astals Cid from comment #3) > (In reply to Ingo Klöcker from comment #2) > > Maybe we should change the name of the backend to "GnuPG (S/MIME)" (or > that makes sense, not the first person to be confused by the naming. Sune? Sure. I didn't have any good ideas at the time, but I kind of prepared the code for it https://invent.kde.org/graphics/okular/-/blob/master/generators/poppler/pdfsettingswidget.cpp#L35 If one option should be > GnuPG (S/MIME) what should the other be > Netscape NSS > NSS > Firefox Certificate store -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #3 from Albert Astals Cid --- (In reply to Ingo Klöcker from comment #2) > Maybe we should change the name of the backend to "GnuPG (S/MIME)" (or > "GPGSM", but many won't understand this) to make this more obvious. "GPG" is > actually very wrong because gpg is the name of the OpenPGP tool of the GnuPG > suite. that makes sense, not the first person to be confused by the naming. Sune? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #2 from Ingo Klöcker --- Maybe we should change the name of the backend to "GnuPG (S/MIME)" (or "GPGSM", but many won't understand this) to make this more obvious. "GPG" is actually very wrong because gpg is the name of the OpenPGP tool of the GnuPG suite. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 Sune Vuorela changed: What|Removed |Added CC||k...@pusling.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Sune Vuorela --- the gpg backend setting is still s/mime and not openpgp, so you need s/mime certificates, just like for the nss backend. The pdf standard specifies s/mime for signing pdfs. -- You are receiving this mail because: You are watching all bug changes.
