Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63640 > unrolled thread
| Started by | Paul Tagliamonte <paultag@debian.org> |
|---|---|
| First post | 2019-03-16 05:10 +0100 |
| Last post | 2019-11-09 22:20 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#924705: Please enable PKCS8_PRIVATE_KEY_PARSER Paul Tagliamonte <paultag@debian.org> - 2019-03-16 05:10 +0100
Processed (with 3 errors): Re: Please enable PKCS8_PRIVATE_KEY_PARSER "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-11-02 18:00 +0100
Bug#924705: Please enable PKCS8_PRIVATE_KEY_PARSER Andreas Henriksson <andreas@fatal.se> - 2019-11-02 18:00 +0100
Bug#924705: marked as done (Please enable PKCS8_PRIVATE_KEY_PARSER) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-11-09 22:20 +0100
| From | Paul Tagliamonte <paultag@debian.org> |
|---|---|
| Date | 2019-03-16 05:10 +0100 |
| Subject | Bug#924705: Please enable PKCS8_PRIVATE_KEY_PARSER |
| Message-ID | <xC8NX-7zx-7@gated-at.bofh.it> |
Package: linux Severity: wishlist thanks It would be nice to add the PKCS8_PRIVATE_KEY_PARSER to the Debian build. Currently, importing a private key is not possible, and generates the error `add_key: Bad message` when a key is attempted to be loaded. Thanks for your hard work and maintenance of such an important package! Paul -- :wq
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2019-11-02 18:00 +0100 |
| Subject | Processed (with 3 errors): Re: Please enable PKCS8_PRIVATE_KEY_PARSER |
| Message-ID | <yY4UO-mw-5@gated-at.bofh.it> |
| In reply to | #63640 |
Processing control commands: > forcemerge 924705 941098 Bug #924705 [linux] Please enable PKCS8_PRIVATE_KEY_PARSER Unable to merge bugs because: package of #941098 is 'src:linux' not 'linux' Failed to forcibly merge 924705: Did not alter merged bugs. > block 941651 by 924705 Bug #941651 [iwd] /usr/lib/modules-load.d/pkcs8.conf triggers failure during boot 941651 was not blocked by any bugs. 941651 was not blocking any bugs. Added blocking bug(s) of 941651: 924705 Failed to set blocking bugs of 941651: failed to get lock on /srv/bugs.debian.org/spool/lock/924705 -- Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > affects 924705 iwd Failed to mark 924705 as affecting package(s): failed to get lock on /srv/bugs.debian.org/spool/lock/924705 -- Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/924705 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. -- 924705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924705 941098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941098 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Andreas Henriksson <andreas@fatal.se> |
|---|---|
| Date | 2019-11-02 18:00 +0100 |
| Message-ID | <yY4UN-mw-1@gated-at.bofh.it> |
| In reply to | #63640 |
Control: forcemerge 924705 941098 Control: block 941651 by 924705 Control: affects 924705 iwd Hi, This issue was discussed today on #debian-kernel and there was a request to add more information about its usage. Quoting what Lev has already written in plain text below (as his html mail is not displayed very well by the bug tracking software). On Fri, Nov 01, 2019 at 02:32:52PM +0300, Lev Abashkin wrote: > This feature is used by iwd for enterprise network connections. > I had to recompile kernel to be able to use iwd in my scenario. > Ubuntu kernel has already turned it on. The iwd (replacement/competitor to wpa_supplicant) relies on lots of in-kernel functionality, instead of duplicating it in userspace. That includes the kernel crypto. The pkcs8 parser is needed for wpa2 enterprise network connections and without it you simply can't connect to those kind of networks. (Connecting to wpa2 personal still works however.) If you need more detailed information on exactly how this works I'd recommend you talk directly to iwd upstream. They can be reached via irc in #iwd on FreeNode, mailinglist iwd at lists.01.org (moderated for non-subscribers), etc. I'm merging a duplicate with similar message. Also there's apparently no auto-module-loading for this and no nice way to handle failures, so iwd upstream decided to cope with this by always shipping a snippet that tries to load the pkcs8 private key parser module in case it's built as a module. That means currently users of iwd gets a warning about failure to load the module on the default debian kernel (which I think is reasonable to give them a hint that something is actually not fully set up for all kind of wifi functionality on their system). This bug was set as a blocker for the reported problem in iwd, although I don't really see anything to do on the iwd side. Regards, Andreas Henriksson
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2019-11-09 22:20 +0100 |
| Subject | Bug#924705: marked as done (Please enable PKCS8_PRIVATE_KEY_PARSER) |
| Message-ID | <z0Gjf-ji-1@gated-at.bofh.it> |
| In reply to | #63640 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sat, 09 Nov 2019 21:10:12 +0000 with message-id <E1iTXzo-0003Go-8A@fasolo.debian.org> and subject line Bug#924705: fixed in linux 5.3.9-1 has caused the Debian Bug report #924705, regarding Please enable PKCS8_PRIVATE_KEY_PARSER to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 924705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924705 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web