Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #63078 > unrolled thread

linux-image-4.19.0-0.bpo.1-amd64 unsigned only?

Started byRichard Hector <richard@walnut.gen.nz>
First post2019-01-16 06:10 +0100
Last post2019-01-16 20:20 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  linux-image-4.19.0-0.bpo.1-amd64 unsigned only? Richard Hector <richard@walnut.gen.nz> - 2019-01-16 06:10 +0100
    Re: linux-image-4.19.0-0.bpo.1-amd64 unsigned only? Ben Hutchings <ben@decadent.org.uk> - 2019-01-16 20:20 +0100

#63078 — linux-image-4.19.0-0.bpo.1-amd64 unsigned only?

FromRichard Hector <richard@walnut.gen.nz>
Date2019-01-16 06:10 +0100
Subjectlinux-image-4.19.0-0.bpo.1-amd64 unsigned only?
Message-ID<xgLCF-2oG-1@gated-at.bofh.it>
Sorry if I missed previous discussion on this.

I seem to only see linux-image-4.19.0-0.bpo.1-amd64-unsigned (and the
virtual package) for this version? Is that deliberate?

(There are cloud, rt and dbg packages as well)

This seems to also result in the kernel being tainted (8192 - An
unsigned module has been loaded in a kernel supporting module
signature); or is that unrelated?

Thanks,
Richard

[toc] | [next] | [standalone]


#63085

FromBen Hutchings <ben@decadent.org.uk>
Date2019-01-16 20:20 +0100
Message-ID<xgYTg-211-9@gated-at.bofh.it>
In reply to#63078

[Multipart message — attachments visible in raw view] — view raw

On Wed, 2019-01-16 at 18:03 +1300, Richard Hector wrote:
> Sorry if I missed previous discussion on this.
> 
> I seem to only see linux-image-4.19.0-0.bpo.1-amd64-unsigned (and the
> virtual package) for this version? Is that deliberate?

No.  The signed packages are built from separate source packages that
need to be separately approved for inclusion in the archive.  That just
happened in the last few hours.

> (There are cloud, rt and dbg packages as well)
> 
> This seems to also result in the kernel being tainted (8192 - An
> unsigned module has been loaded in a kernel supporting module
> signature); or is that unrelated?

This is expected if you install the unsigned packages (or an out-of-
tree module).

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.


[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web