[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-21 Thread Launchpad Bug Tracker
This bug was fixed in the package gcr - 3.41.1-4 --- gcr (3.41.1-4) unstable; urgency=medium * debian/patches/gitlab_meson_resource.patch: - cherry pick a fix proposed upstream to fix a regression in the port to meson where one the gresource files isn't include anymore whi

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-20 Thread Sebastien Bacher
Right, I do plan to cherry pick the gnome-keyring change at some point, I just started with gcr while waiting to see if a gnome-keyring upstream maintainer is still active to review the change -- You received this bug notification because you are a member of Desktop Packages, which is subscribed

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-20 Thread Damjan Jovanovic
Pleasure Sebastien, that's how open-source works, we help each other and all win :-). I'm glad you are picking it up at the distro level, but that gcr-3 patch alone won't fix this issue, as it only comes into play after gnome- keyring-pkcs11.so is loaded, which won't happen without the gnome- keyr

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-20 Thread Sebastien Bacher
Thanks Damjan for the investigation work and the fixes, I've cherrypicked the gcr fix and uploaded to Debian now (which will sync to Ubuntu later today). I would prefer to see an upstream review for the keyring change before distro patching that one since the situation there is a bit more complica

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-19 Thread Damjan Jovanovic
There are at least 2 bugs here. One is that gnome-keyring doesn't whitelist Seahorse in /usr/share/p11-kit/modules/gnome-keyring.module, so its PKCS#11 module doesn't load inside Seahorse at all, cutting off Seahorse from the user's certificates. A merge request (with a patch to remove that whole

Re: [Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-18 Thread Meluco
Thank you, very, very, much! O 19:25, luns, 18 de dec. de 2023, Angelo Giacomini Ribas < 1771...@bugs.launchpad.net> escribiu: > May the Luck be with you! > > On Mon, 18 Dec 2023, 14:35 Damjan Jovanovic, <1771...@bugs.launchpad.net> > wrote: > > > I am personally working on this issue, you can fo

Re: [Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-18 Thread Angelo Giacomini Ribas
May the Luck be with you! On Mon, 18 Dec 2023, 14:35 Damjan Jovanovic, <1771...@bugs.launchpad.net> wrote: > I am personally working on this issue, you can follow my progress on > https://gitlab.gnome.org/GNOME/seahorse/-/issues/205 > > So far it looks like there are a number of bugs; a simplifie

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-12-18 Thread Damjan Jovanovic
I am personally working on this issue, you can follow my progress on https://gitlab.gnome.org/GNOME/seahorse/-/issues/205 So far it looks like there are a number of bugs; a simplified picture looks something like this: seahorse: gcr_import_button_add_parsed()gnome-keyring: gkr-tool-impo

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-11-20 Thread erny
Had the same problem, trying to sign documents with libreoffice, and used the same method to set the certificates store path in libreoffice (tools / options / security / certificate button, and set the path (manual) to: ~/.pki/nssdb Now I can manage my certificates with google chrome (no snap vers

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2023-06-19 Thread Mark - Syminet
Hi, thought I'd chime in here as just ran into the same issue on debian bullseye. Obtained an oh-so-precious "mycert.p12" file and resolved thus: Step 1: a) In Firefox ESR: Settings -> Privacy and Security -> View Certificates button (way down at the bottom). b) "Certificate manager" popup wind

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-11-08 Thread Angelo Giacomini Ribas
** Bug watch added: gitlab.gnome.org/GNOME/seahorse/-/issues #205 https://gitlab.gnome.org/GNOME/seahorse/-/issues/205 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Ti

Re: [Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-11-08 Thread Angelo Giacomini Ribas
https://gitlab.gnome.org/GNOME/seahorse/-/issues/205 On Tue, 8 Nov 2022, 07:11 Angelo Giacomini Ribas, < angelo.ribas@gmail.com> wrote: > I've been using Fedora for tha last few years, and I confirm that the bug > isn't exclusive in Ubuntu, is upstream. > > Sadly, I'm obliged to keep Window

Re: [Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-11-08 Thread Angelo Giacomini Ribas
I've been using Fedora for tha last few years, and I confirm that the bug isn't exclusive in Ubuntu, is upstream. Sadly, I'm obliged to keep Windows installed in my computer in dual boot mode due exclusively to this issue, otherwise I'd diched Windows completely. Other people, on the other hand,

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-11-08 Thread Sebastien Bacher
Ubuntu doesn't have one actively working on that component, the right place to fix the issue would be upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seah

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-11-04 Thread Matej Kovacic
This is a real shame. I am using Ubuntu 22.10 with Seahorse 42, and the problem still persists. The bug is several years old and there is no solution yet. The world is going paperless, people want to use their Linux systems for serious work and business, but certificate management is not supported

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-03-01 Thread FOSS victim #187345
I am still having the same issue, along with many others issues lol... I have stopped trying to find any useful answers, as most sources seem content with being in control, obfuscating, complaining about people's questions or just plain bullying. I actually saw this as advice in a 'support forum'

Re: [Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-02-01 Thread Angelo Giacomini Ribas
I reported this bug 4 years ago. I'm a lawyer, and I depend on digital certificates and signatures to do my job. From 2012 to 2017 I had no problem doing that using Ubuntu/Seahorse. However, since upgraded to Ubuntu 18.04 LTS, found no linux distribution able to import pcks12 certificates anymore.

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-02-01 Thread loizbec
Same Problem : Linux Mint 20.3 Una / Cinnamon 5.2.7 / Seahorse 3.36 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2022-01-29 Thread Alejandro
same problem. LTS Ubuntu 20.04 update today 01-2022, seahorse 3.36-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2021-12-03 Thread Victor Frederico Beust da Silva
Also been hit here. Are there any alternatives, is there an older working version of the software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2021-10-05 Thread Meluco
I can't undestand why this bug still unatended. Certificates and signing is a common practice for today. This bug affects any application who searchs for certificates on operating system storage. Install the same certificate many times in multiple applications increase probabilities for vulnerabi

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2021-01-28 Thread Jo Wilkes
(Sorry for #43, wrong bug/thread - but yes, the same goes for .p12 at the versions stated.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to impo

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2021-01-28 Thread Jo Wilkes
Still unable to import openssh-formatted RSA PRIVATE KEYs on Ubuntu 20.04.1 LTS / Gnome 3.36.8 / Seahorse 3.36-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Se

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-07-31 Thread Angelo Giacomini Ribas
Still unable to import .p12 and .cer certificates on Ubuntu 20.04.1 LTS / GNOME 3.36.3 / Seahorse 3.36. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse un

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-07-31 Thread Sebastien Bacher
To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. Venting frustration in a bug report isn't fine. The bug is triaged with

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-07-31 Thread Matej Kovacic
This is really amazing. I still have the same problem. And yes, it is NOT triaged. I have Ubuntu 18.04.4 LTS. LibreOffice is version 6.0.7.3. I would expect some things just work in 21tg century. But obviously, I am wrong. Maybe the problem is, that Ubuntu developers does not use encryption and

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-07-29 Thread Ferriol
As the problem is still not solved in seahorse 3.36 May I can help someone with this link that explains how you can sign a libreoofice document without seahorse, it works for me. https://askubuntu.com/questions/122058/how-do-i-make-a-digital-certificate-available-to-libreoffice-writer-for-digita

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-06-03 Thread Sebastien Bacher
** Changed in: seahorse (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-05-25 Thread Javier-puche-u
Not seahorse but the same problem described in #33, my Mint 19.3 was not being able to sign with Libreoffice 6.0.7.3 (nor other apps like AutoFirma) It was solved by: - downgrading to openjdk 1.8 (sudo apt install openjdk-8-jre; sudo update-java-alternatives -s java-1.8.0-openjdk-amd64 ) - le

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-04-05 Thread Oliver
The keys I was trying to import into Seahorse were located in an encrypted container (mounted, obviously). As I cannot influence (or haven't learned how to influence) the standard file modes when mounting said container, they all had 0700 as file mode, including the .pub files I had generated based

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-04-05 Thread Oliver
Fascinating, I am seeing this exact same issue with SSH keys. When using ssh-add these keys will load into the agent without a problem, but I cannot import them into Seahorse. The files have been generated with OpenSSH, but their file names aren't following the standard id_ and id_.pub pattern ...

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2020-01-15 Thread karlsebal
I compiled 3.30.1.1 and yet: The same error message—“No compatible importer found” -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-11-04 Thread Waldemar Silva Júnior
Nothing yet? Jesus! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gnome-keyrin

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-11-03 Thread László Meskó
Off-topic for Seahorse, but the reporter's (and my) real problem is about signing in LibreOffice. I've found a way to sign document in LibreOffice on Ubuntu: LibreOffice searches a keystore in this order: a.) The environment variable MOZILLA_CERTIFICATE_FOLDER b.) The Thunderbird profile c.) The

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-08-19 Thread Кощеев
** Bug watch added: Red Hat Bugzilla #1434854 https://bugzilla.redhat.com/show_bug.cgi?id=1434854 ** Also affects: seahorse (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1434854 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-10 Thread Sebastien Bacher
You can ignore that upstream bug triager comment, Andre tends to dismiss reports based on first reporting version without checking if that's still an issue which is often the wrong thing to do, https://gitlab.gnome.org/GNOME/seahorse/issues/205 has a one week old comment stating that it's still a p

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-10 Thread Angelo Giacomini Ribas
Well, after filling the report on GitLab, as suggested in comment #15, I receive the following statement from there: Andre Klapper 💬 @aklapper · 14 hours ago Developer You are using a version that is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-09 Thread Bug Watch Updater
** Changed in: seahorse Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seah

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-09 Thread Andre Klapper
** Bug watch added: gitlab.gnome.org/GNOME/seahorse/issues #205 https://gitlab.gnome.org/GNOME/seahorse/issues/205 ** Also affects: seahorse via https://gitlab.gnome.org/GNOME/seahorse/issues/205 Importance: Unknown Status: Unknown -- You received this bug notification because yo

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-09 Thread Angelo Giacomini Ribas
As suggested in post #15, I just filled a bug report on GitLab: , however, as I have my doubts if it is really an upstream bug, as it didn't occur on Ubuntu 16.04, just on Ubuntu 18.04, and some users reported that in Debian it works. Hope anyone

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-07-04 Thread hvico
The problem is still here and for instance it prevents LibreOffice Draw to check PDFs signatures. I think marking this as "wishlist" is terribly wrong, it is a major bug as there is no workaround to import certificates in LibreOffice. -- You received this bug notification because you are a member

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-06-16 Thread Gregory Orange
Regarding #17 and the bug (issue) report at Seahorse Gitlab, the latest comment is that Seahorse 3.20.0 which is the latest available on Ubuntu 18.04, is "an ancient version". Can 18.04 receive a newer version such that upstream can be brought into the issue if it persists with that? -- You recei

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-05-12 Thread Matthew Ray
It's been over a year.. Is anyone going to fix this? Like pls -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-05-09 Thread Waldemar Silva Júnior
So, I also have the same problem using Ubuntu 19.04, is there any workaround to import p12 certificates? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse u

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-04-11 Thread Angelo Giacomini Ribas
As I've explained in the Bug Description, before filling this bug, I'd tested the same process in my wife's laptop then with 'Ubuntu 16.04 LTS' and it imported the certificates ('.cer' and '.p12') without issues. But in my laptop with 'Ubuntu 18.04 LTS' the problem exist (greyed button). Therefore

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-04-11 Thread Fran
I have the same problem, with xubuntu 18.04.2, @samweis say that is a problem in ubuntu, seahorse can import p12 keys well in debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-02-26 Thread Valeriy Pogrebitskiy
I have installed VirtualBox on my Mac laptop, and built Ubuntu 19.04 guest VM - but had issues with everything that requires HTTP/HTTPS access. Eventually, I came across this post - which matches the issue I have and explains why that's so... To have another look at it, I searched for other ways (

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-02-19 Thread David
Same here, cannot import and sign LibreOffice Documents (as I did since last week with 16.04) . Any news on that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahor

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-01-25 Thread Sam Weis
> Seahorse does not support .p12 certificates. It supports GPG and SSH > certificates. I believe this statement and the categorization of the issue as "wishlist" to be incorrect. On a Debian stretch system with seahorse 3.20.0 this issue does not exist. I can import *.p12 certificates. There, se

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-01-09 Thread Besmir Zanaj
So is there a fix available or in its way? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in gnome-keyring packag

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2018-11-16 Thread Cieniek
For what I have tested this bug affects also Network Manager - can't set certificates for WPA(2) Enterprise and/or 802.1X. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title:

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2018-11-14 Thread Jan Vlug
See also: https://askubuntu.com/questions/1037524/how-can-import-private-key-and-certificate-to-seahorse-in-ubuntu-18-04 ** Also affects: gnome-keyring (Fedora) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which i

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2018-11-14 Thread Jan Vlug
See: https://gitlab.gnome.org/GNOME/seahorse/issues/205 Please note that I could not add this link as affected project because launchpad is configured to point to a seahorse Bugzilla, instead of GitLab. Seahorse migrated to GitLab. -- You received this bug notification because you are a member o

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2018-10-24 Thread Cromefire_
Also tested it with .pem not working either The output just changes to: $ gnome-keyring import .pem gnome-keyring: couldn't find any place to import files seahorse can preview p12 and pem just fine, but can't import any. -- You received this bug notification because you are a member of Desktop

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2018-08-28 Thread Jeremy Bicha
Seahorse does not support .p12 certificates. It supports GPG and SSH certificates. Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of t