Étienne Mollier wrote:
> I don't know if someone else hit some other corner base, but
> signed kernels, bootloaders, drivers, and the like are only
> required if one wishes to, or has to, boot with UEFI Secure Boot
> enabled. That's the only configuration I can think of where it
> would be needed
On 05/10/2019 02.00, Steve McIntyre wrote:
> etienne.moll...@mailoo.org wrote:
>> deloptes, on 2019-10-03:
>>> Gerard ROBIN wrote:
>>>
> What exactly bugs you about the signed kernel? The kernel is so big
> that the extra signatures hardly make a difference.
I read somewhere that the
etienne.moll...@mailoo.org wrote:
>deloptes, on 2019-10-03:
>> Gerard ROBIN wrote:
>>
>> >> What exactly bugs you about the signed kernel? The kernel is so big
>> >> that the extra signatures hardly make a difference.
>> > I read somewhere that the signed kernel was for the "secure boot" of
>> > m
deloptes, on 2019-10-03:
> Gerard ROBIN wrote:
>
> >> What exactly bugs you about the signed kernel? The kernel is so big
> >> that the extra signatures hardly make a difference.
> > I read somewhere that the signed kernel was for the "secure boot" of
> > microsoft and I have nothing of microsoft
Gerard ROBIN wrote:
>> What exactly bugs you about the signed kernel? The kernel is so big
>> that the extra signatures hardly make a difference.
> I read somewhere that the signed kernel was for the "secure boot" of
> microsoft and I have nothing of microsoft on my machine, so that's why
> I ins
On Thu, Oct 03, 2019 at 02:51:29PM +0200, Sven Joachim wrote:
> Date: Thu, 03 Oct 2019 14:51:29 +0200
> From: Sven Joachim
> To: Gerard ROBIN , debian-user@lists.debian.org
> Subject: Re: kernel unsigned
> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
> X-Spam-Fla
On 2019-10-03 12:05 +0200, Gerard ROBIN wrote:
> Hello,
> In my BULLSEYE box, when i make "apt upgrade" if a new kernel is installed
> it is a signed kernel that is installed, but on my machine it is an unsigned
> kernel that I chose to install.
Why did you do that in the first place?
> How can
Hello,
In my BULLSEYE box, when i make "apt upgrade" if a new kernel is installed
it is a signed kernel that is installed, but on my machine it is an unsigned
kernel that I chose to install. How can you force "apt" to install the
unsigned kernel?
For example:
the kernel linux-image-5.2.0-2-amd64-un
Just for the archives...
On Sb, 12 ian 19, 19:31:11, dot...@gmail.com wrote:
>
> Good question. I upgrade my sid regularly and don't mess with the kernel: I
[...]
> Unfortunately no other kernel installed and, unless I go and dig into
> snapsot, at the moment in sid no other kernel version numb
On 14/01/19 11:20 PM, Vincent Lefevre wrote:
> On 2019-01-11 09:52:04 -0500, Michael Stone wrote:
>> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
>>> I recently came across an inconsistency in sid that it seems difficult (to
>>> me)
>>> to overcome.
>>>
>>> A kernel package na
On 2019-01-11 09:52:04 -0500, Michael Stone wrote:
> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
> > I recently came across an inconsistency in sid that it seems difficult (to
> > me)
> > to overcome.
> >
> > A kernel package named linux-image-4.19.0-1-amd64-unsigned provide
On Fri, Jan 11, 2019 at 3:52 PM Michael Stone wrote:
> How did you get the unsigned kernel installed in the first place? It's
> not typically installed, and I don't see any dependencies that would pull
> it in. If it weren't installed there'd be no problem. :)
Good question. I upgrade my sid re
On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
I recently came across an inconsistency in sid that it seems difficult (to me)
to overcome.
A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the running
kernel but, since few days ago, it creates conflicts with
I recently came across an inconsistency in sid that it seems difficult (to
me) to overcome.
A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the
running kernel but, since few days ago, it creates conflicts with the
metapackage linux-image-amd64 (bercause it depends on
linux-imag
14 matches
Mail list logo
